Tokens renaming: edits per peer review

content/concepts/payment-system-basics/accounts/depositauth.md

@@ -54,7 +54,7 @@ An account with Deposit Authorization enabled:
 - If the account has created any trust lines without the [No Ripple flag](rippling.html) enabled, or has enabled the Default Ripple flag and issued any currency, the account **can** receive the tokens of those trust lines in [Payment transactions][] as a result of rippling. It cannot be the destination of those transactions.
 - In general, an account in the XRP Ledger **cannot** receive any non-XRP currencies in the XRP Ledger as long as all of the following are true. (This rule is not specific to the DepositAuth flag.)
     - The account has not created any trust lines with a nonzero limit.
-    - The account has not issued tokens on trust lines created by others
+    - The account has not issued tokens on trust lines created by others.
     - The account has not placed any offers.
 
 The following table summarizes whether a transaction type can deposit money with DepositAuth enabled or disabled:

content/concepts/payment-types/cross-currency-payments.md

@@ -21,7 +21,7 @@ By default, cross-currency payments deliver a fixed amount to their destination
 
 ## Auto-Bridging
 
-Cross-currency payments that exchange one token for another token can automatically use XRP, when it decreases the cost of the payment, by connecting order books to deepen the pool of available liquidity. For example, a payment sending from USD to MXN automatically converts USD to XRP and then XRP to MXN if doing so is cheaper than converting USD to MXN directly.
+Cross-currency payments that exchange one token for another token can automatically use XRP to bridge the tokens, when it decreases the cost of the payment. For example, a payment sending from USD to MXN automatically converts USD to XRP and then XRP to MXN if doing so is cheaper than converting USD to MXN directly. Larger trades can use a combination of direct (USD-MXN) and auto-bridged (USD-XRP-MXN) conversions.
 
 For more information, see [Auto-Bridging](autobridging.html).
 

content/concepts/tokens/authorized-trust-lines.md

@@ -31,7 +31,7 @@ With a stablecoin on the XRP Ledger and use Authorized Trust Lines, the process
 
 ## As a Precaution
 
-Even if you don't intend to use Authorized Trust Lines, you can enable the `RequireAuth` setting on [operational and standby accounts](issuing-and-operational-addresses.html), and then never have those accounts approve any trust lines. This prevents those accounts from issuing tokens by accident (for example, if a user accidentally trusts the wrong address). This is a purely precautionary measure, and does not stop the operational and standby accounts from transferring the _issuer's_ tokens, as intended.
+Even if you don't intend to use Authorized Trust Lines, you can enable the `RequireAuth` setting on [operational and standby accounts](issuing-and-operational-addresses.html), and then never have those accounts approve any trust lines. This prevents those accounts from issuing tokens by accident (for example, if a user accidentally trusts the wrong address). This is only a precaution, and does not stop the operational and standby accounts from transferring the _issuer's_ tokens, as intended.
 
 
 ## Technical Details

content/concepts/tokens/paths.md

@@ -61,7 +61,7 @@ In addition to explicitly specified paths, a transaction can execute along the _
 
 The default path could be any of the following:
 
-* If the transaction is uses only one token (regardless of issuer), then the default path assumes the payment should ripple through the addresses involved. This path only works if those addresses are connected by trust lines.
+* If the transaction uses only one token (regardless of issuer), then the default path assumes the payment should ripple through the addresses involved. This path only works if those addresses are connected by trust lines.
     * If `SendMax` is omitted, or the `issuer` of the `SendMax` is the sender, the default path needs a trust line from the sending `Account` to the `issuer` of the destination `Amount` to work.
     * If the `SendMax` and `Amount` have different `issuer` values, and neither are the sender or receiver, the default path is probably not useful because it would need to ripple across a trust line between the two issuers. Ripple (the company) typically discourages issuers from trusting one another directly.
 * For cross-currency transactions, the default path uses the order book between the source currency (as specified in the `SendMax` field) and the destination currency (as specified in the `Amount` field).

content/concepts/tokens/rippling.md

@@ -32,7 +32,7 @@ We call this process, where two addresses pay each other by adjusting the balanc
 
 Non-issuing accounts, especially liquidity providers who may hold balances from different issuers with different fees and policies, usually do not want their balances to ripple.
 
-The **No Ripple** flag is a setting on a trust line. When two trust lines both have No Ripple enabled by the same address, payments from third parties cannot "ripple" through that address on those trust lines. This protects liquidity providers from having balances shift unexpectedly between different issuers using the same currency code.
+The **No Ripple** flag is a setting on a trust line. When two trust lines both have No Ripple enabled by the same address, payments from third parties cannot ripple through that address on those trust lines. This protects liquidity providers from having balances shift unexpectedly between different issuers using the same currency code.
 
 An account can disable No Ripple on a single trust line, which can allow rippling through any pair that includes that trust line. The account can also enable rippling by default by enabling the [Default Ripple flag](#the-default-ripple-flag).
 

content/references/protocol-reference/data-types/basic-data-types.md

@@ -101,7 +101,7 @@ Reporting Mode does not record ledger data until it has been validated. If you m
 
 ## Specifying Currency Amounts
 
-There are two kinds of currencies in the XRP Ledger: XRP, and tokens. These two types of currencies are specified in different formats, with different precision and rounding behavior.
+There are two kinds of currencies in the XRP Ledger: XRP and tokens. These two types of currencies are specified in different formats, with different precision and rounding behavior.
 
 Some fields, such as the destination `Amount` of a [Payment transaction][], can be either type. Some fields only accept XRP specifically, such as the `Fee` field ([transaction cost](transaction-cost.html)).
 

content/references/protocol-reference/data-types/currency-formats.md

@@ -8,7 +8,7 @@ label:
 ---
 # Currency Formats
 
-The XRP Ledger has two kinds of digital asset: [XRP](xrp.html), and [tokens](tokens.html). Both types have high precision, although their formats are different.
+The XRP Ledger has two kinds of digital asset: [XRP](xrp.html) and [tokens](tokens.html). Both types have high precision, although their formats are different.
 
 ## Comparison