Update links to the example-subgraph repo (#175)

* Update links to the example-subgraph repo

* Combine defining & creating pages

including redirect

* Revert "Combine defining & creating pages"

This reverts commit 359c6e9.

Author: azf20

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-subgraph/tree/arweave-blocks-transactions)
+- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)
 
 ## FAQ
 

pages/en/cookbook/cosmos.mdx

@@ -151,7 +151,7 @@ Each type of handler will receive a different type based on the relevant data. F
 
 `EventData` is passed to the eventHandler.
 
-`TransactionData` is passed to the transactionHandler. Transactions will need to be decoded in the subgraph, [here](https://github.com/graphprotocol/example-subgraph/blob/cosmos-validator-delegations/src/decoding.ts) is an example on how it can be done.
+`TransactionData` is passed to the transactionHandler. Transactions will need to be decoded in the subgraph, [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts) is an example on how it can be done.
 
 ## Creating and building a Cosmos subgraph
 
@@ -223,10 +223,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-subgraph/tree/cosmos-block-filtering)
+[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
 
-[Validator Rewards Example](https://github.com/graphprotocol/example-subgraph/tree/cosmos-validator-rewards)
+[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)
 
-[Validator Delegations Example](https://github.com/graphprotocol/example-subgraph/tree/cosmos-validator-delegations)
+[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)
 
-[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraph/tree/osmosis-token-swaps)
+[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)

pages/en/cookbook/near.mdx

@@ -222,9 +222,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-subgraph/tree/near-blocks-example)
+[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)
 
-[NEAR Receipts](https://github.com/graphprotocol/example-subgraph/tree/near-receipts-example)
+[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)
 
 ## FAQ
 

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-subgraph) 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/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract.
 
 Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever:
 

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

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