find/replace all universal error types links

content/references/rippled-api/admin-rippled-methods/key-generation-methods/validation_create.md

@@ -96,5 +96,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `badSeed` - The request provided an invalid seed value. This usually means that the seed value appears to be a valid string of a different format, such as an account address or validation public key.

content/references/rippled-api/admin-rippled-methods/key-generation-methods/wallet_propose.md

@@ -187,6 +187,6 @@ For more information about multi-signing and signer lists, see [Multi-Signing](r
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly.
 * `badSeed` - The request specified a disallowed seed value (in the `passphrase`, `seed`, or `seed_hex` fields), such as an empty string, or a string resembling a XRP Ledger address.

content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md

@@ -62,7 +62,7 @@ Use this command with no parameter to query the existing `can_delete` setting.
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `notEnabled` - Not enabled in configuration.
 * `notReady` - Not ready to handle this request.
 * `lgrNotFound` - Ledger not found.

content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_cleaner.md

@@ -64,5 +64,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `internal` if one the parameters is specified incorrectly. (This is a bug; the intended error code is `invalidParams`.)

content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_request.md

@@ -173,6 +173,6 @@ When the server is in the progress of fetching a ledger, but has not yet finishe
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. This error can also occur if you specify a ledger index equal or higher than the current in-progress ledger.
 * `lgrNotFound` - If the ledger is not yet available. This indicates that the server has started fetching the ledger, although it may fail if none of its connected peers have the requested ledger. (Previously, this error used the code `ledgerNotFound` instead.) [Updated in: rippled 0.30.1][New in: rippled 0.30.1]

content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/log_level.md

@@ -131,5 +131,5 @@ Otherwise, the request contains the following field:
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.

content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/logrotate.md

@@ -72,4 +72,4 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/server-control-methods/connect.md

@@ -91,6 +91,6 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * Cannot connect in standalone mode - Network-related commands are disabled in stand-alone mode.

content/references/rippled-api/admin-rippled-methods/server-control-methods/ledger_accept.md

@@ -55,5 +55,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `notStandAlone` - If the `rippled` server is not currently running in stand-alone mode.

content/references/rippled-api/admin-rippled-methods/server-control-methods/stop.md

@@ -80,4 +80,4 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/server-control-methods/validation_seed.md

@@ -82,5 +82,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `badSeed` - The request provided an invalid secret value. This usually means that the secret value appears to be a valid string of a different format, such as an account address or validation public key.

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/consensus_info.md

@@ -225,4 +225,4 @@ The results of the `consensus_info` command can vary dramatically if you run it
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md

@@ -184,5 +184,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `badFeature` - The `feature` specified was invalidly formatted, or the server does not know an amendment with that name.

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/fetch_info.md

@@ -153,4 +153,4 @@ The fields describing a fetch in progress are subject to change without notice.
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/get_counts.md

@@ -144,5 +144,5 @@ For most other entries, the value indicates the number of objects of that type c
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/peers.md

@@ -406,4 +406,4 @@ Each member of the `peers` array is a peer object with the following fields:
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/print.md

@@ -228,4 +228,4 @@ The response follows the [standard format](#response-formatting). Additional fie
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validator_list_sites.md

@@ -126,4 +126,4 @@ Each member of the `validator_sites` field array is an object with the following
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validators.md

@@ -174,4 +174,4 @@ Each member of the `publisher_lists` array is an object with the following field
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/public-rippled-methods/account-methods/account_channels.md

@@ -178,7 +178,7 @@ Each Channel Object has the following fields:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The address specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_currencies.md

@@ -142,7 +142,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The address specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_info.md

@@ -202,7 +202,7 @@ Each object in the `transactions` array, if present, may contain any or all of t
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. For example, the request specified `queue` as `true` but specified a `ledger_index` that is not the current open ledger.
 * `actNotFound` - The address specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_lines.md

@@ -179,7 +179,7 @@ Each trust line object has some combination of the following fields:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The [Address][] specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_objects.md

@@ -612,7 +612,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The [Address][] specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_offers.md

@@ -180,7 +180,7 @@ Each offer object contains the following fields:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The [Address][] specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/account-methods/account_tx.md

@@ -584,7 +584,7 @@ Each transaction object includes the following fields, depending on whether it w
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actMalformed` - The [Address][] specified in the `account` field of the request is not formatted properly.
 * `actBitcoin` - The [Address][] specified in the `account` field is formatted like a Bitcoin address instead of a XRP Ledger address.

content/references/rippled-api/public-rippled-methods/account-methods/gateway_balances.md

@@ -211,7 +211,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `invalidHotWallet` - One or more of the addresses specified in the `hotwallet` field is not the [Address][] of an account holding currency issued by the account from the request.
 * `actNotFound` - The [Address][] specified in the `account` field of the request does not correspond to an account in the ledger.

content/references/rippled-api/public-rippled-methods/account-methods/noripple_check.md

@@ -175,7 +175,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actNotFound` - The [Address][] specified in the `account` field of the request does not correspond to an account in the ledger.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger.md

@@ -190,7 +190,7 @@ If the request specified `"owner_funds": true` and expanded transactions, the re
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.
 * `noPermission` - If you specified `full` or `accounts` as true, but are not connected to the server as an admin (usually, admin requires connecting on a local port).

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_closed.md

@@ -84,7 +84,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 
 
 {% include '_snippets/rippled_versions.md' %}

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_current.md

@@ -85,7 +85,7 @@ A `ledger_hash` field is not provided, because the hash of the current ledger is
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 
 
 {% include '_snippets/rippled_versions.md' %}

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_data.md

@@ -252,7 +252,7 @@ The format of each object in the `state` array depends on whether `binary` was s
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors)
+* Any of the [universal error types][]
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.
 

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_entry.md

@@ -142,7 +142,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.
 

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/book_offers.md

@@ -174,7 +174,7 @@ In addition to the standard Offer fields, the following fields may be included i
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.
 * `srcCurMalformed` - The `taker_pays` field in the request is not formatted properly.

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/path_find.md

@@ -453,7 +453,7 @@ Each element in the `alternatives` array is an object that represents a path fro
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `noEvents` - You are using a protocol that does not support asynchronous callbacks, for example JSON-RPC. (See [ripple\_path\_find](#ripple-path-find) for a pathfinding method that _is_ compatible with JSON-RPC.)
 
@@ -528,7 +528,7 @@ If there was no outstanding pathfinding request, an error is returned instead.
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - If any fields are specified incorrectly, or any required fields are missing.
 * `noEvents` - If you tried to use this method on a protocol that does not support asynchronous callbacks, for example JSON-RPC. (See [ripple\_path\_find](#ripple-path-find) for a pathfinding method that _is_ compatible with JSON-RPC.)
 * `noPathRequest` - You tried to close a pathfinding request when there is not an open one.
@@ -573,7 +573,7 @@ If there was no outstanding pathfinding request, an error is returned instead.
 
 ### Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `noEvents` - You are using a protocol that does not support asynchronous callbacks, for example JSON-RPC. (See [ripple\_path\_find](#ripple-path-find) for a pathfinding method that _is_ compatible with JSON-RPC.)
 * `noPathRequest` - You tried to check the status of a pathfinding request when there is not an open one.

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/ripple_path_find.md

@@ -330,7 +330,7 @@ The following fields are deprecated, and may be omitted: `paths_canonical`, and
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `tooBusy` - The server is under too much load to calculate paths. Not returned if you are connected as an admin.
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `srcActMissing` - The `source_account` field is omitted from the request.

content/references/rippled-api/public-rippled-methods/payment-channel-methods/channel_authorize.md

@@ -109,7 +109,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `badSeed` - The `secret` in the request is not a valid secret key.
 * `channelAmtMalformed` - The `amount` in the request is not a valid [XRP amount](#specifying-currency-amounts).
 * `channelMalformed` - The `channel_id` in the request is not a valid Channel ID. The Channel ID should be a 256-bit (64-character) hexadecimal string.

content/references/rippled-api/public-rippled-methods/payment-channel-methods/channel_verify.md

@@ -113,7 +113,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `publicMalformed` - The `public_key` field of the request is not a valid public key in the correct format. Public keys are 33 bytes and must be represented in base58 or hexadecimal. The base58 representation of account public keys starts with the letter `a`. The hexadecimal representation is 66 characters long.
 * `channelMalformed` - The `channel_id` field of the request is not a valid Channel ID. The Channel ID must be a 256-bit (64-character) hexadecimal string.

content/references/rippled-api/public-rippled-methods/server-info-methods/fee.md

@@ -155,7 +155,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 
 
 <!-- TODO: fee levels link to rippled-api-links.md - it is being used one off in a couple of files -->

content/references/rippled-api/public-rippled-methods/server-info-methods/server_info.md

@@ -321,7 +321,7 @@ The `info` object may have some arrangement of the following fields:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 
 
 {% include '_snippets/rippled_versions.md' %}

content/references/rippled-api/public-rippled-methods/server-info-methods/server_state.md

@@ -285,7 +285,7 @@ The `state` object may have some arrangement of the following fields:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 
 <!-- TODO: add fee levels and transaction cost to rippled-api-links.md. multiple files are including them one-off, as below -->
 [fee levels]: concept-transaction-cost.html#fee-levels

content/references/rippled-api/public-rippled-methods/subscription-methods/subscribe.md

@@ -116,7 +116,7 @@ The response follows the [standard format](#response-formatting). The fields con
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `noPermission` - The request included the `url` field, but you are not connected as an admin.
 * `unknownStream` - One or more the members of the `streams` field of the request is not a valid stream name.

content/references/rippled-api/public-rippled-methods/subscription-methods/unsubscribe.md

@@ -78,7 +78,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `noPermission` - The request included the `url` field, but you are not connected as an admin.
 * `malformedStream` - The `streams` field of the request is not formatted properly.

content/references/rippled-api/public-rippled-methods/transaction-methods/sign.md

@@ -209,7 +209,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `highFee` - The current load-based multiplier to the transaction cost exceeds the limit for an automatically-provided transaction cost. Either specify a higher `fee_mult_max` (at least 1000) in the request or manually provide a value in the `Fee` field of the `tx_json`.
 * `tooBusy` - The transaction did not include paths, but the server is too busy to do pathfinding right now. Does not occur if you are connected as an admin.

content/references/rippled-api/public-rippled-methods/transaction-methods/sign_for.md

@@ -221,7 +221,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `srcActNotFound` - If the `Account` from the transaction is not a funded address in the ledger.
 * `srcActMalformed` - If the signing address (`account` field) from the request is not validly formed.

content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md

@@ -271,7 +271,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `amendmentBlocked` - The transaction cannot be submitted to the network because the `rippled` server is [amendment blocked](concept-amendments.html#amendment-blocked).
 * `highFee` - The `fee_mult_max` parameter was specified, but the server's current fee multiplier exceeds the specified one. (Sign-and-Submit mode only)
 * `internalJson` - An internal error occurred when serializing the transaction to JSON. This could be caused by many aspects of the transaction, including a bad signature or some fields being malformed.

content/references/rippled-api/public-rippled-methods/transaction-methods/submit_multisigned.md

@@ -244,7 +244,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `srcActMalformed` - The `Account` field from the `tx_json` was invalid or missing.
 * `internal` - An internal error occurred. This includes the case where a signature is not valid for the transaction JSON provided.

content/references/rippled-api/public-rippled-methods/transaction-methods/transaction_entry.md

@@ -210,7 +210,7 @@ There are a couple possible reasons the server may fail to find the transaction:
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `fieldNotFoundTransaction` - The `tx_hash` field was omitted from the request
 * `notYetImplemented` - A ledger version was not specified in the request.
 * `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

content/references/rippled-api/public-rippled-methods/transaction-methods/tx.md

@@ -199,7 +199,7 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `txnNotFound` - Either the transaction does not exist, or it was part of an older ledger version that `rippled` does not have available.
 

content/references/rippled-api/public-rippled-methods/transaction-methods/tx_history.md

@@ -889,7 +889,7 @@ The fields included in each transaction object vary slightly depending on the ty
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `noPermission` - The `start` field specified was greater than 10000, but you are not connected to the server as an admin.
 

content/references/rippled-api/public-rippled-methods/utility-methods/ping.md

@@ -75,4 +75,4 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].

content/references/rippled-api/public-rippled-methods/utility-methods/random.md

@@ -80,5 +80,5 @@ The response follows the [standard format](#response-formatting), with a success
 
 ## Possible Errors
 
-* Any of the [universal error types](#universal-errors).
+* Any of the [universal error types][].
 * `internal` - Some internal error occurred, possibly relating to the random number generator.