mduo13 suggestions

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

@@ -119,7 +119,7 @@ The `TransferFee` value specifies the percentage fee, in units of 1/10,000, char
 
 This value sets the transfer fee to 314, or .00314%.
 
-![Txr Fee](img/nftokenb.png "Txr Fee")
+![Transfer Fee](img/nftokenb.png "Transfer Fee")
 
 
 
@@ -137,7 +137,7 @@ The fourth section is a `NFTokenTaxon` created by the issuer.
 
 ![NFTokenTaxon](img/nftokend.png "NFTokenTaxon")
 
-An issuer might issue several `NFToken` objects with the same `NFTokenTaxon`; to ensure that `NFToken` objects are spread across multiple pages, the `NFTokenTaxon` is scrambled using the fifth section, a dumb sequential number, as the seed for a random number generator. The scrambled value is stored with the `NFToken`, but the unscrambled value is the actual NFTokenTaxon.
+An issuer might issue several `NFToken` objects with the same `NFTokenTaxon`; to ensure that `NFToken` objects are spread across multiple pages, the `NFTokenTaxon` is scrambled using the fifth section, a sequential number, as the seed for a random number generator. The scrambled value is stored with the `NFToken`, but the unscrambled value is the actual NFTokenTaxon.
 
 ![Dumb Sequential](img/nftokene.png "Dumb Sequential")
 

content/references/protocol-reference/ledger-data/ledger-object-types/nftokenoffer.md

@@ -199,14 +199,6 @@ Sell offers that specify assets other than XRP must specify a non-zero amount. S
    <td>If set, the offer is a sell offer. Otherwise, the offer is a buy offer.
    </td>
   </tr>
-  <!-- tr>
-   <td><code>lsfAuthorized</code>
-   </td>
-   <td><code>0x00000002</code>
-   </td>
-   <td>If set, the offer has been approved by the issuer. This flag can only be set by the <code>Issuer</code> of the token or an account authorized by the issuer (for example, the <code>MintAccount</code> listed in the account root of the <code>Issuer</code>) and only if the token has the flag indicating that authorization is required.
-   </td>
-  </tr -->
 </table>
 
 ## `NFTokenOffer` Transactions

content/references/protocol-reference/ledger-data/ledger-object-types/nftokenpage.md

@@ -11,7 +11,7 @@ status: not_enabled
 # NFTokenPage
 {% include '_snippets/nfts-disclaimer.md' %}
 
-The `NFTokenPage` object represents a collection of `NFToken` objects owned by the same account. An account can have multiple `NFTokenPage` ledger objects, which form a doubly linked list (DLL).
+The `NFTokenPage` object represents a collection of `NFToken` objects owned by the same account. An account can have multiple `NFTokenPage` ledger objects, which form a doubly linked list.
 
 ## Example {{currentpage.name}} JSON
 

content/references/protocol-reference/transactions/transaction-types/nftokenacceptoffer.md

@@ -3,7 +3,7 @@ html: nftokenacceptoffer.html
 parent: transaction-types.html
 blurb: Accept an offer to buy or sell an NFToken.
 labels:
-  - NFTokens, Non-fungible Tokens
+  - NFTs, Non-fungible Tokens
 status: not_enabled
 ---
 # NFTokenAcceptOffer
@@ -28,7 +28,7 @@ The mode in which the transaction operates depends on the presence of the `NFTok
 
 If neither of those fields is specified, the transaction is malformed and produces a `tem` class error.
 
-The semantics of brokered mode are slightly different than one in direct mode: The account executing the transaction functions as a broker, bringing the two offers together and causing them to be matched, but does not acquire ownership of the involved NFToken, which will, if the transaction is successful, be transferred directly from the seller to the buyer.
+The semantics of brokered mode are slightly different than one in direct mode: The account executing the transaction functions as a broker, bringing the two offers together and causing them to be matched, but does not acquire ownership of the involved `NFToken`, which will, if the transaction is successful, be transferred directly from the seller to the buyer.
 
 
 ## Execution Details