chore: fix typos (#2865)

Co-authored-by: Damián Parrino <[email protected]>

Author: roushou

docs/ai/shade-agents/tutorials/ai-dao/dao-agent.md

@@ -43,7 +43,7 @@ Having retrieved both the proposal and manifesto, the agent is ready to make its
 
 ## Voting with an LLM
 
-To make a decision on the proposal, the agent uses an LLM provided by [NEAR AI](https://docs.near.ai/cloud/get-started/). NEAR AI provides verifiable and private inference by running LLMs in GPU TEEs. In this tutorial, the DAO uses NEAR AI for its `verifiable` component. This allows the agent verify that no one is interfering with the the LLM response, as could happen with centralized model hosting. The agent knows the response from the LLM is actually a function of the input, and comes from the expected model.
+To make a decision on the proposal, the agent uses an LLM provided by [NEAR AI](https://docs.near.ai/cloud/get-started/). NEAR AI provides verifiable and private inference by running LLMs in GPU TEEs. In this tutorial, the DAO uses NEAR AI for its `verifiable` component. This allows the agent verify that no one is interfering with the LLM response, as could happen with centralized model hosting. The agent knows the response from the LLM is actually a function of the input, and comes from the expected model.
 
 :::note
 In this tutorial, the agent does not actually verify the attestation from the LLM. Full verification will be added in a future update to the tutorial.

docs/chain-abstraction/intents/overview.md

@@ -13,7 +13,7 @@ NEAR Intents is a multichain transaction protocol where users specify what they
 
 1. **Intent Creation**: A user or AI agent expresses a desired outcome _(ex: Swap Token A for Token B)_ and broadcasts the intent to network of Market Makers (also called Solvers).
 
-2. **Market Makers Compete**: A off-chain decentralized network of Market Makers (aka solvers) compete to fulfill the request in the most optimal way. When the network finds the best solution, it presents it as a quote to the originating user/agent for approval.
+2. **Market Makers Compete**: An off-chain decentralized network of Market Makers (aka solvers) compete to fulfill the request in the most optimal way. When the network finds the best solution, it presents it as a quote to the originating user/agent for approval.
 
 4. **Intent Execution**: If the quote from the Market Maker is accepted, the intent is executed by calling a "Verifier" smart contract on NEAR Protocol. This contract securely verifies and settles the final transaction.
 

docs/primitives/ft/ft.md

@@ -302,7 +302,7 @@ To know how many coins a user has you will need to query the method `ft_balance_
 ---
 
 ## Registering a User
-In order for an user to own and transfer tokens they need to first **register** in the contract. This is done by calling `storage_deposit` and attaching 0.00125Ⓝ.
+In order for a user to own and transfer tokens they need to first **register** in the contract. This is done by calling `storage_deposit` and attaching 0.00125Ⓝ.
 
 By calling this `storage_deposit` the user can register themselves or **register other users**.
 

docs/primitives/linkdrop/linkdrop.md

@@ -261,7 +261,7 @@ await callMethod({
       senderId: accountId,
       // This balance per use is balance of human readable FTs per use.
       amount: "1"
-      // Alternatively, you could use absoluteAmount, which is dependant on the decimals value of the FT
+      // Alternatively, you could use absoluteAmount, which is dependent on the decimals value of the FT
       // ex. if decimals of an ft = 8, then 1 FT token would be absoluteAmount = 100000000
     },
   },

docs/smart-contracts/security/checklist.md

@@ -20,7 +20,7 @@ Check our [security articles](./welcome.md) to understand how to improve the sec
 
 ## Storage
 3. Each time the state grows it is ensured that there is enough balance to cover it
-4. All collections (i.e. Vector, Map, Tree, etc) have an unique id
+4. All collections (i.e. Vector, Map, Tree, etc) have a unique id
 5. Check for underflow and overflow!. In rust, you can do this by simply adding the `overflow-checks = true` flag in your `Cargo.toml`.
 
 ## Actions