fix typos

docs/content/guides/developer/nft/asset-tokenization.mdx

@@ -897,7 +897,7 @@ Examine the `updateConstant` method, which is used to update constants. This met
 - An `expectedValue` that contains the current value of the constant.
 - An `expectedType` that contains the current type of the constant.
 
-The last two arguments are requited to minimize the risk of accidentally updating the wrong constant since this library is directly manipulating complied bytecode, which is quite dangerous.
+The last two arguments are required to minimize the risk of accidentally updating the wrong constant since this library is directly manipulating complied bytecode, which is quite dangerous.
 
 Additionally, the `changeIdentifiers` method updates identifiers, which in our case are the module name and the struct name. This method takes a JSON object as an argument with keys of the current identifier names in the module and values being the desired names you want to change them into.
 

docs/content/guides/developer/nft/nft-rental.mdx

@@ -165,7 +165,7 @@ public struct ProtectedTP<phantom T> has key, store {
 
 The NFT Rental example includes the following functions that define the project's logic. 
 
-The `install` function enables installation of the `Rentables` extension in a kiosk. The party facilitating the rental process is responsible for making sure that the user installs the extension in the their kiosk.
+The `install` function enables installation of the `Rentables` extension in a kiosk. The party facilitating the rental process is responsible for making sure that the user installs the extension in their kiosk.
 
 ```move
 public fun install(

docs/content/guides/developer/sui-101/sponsor-txn.mdx

@@ -119,6 +119,6 @@ Both the user and the sponsor need to sign over the entire `TransactionData`, in
 
 ### Censorship risk
 
-If you chooses to submit the dual-signed transaction to the sponsor or gas station rather than a Full node, the transaction might be subject to sponsor or gas station censorship. Namely, the sponsor might choose not to submit the transaction to the network, or delay the submission. 
+If you choose to submit the dual-signed transaction to the sponsor or gas station rather than a Full node, the transaction might be subject to sponsor or gas station censorship. Namely, the sponsor might choose not to submit the transaction to the network, or delay the submission. 
 
 You can mitigate this risk by submitting the transaction directly to a Full node.

nre/ansible/README.md

@@ -19,7 +19,7 @@ Tested with `ansible [core 2.13.4]` and:
 
 5. Copy the genesis.blob to this directory (should be available after the Genesis ceremony).
 
-6. Udate the `keypair_path` var in the [Ansible Inventory](./inventory.yaml)
+6. Update the `keypair_path` var in the [Ansible Inventory](./inventory.yaml)
 
 ## Example use: