Merge pull request #1669 from nnsW3/Docs-improvements

Docs typo fixes

pages/advanced-api/javascript-sdk.mdx

@@ -1,6 +1,6 @@
 # Ankr.js SDK
 
-_Ankr.js SDK_ contains a compact JavaScript library to enable you interact with [Advanced API](/advanced-api/overview/).
+_Ankr.js SDK_ contains a compact JavaScript library to enable you to interact with [Advanced API](/advanced-api/overview/).
 
 ## Get started
 

pages/advanced-api/token-api.mdx

@@ -3,7 +3,7 @@ import { Callout } from "components";
 
 ## Who Can Spend Your Tokens?
 
-Interacting with DeFi apps, we usually approve token allowances to enable the dApp making transactions on our behalf. It's easy to forget about those allowances and the spending limits involved.
+Interacting with DeFi apps, we usually approve token allowances to enable the dApp to make transactions on our behalf. It's easy to forget about those allowances and the spending limits involved.
 
 Later on it can mean that an exploited project's contract has unlimited access to the tokens in your wallet. And malicious actors can spend those tokens even if you have withdrawn your funds from the smart contract back into your wallet.
 

pages/advanced-tutorials/donation-based-crowdfunding-dapp-on-polygon-with-ankr.mdx

@@ -172,7 +172,7 @@ contract CrowdfundingProject {
     string public projDescription;
     uint256 public goalAmount;
     uint256 public raisedAmount;
-    address ownerWallet; //address where amount to be transfered
+    address ownerWallet; //address where amount to be transferred
 
     event Funded(
         address indexed donar,

pages/automation/create-compatible-contracts.mdx

@@ -6,7 +6,7 @@ Contract that are compatible with the `IAutomateCompatible` Ankr interface allow
 
 A compatible contract contains:
 1. A checker, that repeatedly checks on an event.
-2. A follow-up executor, that contains the custom logic and executes it when the checker returnss `true`. 
+2. A follow-up executor, that contains the custom logic and executes it when the checker returns `true`. 
 
 ## `IAutomateCompatible` interface
 The interface contains a checker `checkTask()` and an executor with the custom logic `performTask()`.

pages/automation/custom-logic-automation.mdx

@@ -12,7 +12,7 @@ To create a custom logic automation task, you need to:
 
 ## Connect a wallet
 <Callout type="info">
-We recommend MetaMask as a most adopted and tested-out wallet and use it throughout our documentation.  
+We recommend MetaMask as the most adopted and tested-out wallet and use it throughout our documentation.  
 </Callout>
 
 To connect a wallet:
@@ -52,4 +52,4 @@ To create a time-based Task:
 * [Automation overview](/automation/overview/)
 * [Time-based automation](/automation/time-based-automation/)
 * [Manage automation tasks](/automation/manage-tasks)
-* [Create compatible contracts](/automation/create-compatible-contracts/)
+* [Create compatible contracts](/automation/create-compatible-contracts/)

pages/automation/manage-tasks.mdx

@@ -5,7 +5,7 @@ import { Callout } from "components";
 ## Fund Tasks
 <Callout type="tip">
 Don't forget to fund your Ankr Automation account so your Tasks can keep running. 
-Remember that actions that write to blockchain and not only read information from need a gas fee to execute.
+Remember that actions that write to blockchain and not only read information from needing a gas fee to execute.
 </Callout>
 
 To add funds:

pages/automation/time-based-automation.mdx

@@ -11,7 +11,7 @@ To create a time-based automation task, you need to:
 
 ## Connect a wallet
 <Callout type="info">
-We recommend MetaMask as a most adopted and tested-out wallet and use it throughout our documentation.  
+We recommend MetaMask as the most adopted and tested-out wallet and use it throughout our documentation.  
 </Callout>
 
 To connect a wallet:
@@ -53,4 +53,4 @@ To create a time-based Task:
 * [Automation overview](/automation/overview/)
 * [Custom logic automation](/automation/custom-logic-automation/)
 * [Manage automation tasks](/automation/manage-tasks)
-* [Create compatible contracts](/automation/create-compatible-contracts/)
+* [Create compatible contracts](/automation/create-compatible-contracts/)

pages/basic-tutorials/backend-nodejs-ipfs-file-uploader-with-filebase.mdx

@@ -429,7 +429,7 @@ FILEBASE_REGION=us-east-1
 FILE_SERVER_URL=http://localhost:5002
 ```
 
-What we want to do is create a way so that when we’re running in `development` mode that the files upload to our local `bucket` folder, but when we’re in production mode, the files upload to IPFS with Filebase. To do this, we’re going to take advantage of our `NODE_ENV` and modify our `upload` middleware to use a different multer configuration when the `NODE_ENV` is set to production. More specifically, we’ll be using an extension of `multer` called `multer-s3` that handles requests regularly to AWS S3 but because Filebase is an AWS S3 compatible service, we’ll just configure it to point to Filebase.
+What we want to do is create a way so that when we’re running in `development` mode the files upload to our local `bucket` folder, but when we’re in production mode, the files upload to IPFS with Filebase. To do this, we’re going to take advantage of our `NODE_ENV` and modify our `upload` middleware to use a different multer configuration when the `NODE_ENV` is set to production. More specifically, we’ll be using an extension of `multer` called `multer-s3` that handles requests regularly to AWS S3 but because Filebase is an AWS S3 compatible service, we’ll just configure it to point to Filebase.
 
 File: `./src/app.ts`