fixed links

content/concept-keys.md

@@ -80,7 +80,7 @@ The XRP Ledger allows an account to authorize a secondary key pair, called a _re
 
 You generate a key pair to use as a regular key pair using the [`wallet_propose`](reference-rippled.html#wallet-propose) method. However, unlike with a [master key pair](#master-key-pair), which is generated alongside and intrinsically related to the `account_id` of an account it supports, you must explicitly create the relationship between a regular key pair and the account you want it to sign transactions for. You use the [`SetRegularKey`](reference-transaction-format.html#setregularkey) method to assign a regular key pair to an account.
 
-For a tutorial on assigning a regular key pair, see [Working with a Regular Key Pair](tutorial-regular-keys.html).
+For a tutorial on assigning a regular key pair, see [Working with a Regular Key Pair](working-regular-key-pair.html).
 
 After you assign a regular key pair to an account, the account has two key pairs associated with it:
 
@@ -91,7 +91,7 @@ You can assign one regular key pair to an account and use it to sign all transac
 
 You can remove or change a regular key pair at any time. This means that if a regular private key is compromised (but the master private key is not), you can regain control of your account by simply removing or changing the regular key pair.
 
-For a tutorial on changing or removing a regular key pair, see [Working with a Regular Key Pair](tutorial-regular-keys.html).
+For a tutorial on changing or removing a regular key pair, see [Working with a Regular Key Pair](working-regular-key-pair.html).
 
 
 ## Signing Algorithms

content/concept-signatures.md

@@ -4,7 +4,7 @@
 
 ***TODO: Question: Added this concept section based on fantastic source material from Rome -- thought we should publish it. Useful? May be good to associate it with a flow diagram - like the one for address encoding: https://ripple.com/build/accounts/#address-encoding. Address both single and multi-sign flows.***
 
-In the XRP Ledger, a digital signature proves that a transaction is authorized to do a specific set of actions. A digital signature is created based on a [key pair](concept-keys.html) associated with the transaction's sending account.
+In the XRP Ledger, a digital signature proves that a transaction is authorized to do a specific set of actions. A digital signature is created based on a [key pair](cryptographic-keys.html) associated with the transaction's sending account.
 
 Here's an overview of some of the more common signature-related fields used in the XRP Ledger.
 
@@ -20,7 +20,7 @@ To verify whether a single-signed transaction is valid, a `rippled` server check
 
 1. This key hashes to an address that's authorized by the transaction's sender.
 
-    The default is that only the address of an account is authorized to send all transactions for that account. That address is [derived from](concept-accounts.html#address-encoding) the public key from the master key pair that was generated during address creation. Regular keys add a different address (derived from a different key pair) that's authorized to send most transactions. And of course, you can also disable the [master key](concept-keys.html) or add a [multi-signing list](reference-transaction-format.html#multi-signing). ***TODO: address from Ryan: "And of course" - Nit: this seems a little informal. Maybe just drop it and go into the next sentence? JHA take a closer look at what this sentence is trying to say.***
+    The default is that only the address of an account is authorized to send all transactions for that account. That address is [derived from](concept-accounts.html#address-encoding) the public key from the master key pair that was generated during address creation. Regular keys add a different address (derived from a different key pair) that's authorized to send most transactions. And of course, you can also disable the [master key](cryptographic-keys.html) or add a [multi-signing list](reference-transaction-format.html#multi-signing). ***TODO: address from Ryan: "And of course" - Nit: this seems a little informal. Maybe just drop it and go into the next sentence? JHA take a closer look at what this sentence is trying to say.***
 
 2. This key matches the signature on the transaction.
 

content/reference-transaction-format.md

@@ -25,7 +25,7 @@ Any signature type can authorize any type of transaction, with the following exc
 * Only the master private key can [permanently give up the ability to freeze](concept-freeze.html#no-freeze).
 * You can never remove the last method of signing transactions from an address.
 
-For more information about master and regular key pairs, see [Cryptographic Keys](concept-keys.html).
+For more information about master and regular key pairs, see [Cryptographic Keys](cryptographic-keys.html).
 
 <!--{# Add this reference after signatures concept doc is published. For more information about signatures, see [Understanding Signatures](concept-signatures.html). #}-->
 
@@ -175,7 +175,7 @@ Example response from the `tx` command:
 
 ### Multi-Signing
 
-Multi-signing in the XRP Ledger is the act of [authorizing transactions](#authorizing-transactions) for the XRP Ledger by using a combination of multiple secret keys. You can have any combination of authorization methods enabled for your address, including multi-signing, a [master key pair](concept-keys.html#master-key-pair), and a [regular key pair](concept-keys.html#regular-key-pair). (The only requirement is that _at least one_ method must be enabled.)
+Multi-signing in the XRP Ledger is the act of [authorizing transactions](#authorizing-transactions) for the XRP Ledger by using a combination of multiple secret keys. You can have any combination of authorization methods enabled for your address, including multi-signing, a [master key pair](cryptographic-keys.html#master-key-pair), and a [regular key pair](cryptographic-keys.html#regular-key-pair). (The only requirement is that _at least one_ method must be enabled.)
 
 The [SignerListSet transaction][] defines which addresses can authorize transactions from your address. You can include up to 8 addresses in a SignerList. You can control how many signatures are needed, in which combinations, by using the quorum and weight values of the SignerList.
 

content/rippled-api-methods/wallet_propose.md

@@ -180,7 +180,7 @@ You can also use this method to generate a key pair to use as a regular key pair
 
 In addition to using it as a regular key pair, you can also use it as a member of a multi-signing list (SignerList).
 
-For more information about master and regular key pairs, see [Cryptographic Keys](concept-keys.html)
+For more information about master and regular key pairs, see [Cryptographic Keys](cryptographic-keys.html)
 
 For more information about multi-signing and signer lists, see [Multi-Signing](reference-transaction-format.html#multi-signing).
 

content/transactions/setregularkey.md

@@ -6,9 +6,9 @@ A `SetRegularKey` transaction assigns, changes, or removes the regular key pair
 
 You can protect your account by assigning a regular key pair to it and using it instead of the master key pair to sign transactions whenever possible. If your regular key pair is compromised, but your master key pair is not, you can use a `SetRegularKey` transaction to regain control of your account.
 
-For more information about regular and master key pairs, see [Cryptographic Keys](concept-keys.html).
+For more information about regular and master key pairs, see [Cryptographic Keys](cryptographic-keys.html).
 
-For a tutorial on assigning a regular key pair to an account, see [Working with a Regular Key Pair](tutorial-regular-keys.html).
+For a tutorial on assigning a regular key pair to an account, see [Working with a Regular Key Pair](working-regular-key-pair.html).
 
 For even greater security, you can use [multi-signing](#multi-signing), but multi-signing requires additional XRP for the [transaction cost](concept-transaction-cost.html) and [reserve](concept-reserves.html).
 

content/tutorial-regular-keys.md

@@ -2,7 +2,7 @@
 
 The XRP Ledger allows an account to authorize a secondary key pair, called a _regular key pair_, to sign future transactions. If the private key of a regular key pair is compromised, you can remove or replace it without changing the rest of your account and re-establishing its relationships to other accounts. You can also rotate a regular key pair proactively. (Neither of those things is possible for the master key pair of an account, which is intrinsically linked to the account's address.)
 
-For more information about master and regular key pairs, see [Cryptographic Keys](concept-keys.html).
+For more information about master and regular key pairs, see [Cryptographic Keys](cryptographic-keys.html).
 
 This article provides the following tutorials:
 
@@ -684,7 +684,7 @@ If your account's regular key pair is compromised, or if you just want to period
 
 The steps to change your existing regular key pair are almost the same as the steps to [assign a regular key](#assigning-a-regular-key-pair) for the first time. You generate the key pair and assign it to your account as a regular key pair, overwriting the existing regular key pair. However, the main difference is that when changing the existing regular key pair, you can use the existing regular private key to replace itself, whereas when assigning a regular key pair to an account for the first time, you have to use the account's master private key to do it.
 
-For more information about master and regular key pairs, see [Cryptographic Keys](concept-keys.html).
+For more information about master and regular key pairs, see [Cryptographic Keys](cryptographic-keys.html).
 
 
 ### Removing a Regular Key Pair