update docs from review comments

docs/docs/architecture/adr/adr-002-globalfee.md

@@ -98,17 +98,22 @@ Checking `feeCoinsNonZeroDenom` against `nonZeroCoinFeesReq`:
 	}
 ```
 
-Here is an example of how the coins split and checked in fee antehandler:\
-**assumption**:\
+Here is an example of how the coins split and checked in fee antehandler:
+
+**assumption**:
+
 `globalfee=[1photon, 0uatom, 1stake]` and `local min-gas-prices=[0.5stake]`
 
-**fee requirement**:\
+**fee requirement**:
+
 `combinedFeeRequirement=[1photon, 0uatom, 1stake]`
 
-**split fee requirement**:\
+**split fee requirement**:
+
 the `combinedFeeRequirement` into `nonZeroCoinFeesReq=[0uatom]`, and `nonZeroCoinFeesReq=[1photon, 1stake]`
 
-**split the paid fees**:\
+**split the paid fees**:
+
 if `paidFee=[1uatom, 0.5photon]`,
 the `splitCoinsByDenoms` splits the paidFee into `feeCoinsZeroDenom=[1uatom]` (the same denom as zero coins in `combinedFeeRequirement`), and `feeCoinsNonZeroDenom=[0.5stake]`
 then `feeCoinsZeroDenom=[1uatom]` is checked by `nonZeroCoinFeesReq=[1photon, 1stake]`.
@@ -121,7 +126,7 @@ Please note that `feeCoins` does not contain zero coins. The fee coins are split
 
 ### Fee Checks in  `DeliverTx`
 Implementing fee checks within the `DeliverTx` function introduces a few requirements:
-- **Deterministic Minimum Fee Requirement**: For the `DeliverTx` process, it is essential to have a deterministic minimum fee requirement. In `CheckTx`, fee is checked by the `CombinedFeeRequirement(globalFees, localFees)`, which considers both `minimum-gas-prices` from `config/app.toml` and `MinimumGasPricesParam` from the globalfee Params (For more details, see [globalfee](../../modules/globalfee)). `CombinedFeeRequirement` contains non-deterministic part: `minimum-gas-prices` from `app.toml`. Therefore, `CombinedFeeRequirement` cannot be used in `DeliverTx`. In `DeliverTx`, only `MinimumGasPricesParam` in globalfee Params is used for fee verification. The code implementation is shown below. 
+- **Deterministic Minimum Fee Requirement**: For the `DeliverTx` process, it is essential to have a deterministic minimum fee requirement. In `CheckTx`, fee is checked by the `CombinedFeeRequirement(globalFees, localFees)`, which considers both `minimum-gas-prices` from `config/app.toml` and `MinimumGasPricesParam` from the globalfee Params (For more details, see [globalfee](../../modules/globalfee.md)). `CombinedFeeRequirement` contains non-deterministic part: `minimum-gas-prices` from `app.toml`. Therefore, `CombinedFeeRequirement` cannot be used in `DeliverTx`. In `DeliverTx`, only `MinimumGasPricesParam` in globalfee Params is used for fee verification. The code implementation is shown below. 
 
 ```go
 func (mfd FeeDecorator) GetTxFeeRequired(ctx sdk.Context, tx sdk.FeeTx) (sdk.Coins, error) {

docs/docs/governance/proposal-types/param-change.md

@@ -3,13 +3,13 @@ title: Parameter Changes
 order: 4
 ---
 
-This documentation also aims to provide guidelines for creating and assessing parameter-change proposals.
+This documentation aims to provide guidelines for creating and assessing parameter-change proposals.
 
 Drafting and submitting a parameter-change governance proposal involves two kinds of risk: losing proposal deposit amounts and the potential to alter the function of the Cosmos Hub network in an undesirable way. 
 
 ## What parameters can be changed?
 
-The complete parameters of the Cosmos Hub are split up into different modules, each of which has its own set of parameters. Most module's parameters can be updated by submitting a governance proposal.
+The complete parameters of the Cosmos Hub are split up into different modules, each of which has its own set of parameters. Most parameters can be updated by submitting a governance proposal.
 
 List of modules whose parameters can be changed via governance:
 * x/auth