fix: point docs to graph tooling for example subgraph

website/pages/ar/cookbook/arweave.mdx

@@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio
 
 Here is an example subgraph for reference:
 
-- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
+- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
 
 ## الأسئلة الشائعة
 

website/pages/ar/cookbook/cosmos.mdx

@@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi
 
 It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed.
 
-An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts).
+An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
 
 ## Creating and building a Cosmos subgraph
 
@@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
 
 فيما يلي بعض الأمثلة على الـ subgraphs للرجوع إليها:
 
-[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
+[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
+[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
+[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
+[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

website/pages/ar/cookbook/near.mdx

@@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition,
 
 فيما يلي بعض الأمثلة على الـ subgraphs للرجوع إليها:
 
-[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
+[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 
-[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
+[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
 
 ## الأسئلة الشائعة
 

website/pages/ar/cookbook/subgraph-debug-forking.mdx

@@ -18,7 +18,7 @@ title: Quick and Easy Subgraph Debugging Using Forks
 
 ## من فضلك ، أرني بعض الأكواد!
 
-To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract.
+To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract.
 
 فيما يلي المعالجات المعرفة لفهرسة `Gravatar` ، بدون أخطاء على الإطلاق:
 

website/pages/ar/developing/creating-a-subgraph.mdx

@@ -98,7 +98,7 @@ Subgraph manifest `subgraph.yaml` تحدد العقود الذكية لفهار
 ```yaml
 specVersion: 0.0.4
 description: Gravatar for Ethereum
-repository: https://github.com/graphprotocol/example-subgraphs
+repository: https://github.com/graphprotocol/graph-tooling
 schema:
   file: ./schema.graphql
 dataSources:

website/pages/de/cookbook/arweave.mdx

@@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio
 
 Here is an example subgraph for reference:
 
-- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
+- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
 
 ## FAQ
 

website/pages/de/cookbook/cosmos.mdx

@@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi
 
 It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed.
 
-An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts).
+An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
 
 ## Creating and building a Cosmos subgraph
 
@@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
 
 Here are some example subgraphs for reference:
 
-[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
+[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
+[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
+[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
+[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

website/pages/de/cookbook/near.mdx

@@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition,
 
 Here are some example subgraphs for reference:
 
-[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
+[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 
-[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
+[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
 
 ## FAQ
 

website/pages/de/cookbook/subgraph-debug-forking.mdx

@@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n
 
 ## Please, show me some code!
 
-To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract.
+To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract.
 
 Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever:
 

website/pages/de/developing/creating-a-subgraph.mdx

@@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is:
 ```yaml
 specVersion: 0.0.4
 description: Gravatar for Ethereum
-repository: https://github.com/graphprotocol/example-subgraphs
+repository: https://github.com/graphprotocol/graph-tooling
 schema:
   file: ./schema.graphql
 dataSources:

website/pages/en/cookbook/arweave.mdx

@@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio
 
 Here is an example subgraph for reference:
 
-- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
+- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
 
 ## FAQ
 

website/pages/en/cookbook/cosmos.mdx

@@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi
 
 It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed.
 
-An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts).
+An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
 
 ## Creating and building a Cosmos subgraph
 
@@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
 
 Here are some example subgraphs for reference:
 
-[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
+[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
+[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
+[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
+[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

website/pages/en/cookbook/near.mdx

@@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition,
 
 Here are some example subgraphs for reference:
 
-[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
+[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 
-[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
+[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
 
 ## FAQ
 

website/pages/en/cookbook/subgraph-debug-forking.mdx

@@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n
 
 ## Please, show me some code!
 
-To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract.
+To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract.
 
 Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever:
 

website/pages/en/developing/creating-a-subgraph.mdx

@@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is:
 ```yaml
 specVersion: 0.0.4
 description: Gravatar for Ethereum
-repository: https://github.com/graphprotocol/example-subgraphs
+repository: https://github.com/graphprotocol/graph-tooling
 schema:
   file: ./schema.graphql
 dataSources:

website/pages/es/cookbook/arweave.mdx

@@ -166,7 +166,7 @@ El endpoint de GraphQL para los subgrafos de Arweave está determinado por la de
 
 A continuación se muestra un ejemplo de subgrafo como referencia:
 
-- [Ejemplo de subgrafo para Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
+- [Ejemplo de subgrafo para Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
 
 ## Preguntas frecuentes
 

website/pages/es/cookbook/cosmos.mdx

@@ -178,7 +178,7 @@ Puedes encontrar una lista completa de los tipos para la integración Cosmos aqu
 
 Es importante tener en cuenta que los mensajes de Cosmos son específicos de la cadena y se pasan a un subgrafo en forma de una carga de Protocol Buffers serializada [Protocol Buffers](https://developers.google.com/protocol-buffers/) Como resultado, los datos del mensaje deben decodificarse en una función de mapeo antes de que puedan ser procesados. Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí.
 
-Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts).
+Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
 
 ## Crear y construir un subgrafo de Cosmos
 
@@ -250,10 +250,10 @@ La red principal de Osmosis es `osmosis-1`. La red de prueba actual de Osmosis e
 
 A continuación se presentan algunos ejemplos de subgrafos como referencia:
 
-[Ejemplo de filtrado de bloques](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
+[Ejemplo de filtrado de bloques](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Ejemplo de recompensas del validador](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
+[Ejemplo de recompensas del validador](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Ejemplo de delegaciones de validador](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
+[Ejemplo de delegaciones de validador](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Ejemplo de intercambio de tokens de Osmosis](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
+[Ejemplo de intercambio de tokens de Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

website/pages/es/cookbook/near.mdx

@@ -235,9 +235,9 @@ El endpoint de GraphQL para los subgrafos NEAR está determinado por la definici
 
 A continuación se presentan algunos ejemplos de subgrafos como referencia:
 
-[Bloques NEAR](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
+[Bloques NEAR](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 
-[Recibos NEAR](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
+[Recibos NEAR](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
 
 ## Preguntas frecuentes
 

website/pages/es/cookbook/subgraph-debug-forking.mdx

@@ -18,7 +18,7 @@ En pocas palabras, vamos a _bifurcar el subgrafo fallido_ desde un nodo de Graph
 
 ## ¡Por favor, muéstrame algo de código!
 
-Para mantenernos enfocados en el debugging de subgrafos, simplifiquemos las cosas y sigamos con el [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) que indexa el contrato inteligente Ethereum Gravity.
+Para mantenernos enfocados en el debugging de subgrafos, simplifiquemos las cosas y sigamos con el [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) que indexa el contrato inteligente Ethereum Gravity.
 
 Estos son los handlers definidos para indexar `Gravatar`s, sin errores de ningún tipo:
 

website/pages/es/developing/creating-a-subgraph.mdx

@@ -98,7 +98,7 @@ Para este subgrafo de ejemplo, `subgraph.yaml` es:
 ```yaml
 specVersion: 0.0.4
 description: Gravatar for Ethereum
-repository: https://github.com/graphprotocol/example-subgraphs
+repository: https://github.com/graphprotocol/graph-tooling
 schema:
   file: ./schema.graphql
 dataSources:

website/pages/fr/cookbook/arweave.mdx

@@ -166,7 +166,7 @@ Le endpoint GraphQL pour les subgraphes d'Arweave est déterminé par la défini
 
 Voici un exemple de modèle subgraphe :
 
-- [Exemple de subgraphe pour Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
+- [Exemple de subgraphe pour Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
 
 ## FAQ
 

website/pages/fr/cookbook/cosmos.mdx

@@ -178,7 +178,7 @@ Vous pouvez trouver la liste complète des types pour l'intégration Cosmos [ici
 
 Il est important de noter que les messages Cosmos sont spécifiques à une chaîne et qu'ils sont transmis à un sous-graphe sous la forme d'une charge utile sérialisée [Protocol Buffers](https://developers.google.com/protocol-buffers/). Par conséquent, les données du message doivent être décodées dans une fonction de mappage avant de pouvoir être traitées.
 
-An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts).
+An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
 
 ## Création et construction d'un subgraphe Cosmos
 
@@ -250,10 +250,10 @@ Le réseau principal d'Osmosis est `osmosis-1`. Le réseau de test actuel d'Osmo
 
 Voici quelques exemples de subgraphes pour référence :
 
-[Exemple de filtrage par blocs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
+[Exemple de filtrage par blocs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Exemple de récompenses de validateurs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
+[Exemple de récompenses de validateurs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Exemple de délégation de validateurs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
+[Exemple de délégation de validateurs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Exemple d'échange de jetons Osmosis](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
+[Exemple d'échange de jetons Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

website/pages/fr/cookbook/near.mdx

@@ -235,9 +235,9 @@ Le point de terminaison GraphQL pour les subgraphes NEAR est déterminé par la
 
 Voici quelques exemples de subgraphes pour référence :
 
-[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
+[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 
-[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
+[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
 
 ## FAQ
 

website/pages/fr/cookbook/subgraph-debug-forking.mdx

@@ -18,7 +18,7 @@ En bref, nous allons _fork le subgraphe défaillant_ à partir d'un nœud The Gr
 
 ## Je vous en prie, montrez-moi du code !
 
-Pour rester concentré sur le débogage des subgraphes, gardons les choses simples et suivons l'[exemple du subgraphe](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexant le contrat intelligent Ethereum Gravity.
+Pour rester concentré sur le débogage des subgraphes, gardons les choses simples et suivons l'[exemple du subgraphe](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexant le contrat intelligent Ethereum Gravity.
 
 Voici les gestionnaires définis pour l'indexation des `Gravatars`, sans le moindre bug :
 

website/pages/fr/developing/creating-a-subgraph.mdx

@@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is:
 ```yaml
 specVersion: 0.0.4
 description: Gravatar for Ethereum
-repository: https://github.com/graphprotocol/example-subgraphs
+repository: https://github.com/graphprotocol/graph-tooling
 schema:
   file: ./schema.graphql
 dataSources: