tasks -> how-tos

docs/concepts/accounts/account-types.md

@@ -74,8 +74,8 @@ If a standby address is compromised, the consequences are like an operational ad
     - [Accounts](index.md)
     - [Cryptographic Keys](cryptographic-keys.md)
 - **Tutorials:**
-    - [Assign a Regular Key Pair](../../tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md)
-    - [Change or Remove a Regular Key Pair](../../tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md)
+    - [Assign a Regular Key Pair](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md)
+    - [Change or Remove a Regular Key Pair](../../tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md)
 - **References:**
     - [account_info method][]
     - [SetRegularKey transaction][]

docs/concepts/accounts/cryptographic-keys.md

@@ -88,7 +88,7 @@ The [wallet_propose method][] is one way of generating a master key pair. The re
 
 **Warning:** If a malicious actor learns your master private key (or seed), they have full control over your account, unless your master key pair is disabled. They can take all the money your account holds and do other irreparable harm. Treat your secret values with care!
 
-Because changing a master key pair is impossible, you should treat it with care proportionate to the value it holds. A good practice is to [keep your master key pair offline](../../tutorials/tasks/manage-account-settings/offline-account-setup.md) and set up a regular key pair to sign transactions from your account instead. By keeping the master key pair enabled but offline, you can be reasonably certain that no one can get access to it using the internet, but you can still go find it to use in an emergency.
+Because changing a master key pair is impossible, you should treat it with care proportionate to the value it holds. A good practice is to [keep your master key pair offline](../../tutorials/how-tos/manage-account-settings/offline-account-setup.md) and set up a regular key pair to sign transactions from your account instead. By keeping the master key pair enabled but offline, you can be reasonably certain that no one can get access to it using the internet, but you can still go find it to use in an emergency.
 
 Keeping your master key pair offline means not putting the secret information (passphrase, seed, or private key) anywhere that malicious actors can get access to it. In general, this means it is not within reach of a computer program that interacts with the internet at large. For example, you could keep it on an air-gapped machine that never connects to the internet, on a piece of paper stored in a safe, or have it completely memorized. (Memorization has some drawbacks, though, including making it impossible to pass the key on after you are dead.)
 
@@ -119,7 +119,7 @@ A good security practice is to save your master private key somewhere offline, a
 
 Regular key pairs have the same format as master key pairs. You generate them the same way (for example, using the [wallet_propose method][]). The only difference is that a regular key pair is not intrinsically tied to the account it signs transactions for. It is possible (but not a good idea) to use the master key pair from one account as the regular key pair for another account.
 
-The [SetRegularKey transaction][] assigns or changes the regular key pair for an account. For a tutorial on assigning or changing a regular key pair, see [Assign a Regular Key Pair](../../tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md).
+The [SetRegularKey transaction][] assigns or changes the regular key pair for an account. For a tutorial on assigning or changing a regular key pair, see [Assign a Regular Key Pair](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md).
 
 
 ## Signing Algorithms
@@ -248,8 +248,8 @@ The steps to derive the XRP Ledger's secp256k1 account key pair from a seed valu
 - **Concepts:**
     - [Issuing and Operational Addresses](account-types.md)
 - **Tutorials:**
-    - [Assign a Regular Key Pair](../../tutorials/tasks/manage-account-settings/assign-a-regular-key-pair.md)
-    - [Change or Remove a Regular Key Pair](../../tutorials/tasks/manage-account-settings/change-or-remove-a-regular-key-pair.md)
+    - [Assign a Regular Key Pair](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md)
+    - [Change or Remove a Regular Key Pair](../../tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md)
 - **References:**
     - [SetRegularKey transaction][]
     - [AccountRoot ledger object](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md)

docs/concepts/accounts/index.md

@@ -63,7 +63,7 @@ The typical way to get an account in the XRP Ledger is as follows:
     - [Payment transaction][]
     - [AccountRoot object](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md)
 - **Tutorials:**
-    - [Manage Account Settings (Category)](../../tutorials/tasks/manage-account-settings/index.md)
+    - [Manage Account Settings (Category)](../../tutorials/how-tos/manage-account-settings/index.md)
     - [Monitor Incoming Payments with WebSocket](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md)
 
 {% raw-partial file="/docs/_snippets/common-links.md" /%}

docs/concepts/accounts/multi-signing.md

@@ -60,7 +60,7 @@ There might be a scenario where you create a multi-signing list as a "backup pla
 
 To successfully submit a multi-signed transaction, you must do all of the following:
 
-* The address sending the transaction (specified in the `Account` field) must have a [`SignerList` object in the ledger](../../references/protocol/ledger-data/ledger-entry-types/signerlist.md). For instructions on how to do this, see [Set Up Multi-Signing](../../tutorials/tasks/manage-account-settings/set-up-multi-signing.md).
+* The address sending the transaction (specified in the `Account` field) must have a [`SignerList` object in the ledger](../../references/protocol/ledger-data/ledger-entry-types/signerlist.md). For instructions on how to do this, see [Set Up Multi-Signing](../../tutorials/how-tos/manage-account-settings/set-up-multi-signing.md).
 * The transaction must include the `SigningPubKey` field as an empty string.
 * The transaction must include a [`Signers` field](../../references/protocol/transactions/common-fields.md#signers-field) containing an array of signatures.
 * The signatures present in the `Signers` array must match signers defined in the `SignerList`.
@@ -72,8 +72,8 @@ To successfully submit a multi-signed transaction, you must do all of the follow
 ## See Also
 
 - **Tutorials:**
-    - [Set Up Multi-Signing](../../tutorials/tasks/manage-account-settings/set-up-multi-signing.md)
-    - [Send a Multi-Signed Transaction](../../tutorials/tasks/manage-account-settings/send-a-multi-signed-transaction.md)
+    - [Set Up Multi-Signing](../../tutorials/how-tos/manage-account-settings/set-up-multi-signing.md)
+    - [Send a Multi-Signed Transaction](../../tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction.md)
 - **Concepts:**
     - [Cryptographic Keys](cryptographic-keys.md)
     - [Special Transaction Cost for Multi-signed transactions](../transactions/transaction-cost.md#special-transaction-costs)

docs/concepts/accounts/tickets.md

@@ -63,7 +63,7 @@ Any account can create and use Tickets on any type of transaction. However, some
 - **Concepts:**
     - [Multi-Signing](multi-signing.md)
 - **Tutorials:**
-    - [Use Tickets](../../tutorials/tasks/manage-account-settings/use-tickets.md)
+    - [Use Tickets](../../tutorials/how-tos/manage-account-settings/use-tickets.md)
 - **References:**
     - [TicketCreate transaction][]
     - [Transaction Common Fields](../../references/protocol/transactions/common-fields.md)