Update for NEAR testnet and sync status (#1)

* Update for NEAR testnet and sync status

* Remove note on the indexing progress bar

* Add note on "pending" versions

Author: azf20

pages/en/developer/create-subgraph-hosted.mdx

@@ -23,7 +23,8 @@ The Graph Network supports subgraphs indexing mainnet Ethereum:
 - `poa-core`
 - `poa-sokol`
 - `xdai`
-- `near`
+- `near-mainnet`
+- `near-testnet`
 - `matic`
 - `mumbai`
 - `fantom`
@@ -532,7 +533,7 @@ import {
   Gravity,
   // The events classes:
   NewGravatar,
-  UpdatedGravatar,
+  UpdatedGravatar
 } from '../generated/Gravity/Gravity'
 ```
 

pages/en/developer/developer-faq.mdx

@@ -115,7 +115,8 @@ In the Hosted Service, the following networks are supported:
 - PoA-Core
 - PoA-Sokol
 - xDAI
-- Near
+- NEAR
+- NEAR testnet
 - Matic
 - Mumbai
 - Fantom

pages/en/hosted-service/what-is-hosted-service.mdx

@@ -57,7 +57,8 @@ Please note that the following networks are supported on the Hosted Service. Net
 - `poa-core`
 - `poa-sokol`
 - `xdai`
-- `near`
+- `near-mainnet`
+- `near-testnet`
 - `matic`
 - `mumbai`
 - `fantom`

pages/en/supported-networks/near.mdx

@@ -2,7 +2,7 @@
 title: Building Subgraphs on NEAR
 ---
 
-> NEAR support in Graph Node and on the Hosted Service is in beta: please contact [email protected] so that we can support you in building NEAR subgraphs!
+> NEAR support in Graph Node and on the Hosted Service is in beta: please contact [email protected] with any questions about building NEAR subgraphs!
 
 This guide is an introduction to building subgraphs indexing smart contracts on the [NEAR blockchain](https://docs.near.org/).
 
@@ -75,7 +75,7 @@ dataSources:
 ```
 
 - NEAR subgraphs introduce a new `kind` of data source (`near`)
-- The `network` should correspond to a network on the hosting Graph Node. On the Hosted Service, NEAR's mainnet is `near-mainnet`
+- The `network` should correspond to a network on the hosting Graph Node. On the Hosted Service, NEAR's mainnet is `near-mainnet`, and NEAR's testnet is `near-testnet`
 - NEAR data sources introduce an optional `source.account` field, which is a human readable ID corresponding to a [NEAR account](https://docs.near.org/docs/concepts/account). This can be an account, or a sub account.
 
 NEAR data sources support two types of handlers:
@@ -166,11 +166,10 @@ This includes a new JSON parsing function - logs on NEAR are frequently emitted
 
 Once you have a built subgraph, it is time to deploy it to Graph Node for indexing. NEAR subgraphs can be deployed to any Graph Node `>=v0.26.x` (this version has not yet been tagged & released).
 
-The Graph's Hosted Service currently supports indexing NEAR mainnet in beta, with the following network name:
+The Graph's Hosted Service currently supports indexing NEAR mainnet and testnet in beta, with the following network names:
 
 - `near-mainnet`
-
-Work is in progress to also support the NEAR testnet.
+- `near-testnet`
 
 More information on creating and deploying subgraphs on the Hosted Service can be found [here](/hosted-service/deploy-subgraph-hosted).
 
@@ -207,8 +206,6 @@ Once your subgraph has been deployed, it will be indexed by Graph Node. You can
 }
 ```
 
-> The Indexing progress bar on the Graph Explorer is not currently supported for NEAR subgraphs
-
 ### Indexing NEAR with a Local Graph Node
 
 Running a Graph Node that indexes NEAR has the following operational requirements:
@@ -257,13 +254,13 @@ This is not supported. We are evaluating whether this functionality is required
 
 This is not currently supported. We are evaluating whether this functionality is required for indexing.
 
-### The indexing progress bar for my subgraph on the Hosted Service isn't showing any progress, what is going on?
+### Ethereum subgraphs support "pending" and "current" versions, how can I deploy a "pending" version of a NEAR subgraph?
 
-The indexing progress bar is not currently available for NEAR subgraphs, we are working to add support.
+Pending functionality is not yet supported for NEAR subgraphs. In the interim, you can deploy a new version to a different "named" subgraph, and then when that is synced with the chain head, you can redeploy to your primary "named" subgraph, which will use the same underlying deployment ID, so the main subgraph will be instantly synced.
 
 ### My question hasn't been answered, where can I get more help building NEAR subgraphs?
 
-If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/developer/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/vtvv7FP) and ask in the #near channel
+If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/developer/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/vtvv7FP) and ask in the #near channel, or email [email protected].
 
 ## References