Last link cleanup(??) and removing now-unused files

content/references/rippled-api/api-conventions/basic-data-types.md

@@ -12,24 +12,28 @@ Each closed [Ledger](ledger-data-formats.html) has a [Ledger Index][] and a [Has
 [Address]: #addresses
 
 {% include '_snippets/data_types/address.md' %}
+<!--{#_ #}-->
 
 
 ## Hashes
 [Hash]: #hashes
 
 {% include '_snippets/data_types/hash.md' %}
+<!--{#_ #}-->
 
 
 ## Account Sequence
 [Sequence Number]: #account-sequence
 
 {% include '_snippets/data_types/account_sequence.md' %}
+<!--{#_ #}-->
 
 
 ## Ledger Index
 [Ledger Index]: #ledger-index
 
 {% include '_snippets/data_types/ledger_index.md' %}
+<!--{#_ #}-->
 
 
 ### Specifying Ledgers
@@ -119,6 +123,7 @@ Finally, if the recipient account of the payment trusts multiple issuers for a c
 [Currency Code]: #currency-codes
 
 {% include '_snippets/data_types/currency_code.md' %}
+<!--{#_ #}-->
 
 
 ## Specifying Time
@@ -126,3 +131,8 @@ Finally, if the recipient account of the payment trusts multiple issuers for a c
 The `rippled` server and its APIs represent time as an unsigned integer. This number measures the number of seconds since the "Ripple Epoch" of January 1, 2000 (00:00 UTC). This is like the way the [Unix epoch](http://en.wikipedia.org/wiki/Unix_time) works, except the Ripple Epoch is 946684800 seconds after the Unix Epoch.
 
 Don't convert Ripple Epoch times to UNIX Epoch times in 32-bit variables: this could lead to integer overflows.
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}			
+{% include '_snippets/tx-type-links.md' %}			
+{% include '_snippets/rippled_versions.md' %}

content/references/rippled-api/api-conventions/currency-formats.md

@@ -1,10 +1,11 @@
 # Currency Formats
 
-The XRP Ledger has [two kinds of money](money.html): XRP, and issued currencies. In the XRP Ledger, both types have high precision, although their formats are different.
+The XRP Ledger has two kinds of money: [XRP](xrp.html), and [issued currencies](issued-currencies.html). In the XRP Ledger, both types have high precision, although their formats are different.
 
 ## String Formatting
 
 {% include '_snippets/string-number-formatting.md' %}
+<!--{#_ #}-->
 
 ## XRP Precision
 
@@ -38,7 +39,7 @@ When transmitting non-XRP amounts across the network or recording them in ledger
 
 ## Currency Codes
 
-All non-XRP currencies in the XRP Ledger have a 160-bit currency code. The [`rippled` APIs](reference-rippled.html) map 3-character ASCII strings (case-sensitive) to 160-bit currency codes using a standard mapping. The currency code `XRP` is disallowed for issued currencies. Currencies with the same code can [ripple](rippling.html) across connected trustlines. Currency codes have no other behavior built into the XRP Ledger.
+All non-XRP currencies in the XRP Ledger have a 160-bit currency code. The [`rippled` APIs](rippled-api.html) map 3-character ASCII strings (case-sensitive) to 160-bit currency codes using a standard mapping. The currency code `XRP` is disallowed for issued currencies. Currencies with the same code can [ripple](rippling.html) across connected trustlines. Currency codes have no other behavior built into the XRP Ledger.
 
 ### Standard Currency Codes
 

content/references/rippled-api/api-conventions/error-formatting.md

@@ -99,7 +99,7 @@ For other errors that returned with HTTP status code 200 OK, the responses are f
 
 All methods can potentially return any of the following values for the `error` code:
 
-* `unknownCmd` - The request does not contain a [command](XREF: rippled-api.md) that the `rippled` server recognizes.
+* `unknownCmd` - The request does not contain a [command](rippled-api.html) that the `rippled` server recognizes.
 * `jsonInvalid` - (WebSocket only) The request is not a proper JSON object.
     * JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
 * `missingCommand` - (WebSocket only) The request did not specify a `command` field.

content/references/rippled-api/api-conventions/modifying-the-ledger.md

@@ -4,7 +4,12 @@ All changes to the XRP Ledger happen as the result of transactions. The only API
 
 Transaction submission commands:
 
-- [`submit` command](XREF: submit.md)
-- [`submit_multisigned` command](XREF: submit-multisigned.md)
+- [submit method][]
+- [submit_multisigned method][]
 
-For more information on the various transactions you can submit, see the [Transaction Reference](xref: transaction-methods.html).
+For more information on the various transactions you can submit, see the [Transaction Formats Reference](transaction-formats.html).
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}
+{% include '_snippets/tx-type-links.md' %}
+{% include '_snippets/rippled_versions.md' %}