Fixed formatting issues

Author: node-druidx56y

docs/Learn/rev-plus/design.md

@@ -12,7 +12,7 @@ sidebar_position: 2
 
 Rev+ is implemented as a protocol-level feature integrated directly into the Core blockchain's transaction processing pipeline. The Rev+ model comprises two primary components: an on-chain `configuration` contract and `core chain modifications` that handle the fee distribution logic.
 
-## **Core Components**
+## Core Components
 
 ### 1. Configuration Contract (`Configuration.sol`)
 
@@ -46,7 +46,7 @@ Rev+ core chain logic is implemented directly in the Core blockchain's transacti
 * **Configuration Sync:** Reads the latest configuration from `Configuration.sol`. Governance updates are reflected immediately in the next processed transaction.  
 * **Struct Compatibility:** Uses Go-language versions of the same structs as in Solidity, ensuring consistency across layers.
 
-#### **Gas Accounting**
+#### Gas Accounting
 
 Rev+ introduces a distinct gas accounting mechanism that preserves Core’s standard 50M gas per block limit while supporting additional gas-based reward distributions.
 
@@ -56,8 +56,10 @@ Rev+ introduces a distinct gas accounting mechanism that preserves Core’s stan
 
 ##### Example
 
-* `block.gasUsed`: 50,000,000 (reported)  
-* Sum of all `tx.gasUsed`: 150,000,000 (includes 100M for Rev+ rewards)  
+* `block.gasUsed`: 50,000,000 (reported)
+  
+* Sum of all `tx.gasUsed`: 150,000,000 (includes 100M for Rev+ rewards)
+
 * Net effect: The block’s throughput remains stable, while distributed gas is transparently handled post-EVM.
 
 This accounting model ensures that Rev+ can scale with network usage without disrupting validator block production or degrading network performance.
@@ -148,15 +150,15 @@ if rules.IsLondon {
     rewardAmount.Mul(rewardAmount, effectiveTipU256)  // 10000 * effectiveTip (gasPrice)
 ```
 
-### 6. Fee Distribution**
+### 6. Fee Distribution
 
 * The total distributed reward:  
   * Is added back to the block’s gas pool.  
   * Is **not counted** in the `block.gasUsed` field.  
 * Gas rewards are transferred directly to the configured reward addresses (e.g., DAOs, developers, multisigs, etc).  
 * Any unused transaction gas is refunded to the sender per standard EVM behavior.
 
-### . Accounting and Compliance
+### 7. Accounting and Compliance
 
 * Core enforces the standard **50M gas block limit**, even with Rev+ active.  
 * While `block.gasUsed` may show 50M, the actual sum of all transaction gas usage (including Rev+ distribution gas) may exceed it.  
@@ -232,13 +234,11 @@ recipientAmount = (rewardAmount * rewardPercentage) / DENOMINATOR
 * **Transaction Gas**: Individual `tx.gasUsed` includes Rev+ gas  
 * **Net Effect**: Block can accommodate same transaction count as before Rev+
 
-### **Example Scenario**
+### Example Scenario
 
-```math
 Block Gas Limit: 50,000,000
 Block Gas Used: 50,000,000 (reported)
 Actual Transaction Gas Sum: 150,000,000 (includes 100M distributed)
-```
 
 ## Configuration Lifecycle
 
@@ -308,7 +308,7 @@ The Rev+ revenue sharing model allows Core DAO, the governing body of the Core b
 
 ### Gas Overhead
 
-* Rev+ logic adds minimal computational overhead per transaction  
+* Rev+ logic adds minimal computational overhead per transaction
 * Event signature matching uses efficient hash lookups  
 * Distribution calculations are simple arithmetic operations