Attribute the Upgrade Indexer to The Graph Foundation and clean up publishing and curating pages

website/src/pages/en/gateways/subgraphs/consumer-side/indexing-approaches.mdx

@@ -18,7 +18,7 @@ Standing up an Indexer is its own body of work (the Indexer tech stack, allocati
 
 ## Staging Environments
 
-The most common reason for an Operator to run their own indexing alongside the network is to provide a staging environment for their consumers. In the past, this role was filled by Edge & Node's Upgrade Indexer and hosted service.
+The most common reason for an Operator to run their own indexing alongside the network is to provide a staging environment for their consumers. In the past, this role was filled by the Upgrade Indexer and the hosted service.
 
 Staging environments typically provide:
 

website/src/pages/en/resources/roles/curating.mdx

@@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to Subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality Subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
-The Sunrise Upgrade Indexer ensures the indexing of all Subgraphs, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+The Upgrade Indexer ensures the indexing of all Subgraphs, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
 
 When signaling, Curators can decide to signal on a specific version of the Subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 

website/src/pages/en/subgraphs/developing/deploying-publishing/publishing-a-subgraph.mdx

@@ -7,11 +7,9 @@ Once you have [deployed your Subgraph to Subgraph Studio](/deploying/deploying-a
 
 When you publish a Subgraph to the decentralized network, you make it available for:
 
-- [Curators](/resources/roles/curating/) to begin curating it.
+- [Curators](/resources/roles/curating/) to begin attracting Indexers to sync and serve queries.
 - [Indexers](/indexing/overview/) to begin indexing it.
 
-<VideoEmbed title="How to Publish a Subgraph to Arbitrum" youtube="satdwdbvzAQ" />
-
 Check out the list of [supported networks](/supported-networks/).
 
 ## Publishing from Subgraph Studio
@@ -76,7 +74,7 @@ Developers can add GRT signal to their Subgraphs to incentivize Indexers to quer
 
 > If your Subgraph is eligible for rewards, it is recommended that you curate your own Subgraph with at least 3,000 GRT in order to attract additional indexers to index your Subgraph.
 
-The Sunrise Upgrade Indexer ensures the indexing of all Subgraphs. However, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+The Upgrade Indexer ensures the indexing of all Subgraphs. However, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
 
 When signaling, Curators can decide to signal on a specific version of the Subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 

website/src/pages/en/subgraphs/providers/subgraph-studio/fair-use-policy.mdx

@@ -6,15 +6,15 @@ title: Fair Use Policy
 
 ## Overview
 
-This page outlines the fair usage of [Edge & Node's Upgrade Indexer](/subgraphs/providers/subgraph-studio/upgrade-indexer/). This policy is designed to ensure the efficient use of queries and storage across the free-tier community.
+This page outlines the fair usage of [The Graph Foundation's Upgrade Indexer](/subgraphs/providers/subgraph-studio/upgrade-indexer/). This policy is designed to ensure the efficient use of queries and storage across the free-tier community.
 
 Storage limits, sync thresholds, and usage requirements are explained below. Users who exceed specified limits will need to advance to a paid plan.
 
 We thank users for doing their part to maintain performance and reliability across Edge & Node's infrastructure.
 
 ### 1. Scope
 
-This policy applies to all individual users, teams, chains, and dapps using Edge & Node's Upgrade Indexer in Subgraph Studio.
+This policy applies to all individual users, teams, chains, and dapps using The Graph Foundation's Upgrade Indexer in Subgraph Studio.
 
 ### 2. Fair Use Limits
 

website/src/pages/en/subgraphs/providers/subgraph-studio/upgrade-indexer.mdx

@@ -1,11 +1,10 @@
 ---
-title: Edge & Node Upgrade Indexer
-sidebarTitle: Upgrade Indexer
+title: Upgrade Indexer
 ---
 
 ## Overview
 
-The Upgrade Indexer is a specialized Indexer operated by Edge & Node. It supports newly integrated chains within The Graph ecosystem and ensures new Subgraphs are immediately available for querying, eliminating potential downtime.
+The Upgrade Indexer is a specialized Indexer operated by The Graph Foundation. It supports newly integrated chains within The Graph ecosystem and ensures new Subgraphs are immediately available for querying, eliminating potential downtime.
 
 Originally designed as a transitional support, its primary purpose was to facilitate the migration of Subgraphs from the hosted service to the decentralized network. Currently, it supports newly deployed Subgraphs before the full Chain Integration Process (CIP) Indexing rewards are activated.
 
@@ -22,4 +21,4 @@ Originally designed as a transitional support, its primary purpose was to facili
 
 ### Conclusion
 
-The Edge & Node Upgrade Indexer is foundational in supporting chain integrations and mitigating data latency risks. It plays a critical role in scaling The Graph's decentralized infrastructure by ensuring immediate query support and fostering community-driven indexing.
+The Upgrade Indexer, operated by The Graph Foundation, is foundational in supporting chain integrations and mitigating data latency risks. It plays a critical role in scaling The Graph's decentralized infrastructure by ensuring immediate query support and fostering community-driven indexing.

website/src/pages/en/subgraphs/quick-start.mdx

@@ -96,7 +96,7 @@ graph codegen && graph build
 
 ### 6. Deploy your Subgraph to Subgraph Studio
 
-When you **deploy** a Subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it. A deployed Subgraph's indexing is performed by the [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/), which is a single Indexer owned and operated by Edge & Node. A **deployed** Subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes.
+When you **deploy** a Subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it. A deployed Subgraph's indexing is performed by the [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/), which is a single Indexer operated by The Graph Foundation. A **deployed** Subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes.
 
 > [!IMPORTANT] You do not need to use Subgraph Studio to publish your Subgraph to The Graph Network. Studio is only required for testing and staging your Subgraph prior to publishing.