Removing betas & updating based on sunrise (graphprotocol#545)

MichaelMacaulay · web-flow · commit 4f5e884cc79e · 2023-11-09T11:33:01.000-05:00
* Removing betas and small changes

* Updating based on sunrise\

Also fixing hosted service capitalizations

* Minor tweak

* Addressing Benoit's feedback
diff --git a/website/pages/en/chain-integration-overview.mdx b/website/pages/en/chain-integration-overview.mdx
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [Hosted Service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
diff --git a/website/pages/en/cookbook/arweave.mdx b/website/pages/en/cookbook/arweave.mdx
@@ -2,7 +2,7 @@
 title: Building Subgraphs on Arweave
 ---
 
-> Arweave support in Graph Node and on the Hosted Service is in beta: please reach us on [Discord](https://discord.gg/graphprotocol) with any questions about building Arweave subgraphs!
+> Arweave support in Graph Node and on the hosted service is in beta: please reach us on [Discord](https://discord.gg/graphprotocol) with any questions about building Arweave subgraphs!
 
 In this guide, you will learn how to build and deploy Subgraphs to index the Arweave blockchain.
 
@@ -83,7 +83,7 @@ dataSources:
 ```
 
 - Arweave subgraphs introduce a new kind of data source (`arweave`)
-- The network should correspond to a network on the hosting Graph Node. On the Hosted Service, Arweave's mainnet is `arweave-mainnet`
+- The network should correspond to a network on the hosting Graph Node. On the hosted service, Arweave's mainnet is `arweave-mainnet`
 - Arweave data sources introduce an optional source.owner field, which is the public key of an Arweave wallet
 
 Arweave data sources support two types of handlers:
@@ -150,9 +150,9 @@ Block handlers receive a `Block`, while transactions receive a `Transaction`.
 
 Writing the mappings of an Arweave Subgraph is very similar to writing the mappings of an Ethereum Subgraph. For more information, click [here](/developing/creating-a-subgraph/#writing-mappings).
 
-## Deploying an Arweave Subgraph on the Hosted Service
+## Deploying an Arweave Subgraph on the hosted service
 
-Once your subgraph has been created on the Hosted Service dashboard, you can deploy by using the `graph deploy` CLI command.
+Once your subgraph has been created on the hosted service dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
 graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ --access-token <your-access-token>
diff --git a/website/pages/en/cookbook/upgrading-a-subgraph.mdx b/website/pages/en/cookbook/upgrading-a-subgraph.mdx
@@ -11,7 +11,7 @@ The process of upgrading is quick and your subgraphs will forever benefit from t
 ### Prerequisites
 
 - You have already deployed a subgraph on the hosted service.
-- The subgraph is indexing a chain available (or available in beta) on The Graph Network.
+- The subgraph is indexing a chain available on The Graph Network.
 - You have a wallet with ETH to publish your subgraph on-chain.
 - You have ~10,000 GRT to curate your subgraph so Indexers can begin indexing it.
 
diff --git a/website/pages/en/developing/creating-a-subgraph.mdx b/website/pages/en/developing/creating-a-subgraph.mdx
@@ -143,7 +143,7 @@ dataSources:
 
 The important entries to update for the manifest are:
 
-- `description`: a human-readable description of what the subgraph is. This description is displayed by the Graph Explorer when the subgraph is deployed to the Hosted Service.
+- `description`: a human-readable description of what the subgraph is. This description is displayed by the Graph Explorer when the subgraph is deployed to the hosted service.
 
 - `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed by The Graph Explorer.
 
diff --git a/website/pages/en/developing/developer-faqs.mdx b/website/pages/en/developing/developer-faqs.mdx
@@ -125,18 +125,14 @@ someCollection(first: 1000, skip: <number>) { ... }
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the Hosted Service?
+## 25. Where do I go to find my current subgraph on the hosted service?
 
 Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
 
-## 26. Will the Hosted Service start charging query fees?
+## 26. Will the hosted service start charging query fees?
 
 The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
 
-## 27. When will the Hosted Service be shut down?
-
-The hosted service will shut down in 2023. Read the announcement blog post [here](https://thegraph.com/blog/sunsetting-hosted-service). All dapps using the hosted service are encouraged to upgrade to the decentralized network. Network Grants are available for developers to help upgrade their subgraph to The Graph Network. If your dapp is upgrading a subgraph you can apply [here](https://thegraph.typeform.com/to/Zz8UAPri?typeform-source=thegraph.com).
-
-## 28. How do I update a subgraph on mainnet?
+## 27. How do I update a subgraph on mainnet?
 
 If you’re a subgraph developer, you can deploy a new version of your subgraph to the Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
diff --git a/website/pages/en/developing/supported-networks.mdx b/website/pages/en/developing/supported-networks.mdx
@@ -35,7 +35,7 @@ import { getSupportedNetworks } from '@/src/getSupportedNetworks'
 
 The hosted service relies on the stability and reliability of the underlying technologies, namely the provided JSON RPC endpoints.
 
-Ropsten, Rinkeby and Kovan are being deprecated. Read more on the [Ethereum Foundation Blog](https://blog.ethereum.org/2022/06/21/testnet-deprecation). As of Feb 25th 2023, Ropsten, Rinkeby and Kovan are no longer supported by the Hosted Service. Goerli will be maintained by client developers post-merge, and is also supported by the Hosted Service. Developers who currently use Ropsten, Rinkeby or Kovan as their staging/testing environment are encouraged to migrate to Goerli.
+Ropsten, Rinkeby and Kovan are being deprecated. Read more on the [Ethereum Foundation Blog](https://blog.ethereum.org/2022/06/21/testnet-deprecation). As of Feb 25th 2023, Ropsten, Rinkeby and Kovan are no longer supported by the hosted service. Goerli will be maintained by client developers post-merge, and is also supported by the hosted service. Developers who currently use Ropsten, Rinkeby or Kovan as their staging/testing environment are encouraged to migrate to Goerli.
 
 Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
 
diff --git a/website/pages/en/glossary.mdx b/website/pages/en/glossary.mdx
@@ -12,7 +12,7 @@ title: Glossary
 
 - **Subgraph**: A custom API built on blockchain data that can be queried using [GraphQL](https://graphql.org/). Developers can build, deploy and publish subgraphs to The Graph's decentralized network. Then, Indexers can begin indexing subgraphs to make them available to be queried by subgraph consumers.
 
-- **Hosted Service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
+- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
 
 - **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
diff --git a/website/pages/en/index.json b/website/pages/en/index.json
@@ -23,8 +23,8 @@
       "description": "Use Studio to create subgraphs"
     },
     "migrateFromHostedService": {
-      "title": "Migrate from the Hosted Service",
-      "description": "Migrating subgraphs to The Graph Network"
+      "title": "Upgrade from the hosted service",
+      "description": "Upgrading subgraphs to The Graph Network"
     }
   },
   "networkRoles": {
@@ -63,15 +63,14 @@
       },
       "hostedService": {
         "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the Hosted Service"
+        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },
   "supportedNetworks": {
     "title": "Supported Networks",
-    "description": "The Graph supports the following networks on The Graph Network and the Hosted Service.",
-    "graphNetworkAndHostedService": "The Graph Network & Hosted Service",
-    "hostedService": "Hosted Service",
-    "betaWarning": "In beta."
+    "description": "The Graph supports the following networks on The Graph Network and the hosted service.",
+    "graphNetworkAndHostedService": "The Graph Network & hosted service",
+    "hostedService": "hosted service"
   }
 }
diff --git a/website/pages/en/querying/querying-the-hosted-service.mdx b/website/pages/en/querying/querying-the-hosted-service.mdx
@@ -2,7 +2,7 @@
 title: Querying the Hosted Service
 ---
 
-With the subgraph deployed, visit the [Hosted Service](https://thegraph.com/hosted-service/) to open up a [GraphiQL](https://github.com/graphql/graphiql) interface where you can explore the deployed GraphQL API for the subgraph by issuing queries and viewing the schema.
+With the subgraph deployed, visit the [hosted service](https://thegraph.com/hosted-service/) to open up a [GraphiQL](https://github.com/graphql/graphiql) interface where you can explore the deployed GraphQL API for the subgraph by issuing queries and viewing the schema.
 
 An example is provided below, but please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities.
 
@@ -19,9 +19,9 @@ This query lists all the counters our mapping has created. Since we only create
 }
 ```
 
-## Using The Hosted Service
+## Using the hosted service
 
-The Graph Explorer and its GraphQL playground is a useful way to explore and query deployed subgraphs on the Hosted Service.
+The Graph Explorer and its GraphQL playground is a useful way to explore and query deployed subgraphs on the hosted service.
 
 Some of the main features are detailed below:
 
diff --git a/website/pages/en/tokenomics.mdx b/website/pages/en/tokenomics.mdx
@@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat
 
 It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular applications](https://thegraph.com/explorer) in the web3 ecosystem today.
+By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
 
 The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
 
diff --git a/website/pages/it/developing/supported-networks.mdx b/website/pages/it/developing/supported-networks.mdx
@@ -35,7 +35,7 @@ import { getSupportedNetworks } from '@/src/getSupportedNetworks'
 
 The hosted service relies on the stability and reliability of the underlying technologies, namely the provided JSON RPC endpoints.
 
-Ropsten, Rinkeby and Kovan are being deprecated. Read more on the [Ethereum Foundation Blog](https://blog.ethereum.org/2022/06/21/testnet-deprecation). As of Feb 25th 2023, Ropsten, Rinkeby and Kovan are no longer supported by the Hosted Service. Goerli will be maintained by client developers post-merge, and is also supported by the Hosted Service. Developers who currently use Ropsten, Rinkeby or Kovan as their staging/testing environment are encouraged to migrate to Goerli.
+Ropsten, Rinkeby and Kovan are being deprecated. Read more on the [Ethereum Foundation Blog](https://blog.ethereum.org/2022/06/21/testnet-deprecation). As of Feb 25th 2023, Ropsten, Rinkeby and Kovan are no longer supported by the hosted service. Goerli will be maintained by client developers post-merge, and is also supported by the hosted service. Developers who currently use Ropsten, Rinkeby or Kovan as their staging/testing environment are encouraged to migrate to Goerli.
 
 Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
 
diff --git a/website/src/IndexPage.tsx b/website/src/IndexPage.tsx
@@ -404,9 +404,6 @@ export function SupportedNetworks() {
             )
           })}
         </ul>
-        <Text.P14 color="White64" sx={{ mt: '32px' }}>
-          *{t('index.supportedNetworks.betaWarning')}
-        </Text.P14>
       </div>
     </>
   )

Original file line number	Diff line number	Diff line change
`@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to`
`46`	`46`
`47`	`47`	`### 4. How will priorities be handled?`
`48`	`48`
`49`		`-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [Hosted Service](https://thegraph.com/hosted-service) or those relying on already tested stacks.`
	`49`	`+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.`
Original file line number	Diff line number	Diff line change
`@@ -404,9 +404,6 @@ export function SupportedNetworks() {`
`404`	`404`	`)`
`405`	`405`	`})}`
`406`	`406`	`</ul>`
`407`		`- <Text.P14 color="White64" sx={{ mt: '32px' }}>`
`408`		`- *{t('index.supportedNetworks.betaWarning')}`
`409`		`- </Text.P14>`
`410`	`407`	`</div>`
`411`	`408`	`</>`
`412`	`409`	`)`