Add reviewer fixes

content/references/protocol-reference/ledger-data/ledger-object-types/amendments.md

@@ -38,7 +38,7 @@ The `Amendments` object type contains a list of [Amendments](amendments.html) th
 
 | Name              | JSON Type | [Internal Type][] | Required? | Description |
 |-------------------|-----------|-------------------|-----------|-------------|
-| `Amendments`      | Array     | Vector256         | No        | Array of 256-bit [amendment IDs](amendments.html) for all currently-enabled amendments. If omitted, there are no enabled amendments. |
+| `Amendments`      | Array     | Vector256         | No        | Array of 256-bit [amendment IDs](amendments.html) for all currently enabled amendments. If omitted, there are no enabled amendments. |
 | `Flags`           | Number    | UInt32            | Yes       | A bit-map of boolean flags enabled for this object. Currently, the protocol defines no flags for `Amendments` objects. The value is always `0`. |
 | `LedgerEntryType` | String    | UInt16            | Yes       | The value `0x0066`, mapped to the string `Amendments`, indicates that this object describes the status of amendments to the XRP Ledger. |
 | `Majorities`      | Array     | STArray           | No        | Array of objects describing the status of amendments that have majority support but are not yet enabled. If omitted, there are no pending amendments with majority support. |

content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.md

@@ -11,7 +11,7 @@ You can start a `rippled` server in [Stand-Alone Mode](rippled-server-modes.html
 
 Loading a historical ledger version is useful for "replaying" a ledger to verify that transactions were processed according to the rules of the network, or to compare the results of processing transaction sets with different [amendments](amendments.html) enabled. In the unlikely event that [an attack against the XRP Ledger's consensus mechanism](consensus-protections.html) caused unwanted effects to the shared ledger state, a consensus of validators could "roll back" to a known-good network state starting with this process.
 
-**Caution:** As `rippled` is updated to newer versions, amendments are retired and become core functions of the ledger, which can affect how transactions are processed. To produce historically-accurate resulsts, you need to replay ledgers using the version of `rippled` the transaction was processed in.
+**Caution:** As `rippled` is updated to newer versions, amendments are retired and become core functions of the ledger, which can affect how transactions are processed. To produce historically accurate results, you need to replay ledgers using the version of `rippled` the transaction was processed in.
 
 ## 1. Start `rippled` normally.
 
@@ -65,13 +65,13 @@ For more information on the options you can use when starting `rippled` in stand
 
 ## 6. Manually advance the ledger.
 
-In stand-alone mode, you have to manually advance the ledger with the `ledger_accept` method:
+In stand-alone mode, you must manually advance the ledger with the `ledger_accept` method:
 
 ```
 rippled ledger_accept --conf=/path/to/rippled.cfg
 ```
 
-If a transaction depends on the result of a transaction from a different address, advance the ledger to ensure they're processed in the correct order. Otherwise, you can submit multiple transactions from a single address `rippled` sorts transactions from the same address by ascending `Sequence` number.
+If a transaction depends on the result of a transaction from a different address, advance the ledger to ensure they are processed in the correct order. Otherwise, you can submit multiple transactions from a single address `rippled` sorts transactions from the same address by ascending `Sequence` number.
 
 
 ## See Also

dactyl-config.yml

@@ -2036,7 +2036,7 @@ pages:
 
     -   md: tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.ja.md
         targets:
-            - ja    
+            - ja
 
     -   name: Troubleshooting
         html: troubleshoot-the-rippled-server.html
@@ -2065,8 +2065,8 @@ pages:
     -   md: tutorials/manage-the-rippled-server/troubleshooting/health-check-interventions.md
         targets:
             - en
-            - ja       
-        
+            - ja
+
     -   md: tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md
         targets:
             - en