IA: add links for tutorials

IA: more tutorial links

IA: Tutorials stuff

- Move 'Cancel or Skip a Transaction' to 'About Canceling a Transaction'
  (Fixes #582)
- Add more 'See Also' links to Escrow & Payment Channel tutorials

content/tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.md

@@ -1,6 +1,6 @@
 # Advance the Ledger in Stand-Alone Mode
 
-In stand-alone mode, `rippled` does not communicate to other members of the peer-to-peer network or participate in a consensus process. Instead, you must manually advance the ledger index using the [ledger_accept method][]:
+In [stand-alone mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode), `rippled` does not communicate to other members of the peer-to-peer network or participate in a consensus process. Since there is no consensus process in this mode, you must manually advance the ledger index using the [ledger_accept method][]:
 
 ```
 rippled ledger_accept --conf=/path/to/rippled.cfg
@@ -11,6 +11,20 @@ In stand-alone mode, `rippled` makes no distinction between a "closed" ledger ve
 Whenever `rippled` closes a ledger, it reorders the transactions according to a deterministic but hard-to-game algorithm. (This is an important part of consensus, since transactions may arrive at different parts of the network in different order.) When using `rippled` in stand-alone mode, you should manually advance the ledger before submitting a transaction that depends on the result of a transaction from a different address. Otherwise, the two transactions might be executed in reverse order when the ledger is closed. **Note:** You can safely submit multiple transactions from a single address to a single ledger, because `rippled` sorts transactions from the same address in ascending order by [`Sequence` number](transaction-common-fields.html).
 
 
+## See Also
+
+- **Concepts:**
+    - [The `rippled` Server](the-rippled-server.html)
+        - [`rippled` Server Modes](rippled-server-modes.html)
+    - [Introduction to Consensus](intro-to-consensus.html)
+    - [Amendments](amendments.html)
+- **References:**
+    - [ledger_accept method][]
+    - [server_info method][]
+    - [`rippled` Commandline Usage](commandline-usage.html)
+- **Use Cases:**
+    - [Contribute Code to `rippled`](contribute-code-to-rippled.html)
+
 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
 {% include '_snippets/tx-type-links.md' %}

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

@@ -1,6 +1,8 @@
 # Load a Saved Ledger in Stand-Alone Mode
 
-You can start with a ledger version that was saved to disk if your `rippled` server was previously synced with the XRP Ledger peer-to-peer network (either the production network or the [Test Net](parallel-networks.html)).
+You can start a `rippled` server in [Stand-Alone Mode](TODO) using a [historical ledger version](TODO) that was previously saved to disk. For example, if your `rippled` server was previously synced with any XRP Ledger peer-to-peer network including [the production Mainnet, the Testnet, or the Devnet](parallel-networks.html), you can load any ledger version your server had available.
+
+Loading a historical ledger version so may be 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 previous, known-good network state starting with this process.
 
 ## 1. Start `rippled` normally.
 
@@ -60,6 +62,21 @@ When you load a ledger with `--ledger` in stand-alone mode, it goes to the curre
 rippled ledger_accept --conf=/path/to/rippled.cfg
 ```
 
+
+## See Also
+
+- **Concepts:**
+    - [The `rippled` Server](the-rippled-server.html)
+        - [`rippled` Server Modes](rippled-server-modes.html)
+    - [Introduction to Consensus](intro-to-consensus.html)
+    - [Amendments](amendments.html)
+- **References:**
+    - [ledger_accept method][]
+    - [server_info method][]
+    - [`rippled` Commandline Usage](commandline-usage.html)
+- **Use Cases:**
+    - [Contribute Code to `rippled`](contribute-code-to-rippled.html)
+
 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
 {% include '_snippets/tx-type-links.md' %}

content/tutorials/manage-the-rippled-server/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md

@@ -22,6 +22,21 @@ In a new genesis ledger, the hard-coded default [Reserve](reserves.html) is **20
 
 By default, a new genesis ledger has no [amendments](amendments.html) enabled. If you start a new genesis ledger with `--start`, the genesis ledger contains an [EnableAmendment pseudo-transaction](enableamendment.html) to turn on all amendments natively supported by the `rippled` server, except for amendments that you explicitly disable in the config file. The effects of those amendments are available starting from the very next ledger version. (Reminder: in stand-alone mode, you must [advance the ledger manually](advance-the-ledger-in-stand-alone-mode.html).) [New in: rippled 0.50.0][]
 
+## See Also
+
+- **Concepts:**
+    - [The `rippled` Server](the-rippled-server.html)
+        - [`rippled` Server Modes](rippled-server-modes.html)
+    - [Parallel Networks](parallel-networks.html)
+    - [Amendments](amendments.html)
+    - [Fee Voting](fee-voting.html)
+- **References:**
+    - [ledger_accept method][]
+    - [server_info method][]
+    - [`rippled` Commandline Usage](commandline-usage.html)
+- **Use Cases:**
+    - [Contribute Code to `rippled`](contribute-code-to-rippled.html)
+
 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
 {% include '_snippets/tx-type-links.md' %}