Update: Remove The Graph refences

Author: Juminstock

docs/build/dapp-staking/indexer/tutorial.md

@@ -1,6 +1,6 @@
 # How to Install and Run
 
-## Indexder Installation
+## Indexer Installation
 
 ### 1. Prerequisites
 

docs/build/integrations/indexers/thegraph.md

@@ -1,6 +1,6 @@
 # Node Providers
- 
-The free endpoints mentioned in the [Build Environment section](/docs/build/environment/endpoints) are rate limited and designed for end users to be able to interact with dApps, or deploy/call smart contracts. They are not suitable for usage by dApp UIs that scrape blockchain data continuously, or indexers (like the Graph).
+
+The free endpoints mentioned in the [Build Environment section](/docs/build/environment/endpoints) are rate limited and designed for end users to be able to interact with dApps, or deploy/call smart contracts. They are not suitable for usage by dApp UIs that scrape blockchain data continuously, or indexers.
 
 
 If you are an active developer you should consider creating your own endpoint, and it is mandatory to do so for production deployments. Refer to how run an [archive node](/docs/nodes

docs/build/integrations/node-providers/index.md

@@ -71,7 +71,7 @@ Description=Astar Archive node
 [Service]
 User=astar
 Group=astar
-  
+
 ExecStart=/usr/local/bin/astar-collator \
   --pruning archive \
   --rpc-cors all \
@@ -101,7 +101,7 @@ Description=Shiden Archive node
 [Service]
 User=astar
 Group=astar
-  
+
 ExecStart=/usr/local/bin/astar-collator \
   --pruning archive \
   --rpc-cors all \
@@ -131,7 +131,7 @@ Description=Shibuya Archive node
 [Service]
 User=astar
 Group=astar
-  
+
 ExecStart=/usr/local/bin/astar-collator \
   --pruning archive \
   --rpc-cors all \
@@ -208,7 +208,7 @@ journalctl -fu astar-collator -n100
 
 ### Indexers and oracles
 
-To access data from indexers (e.g. The Graph) or Oracles (e.g. Chainlink), you need to add the debug flags below to the node launch command, after the `astar-collator` line:
+To access data from indexers (e.g. Subsquid) or Oracles (e.g. Chainlink), you need to add the debug flags below to the node launch command, after the `astar-collator` line:
 
 `--ethapi=debug`
 

docs/build/nodes/archive-node/binary.md

@@ -118,7 +118,7 @@ curl -H "Content-Type: application/json" --data '{ "jsonrpc":"2.0", "method":"sy
 
 In any case, wait for the chain to be fully synchronized by checking the [node log](/docs/build/nodes/archive-node/binary#get-node-logs).
 
-How the archive node will be used will largely determine what steps to follow next: 
+How the archive node will be used will largely determine what steps to follow next:
 - If accessing the node publicly, running an [nginx server](/docs/build/nodes/archive-node/nginx) is the recommended option.
 - If the dApp is running on the same server as the node, then it can be accessed directly with the `localhost` address. This setup is recommended for testing purposes only.
 - If running the node locally for testing purposes, switch networks in [Polkadot.js portal](https://polkadot.js.org/apps) to explore the chain:
@@ -145,7 +145,7 @@ docker logs -f -n 100 $(docker ps -aq --filter name="astar-container")
 
 ### Indexers and Oracles
 
-To access data from indexers (like The Graph) or Oracles (like Chainlink), add the follwing debug flags to the node launch command, after the `astar-collator` line:
+To access data from indexers (like Subsquid) or Oracles (like Chainlink), add the follwing debug flags to the node launch command, after the `astar-collator` line:
 
 `--ethapi=debug`