diff --git a/content/concepts/consensus-network/amendments.md b/content/concepts/consensus-network/amendments.md
index b1270e6eee..70019ac85e 100644
--- a/content/concepts/consensus-network/amendments.md
+++ b/content/concepts/consensus-network/amendments.md
@@ -221,7 +221,7 @@ To look up which `rippled` version supports these features, see [Known Amendment
 
 If you want to see how `rippled` behaves with an amendment enabled, before that amendment gets enabled on the production network, you can run use `rippled`'s configuration file to forcibly enable a feature. This is intended for development purposes only.
 
-Because other members of the consensus network probably do not have the feature enabled, you should not use this feature while connecting to the production network. While testing with features forcibly enabled, you should run `rippled` in [Stand-Alone Mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode).
+Because other members of the consensus network probably do not have the feature enabled, you should not use this feature while connecting to the production network. While testing with features forcibly enabled, you should run `rippled` in [stand-alone mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode).
 
 To forcibly enable a feature, add a `[features]` stanza to your `rippled.cfg` file. In this stanza, add the short names of the features to enable, one per line. For example:
 
diff --git a/content/tutorials/manage-the-rippled-server/load-a-saved-ledger-in-stand-alone-mode.md b/content/tutorials/manage-the-rippled-server/load-a-saved-ledger-in-stand-alone-mode.md
index 27a5837838..9cff00007e 100644
--- a/content/tutorials/manage-the-rippled-server/load-a-saved-ledger-in-stand-alone-mode.md
+++ b/content/tutorials/manage-the-rippled-server/load-a-saved-ledger-in-stand-alone-mode.md
@@ -50,7 +50,7 @@ To instead load a specific historical ledger, use the `--load` parameter along w
 rippled -a --load --ledger 19860944 --conf=/path/to/rippled.cfg
 ```
 
-For more information on the options you can use when starting `rippled` in Stand-Alone mode, see [Commandline Usage: Stand-Alone Mode Options](commandline-usage.html#stand-alone-mode-options).
+For more information on the options you can use when starting `rippled` in stand-alone mode, see [Commandline Usage: Stand-Alone Mode Options](commandline-usage.html#stand-alone-mode-options).
 
 ## 6. Manually advance the ledger.
 
diff --git a/content/tutorials/manage-the-rippled-server/start-a-new-genesis-ledger-in-stand-alone-mode.md b/content/tutorials/manage-the-rippled-server/start-a-new-genesis-ledger-in-stand-alone-mode.md
index 1ec85da92e..d19b3b1f0c 100644
--- a/content/tutorials/manage-the-rippled-server/start-a-new-genesis-ledger-in-stand-alone-mode.md
+++ b/content/tutorials/manage-the-rippled-server/start-a-new-genesis-ledger-in-stand-alone-mode.md
@@ -8,7 +8,7 @@ In stand-alone mode, you can have `rippled` create a new genesis ledger. This pr
 rippled -a --start --conf=/path/to/rippled.cfg
 ```
 
-For more information on the options you can use when starting `rippled` in Stand-Alone mode, see [Commandline Usage: Stand-Alone Mode Options](commandline-usage.html#stand-alone-mode-options).
+For more information on the options you can use when starting `rippled` in stand-alone mode, see [Commandline Usage: Stand-Alone Mode Options](commandline-usage.html#stand-alone-mode-options).
 
 In a genesis ledger, the [genesis address](accounts.html#special-addresses) holds all 100 billion XRP. The keys of the genesis address are [hardcoded](https://github.com/ripple/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184) as follows: