update Spec and Api versions + typos (#894)

* update Spec and Api versions

* fix: commit requested change

* fix: add style

Author: yash251

website/src/pages/en/indexing/overview.mdx

@@ -95,7 +95,7 @@ The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that
 
 Indexers may differentiate themselves by applying advanced techniques for making Subgraph indexing decisions but to give a general idea we'll discuss several key metrics used to evaluate Subgraphs in the network:
 
-- **Curation signal** - The proportion of network curation signal applied to a particular Subgraph is a good indicator of the interest in that Subgraph, especially during the bootstrap phase when query voluming is ramping up.
+- **Curation signal** - The proportion of network curation signal applied to a particular Subgraph is a good indicator of the interest in that Subgraph, especially during the bootstrap phase when query volume is ramping up.
 
 - **Query fees collected** - The historical data for volume of query fees collected for a specific Subgraph is a good indicator of future demand.
 
@@ -784,7 +784,7 @@ Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexi
 
 7. (Optional) Indexers may approve another address to be the operator for their Indexer infrastructure in order to separate the keys that control the funds from those that are performing day to day actions such as allocating on Subgraphs and serving (paid) queries. In order to set the operator call `setOperator()` with the operator address.
 
-8. (Optional) In order to control the distribution of rewards and strategically attract Delegators Indexers can update their delegation parameters by updating their indexingRewardCut (parts per million), queryFeeCut (parts per million), and cooldownBlocks (number of blocks). To do so call `setDelegationParameters()`. The following example sets the queryFeeCut to distribute 95% of query rebates to the Indexer and 5% to Delegators, set the indexingRewardCutto distribute 60% of indexing rewards to the Indexer and 40% to Delegators, and set `thecooldownBlocks` period to 500 blocks.
+8. (Optional) In order to control the distribution of rewards and strategically attract Delegators Indexers can update their delegation parameters by updating their `indexingRewardCut` (parts per million), `queryFeeCut` (parts per million), and `cooldownBlocks` (number of blocks). To do so call `setDelegationParameters()`. The following example sets the `queryFeeCut` to distribute 95% of query rebates to the Indexer and 5% to Delegators, set the `indexingRewardCut` to distribute 60% of indexing rewards to the Indexer and 40% to Delegators, and set the `cooldownBlocks` period to 500 blocks.
 
 ```
 setDelegationParameters(950000, 600000, 500)

website/src/pages/en/indexing/supported-network-requirements.mdx

@@ -6,7 +6,7 @@ title: Supported Network Requirements
 | --- | --- | --- | :-: |
 | Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
 | Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preferred)<br /> _last updated 14th May 2024_ | ✅ |
 | Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
 | Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
 | Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |

website/src/pages/en/resources/migration-guides/assemblyscript-migration-guide.mdx

@@ -44,15 +44,15 @@ This guide is applicable for anyone using `graph-cli`/`graph-ts` below version `
 
 ## How to upgrade?
 
-1. Change your mappings `apiVersion` in `subgraph.yaml` to `0.0.6`:
+1. Change your mappings `apiVersion` in `subgraph.yaml` to `0.0.9`:
 
 ```yaml
 ...
 dataSources:
   ...
     mapping:
       ...
-      apiVersion: 0.0.6
+      apiVersion: 0.0.9
       ...
 ```
 

website/src/pages/en/sps/tutorial.mdx

@@ -72,7 +72,7 @@ dataSources:
         moduleName: map_spl_transfers # Module defined in the substreams.yaml
         file: ./my-project-sol-v0.1.0.spkg
     mapping:
-      apiVersion: 0.0.7
+      apiVersion: 0.0.9
       kind: substreams/graph-entities
       file: ./src/mappings.ts
       handler: handleTriggers

website/src/pages/en/subgraphs/best-practices/grafting-hotfix.mdx

@@ -62,7 +62,7 @@ Suppose you have a Subgraph tracking a smart contract that has stopped indexing
 1. **Failed Subgraph Manifest (subgraph.yaml)**
 
    ```yaml
-   specVersion: 1.0.0
+   specVersion: 1.3.0
    schema:
      file: ./schema.graphql
    dataSources:
@@ -75,7 +75,7 @@ Suppose you have a Subgraph tracking a smart contract that has stopped indexing
          startBlock: 5000000
        mapping:
          kind: ethereum/events
-         apiVersion: 0.0.7
+         apiVersion: 0.0.9
          language: wasm/assemblyscript
          entities:
            - Withdrawal
@@ -90,7 +90,7 @@ Suppose you have a Subgraph tracking a smart contract that has stopped indexing
 
 2. **New Grafted Subgraph Manifest (subgraph.yaml)**
    ```yaml
-   specVersion: 1.0.0
+   specVersion: 1.3.0
    schema:
      file: ./schema.graphql
    dataSources:
@@ -103,7 +103,7 @@ Suppose you have a Subgraph tracking a smart contract that has stopped indexing
          startBlock: 6000001 # Block after the last indexed block
        mapping:
          kind: ethereum/events
-         apiVersion: 0.0.7
+         apiVersion: 0.0.9
          language: wasm/assemblyscript
          entities:
            - Withdrawal

website/src/pages/en/subgraphs/best-practices/pruning.mdx

@@ -20,7 +20,7 @@ Add a section called `indexerHints` in the manifest.
 We can add `indexerHints` to our Subgraphs by updating our `subgraph.yaml`:
 
 ```yaml
-specVersion: 1.0.0
+specVersion: 1.3.0
 schema:
   file: ./schema.graphql
 indexerHints:

website/src/pages/en/subgraphs/cookbook/arweave.mdx

@@ -58,7 +58,7 @@ $ graph build # generates Web Assembly from the AssemblyScript files, and prepar
 The Subgraph manifest `subgraph.yaml` identifies the data sources for the Subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example Subgraph manifest for an Arweave Subgraph:
 
 ```yaml
-specVersion: 0.0.5
+specVersion: 1.3.0
 description: Arweave Blocks Indexing
 schema:
   file: ./schema.graphql # link to the schema file
@@ -70,7 +70,7 @@ dataSources:
       owner: 'ID-OF-AN-OWNER' # The public key of an Arweave wallet
       startBlock: 0 # set this to 0 to start indexing from chain genesis
     mapping:
-      apiVersion: 0.0.5
+      apiVersion: 0.0.9
       language: wasm/assemblyscript
       file: ./src/blocks.ts # link to the file with the Assemblyscript mappings
       entities:

website/src/pages/en/subgraphs/cookbook/grafting.mdx

@@ -53,7 +53,7 @@ Building Subgraphs is an essential part of The Graph, described more in depth [h
 The Subgraph manifest `subgraph.yaml` identifies the data sources for the Subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example Subgraph manifest that you will use:
 
 ```yaml
-specVersion: 0.0.4
+specVersion: 1.3.0
 schema:
   file: ./schema.graphql
 dataSources:
@@ -66,7 +66,7 @@ dataSources:
       startBlock: 5955690
     mapping:
       kind: ethereum/events
-      apiVersion: 0.0.6
+      apiVersion: 0.0.9
       language: wasm/assemblyscript
       entities:
         - Withdrawal

website/src/pages/en/subgraphs/cookbook/near.mdx

@@ -51,7 +51,7 @@ $ graph build # generates Web Assembly from the AssemblyScript files, and prepar
 The Subgraph manifest (`subgraph.yaml`) identifies the data sources for the Subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example Subgraph manifest for a NEAR Subgraph:
 
 ```yaml
-specVersion: 0.0.2
+specVersion: 1.3.0
 schema:
   file: ./src/schema.graphql # link to the schema file
 dataSources:
@@ -61,7 +61,7 @@ dataSources:
       account: app.good-morning.near # This data source will monitor this account
       startBlock: 10662188 # Required for NEAR
     mapping:
-      apiVersion: 0.0.5
+      apiVersion: 0.0.9
       language: wasm/assemblyscript
       blockHandlers:
         - handler: handleNewBlock # the function name in the mapping file

website/src/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx

@@ -1,5 +1,5 @@
 ---
-title: Tranfer to The Graph
+title: Transfer to The Graph
 ---
 
 Quickly upgrade your Subgraphs from any platform to [The Graph's decentralized network](https://thegraph.com/networks/).