Update website/pages/en/deploying/multiple-networks.mdx

Co-authored-by: Benoît Rouleau <[email protected]>

Author: MichaelMacaulay

website/pages/en/deploying/multiple-networks.mdx

@@ -198,7 +198,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
 
-Graph Node exposes a graphql endpoint which you can query to check the status of your subgraph. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 
 ```graphql
 {