remove ropsten and kovan (#185)

* remove ropsten and goerli

* Update developer-faqs.mdx

Author: azf20

.husky/pre-push

@@ -98,7 +98,7 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 **Note:** You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `ropsten` networks, and this is your `subgraph.yaml`:
+Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `goerli` networks, and this is your `subgraph.yaml`:
 
 ```yaml
 # ...
@@ -122,7 +122,7 @@ This is what your networks config file should look like:
       "address": "0x123..."
     }
   },
-  "ropsten": {
+  "goerli": {
     "Gravity": {
       "address": "0xabc..."
     }
@@ -134,20 +134,20 @@ Now we can run the following command:
 
 ```sh
 # Using default networks.json file
-yarn build --network ropsten
+yarn build --network goerli
 
 # Using custom named file
-yarn build --network ropsten --network-file path/to/config
+yarn build --network goerli --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `ropsten` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+The `build` command will update your `subgraph.yaml` with the `goerli` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
 
 ```yaml
 # ...
 dataSources:
   - kind: ethereum/contract
     name: Gravity
-    network: ropsten
+    network: goerli
     source:
       address: '0xabc...'
       abi: Gravity
@@ -161,7 +161,7 @@ Now you are ready to `yarn deploy`
 
 One solution for older graph-cli versions that allows to parameterize aspects like contract addresses is to generate parts of it using a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Ropsten using different contract addresses. You could then define two config files providing the addresses for each network:
+To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Goerli using different contract addresses. You could then define two config files providing the addresses for each network:
 
 ```json
 {
@@ -174,7 +174,7 @@ and
 
 ```json
 {
-  "network": "ropsten",
+  "network": "goerli",
   "address": "0xabc..."
 }
 ```
@@ -204,7 +204,7 @@ In order generate a manifest to either network, you could add two additional com
   "scripts": {
     ...
     "prepare:mainnet": "mustache config/mainnet.json subgraph.template.yaml > subgraph.yaml",
-    "prepare:ropsten": "mustache config/ropsten.json subgraph.template.yaml > subgraph.yaml"
+    "prepare:goerli": "mustache config/goerli.json subgraph.template.yaml > subgraph.yaml"
   },
   "devDependencies": {
     ...
@@ -213,14 +213,14 @@ In order generate a manifest to either network, you could add two additional com
 }
 ```
 
-To deploy this subgraph for mainnet or Ropsten you would now simply run one of the two following commands:
+To deploy this subgraph for mainnet or Goerli you would now simply run one of the two following commands:
 
 ```sh
 # Mainnet:
 yarn prepare:mainnet && yarn deploy
 
-# Ropsten:
-yarn prepare:ropsten && yarn deploy
+# Goerli:
+yarn prepare:goerli && yarn deploy
 ```
 
 A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).

pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx

@@ -4,7 +4,7 @@ title: ما هي الخدمة المستضافة (Hosted Service)؟
 
 سيرشدك هذا القسم لنشر subgraph على الـخدمة المستضافة، والمعروفة باسم [Hosted Service.](https://thegraph.com/hosted-service/) وكتذكير ، الـ Hosted Service لن يغلق قريبا وسننهي الخدمة المستضافة تدريجيا بمجرد أن نصل إلى ميزات مساوية للشبكة اللامركزية. لا تزال الـ subgraphs المنشورة على الخدمة المستضافة متاحة [ هنا. ](https://thegraph.com/hosted-service/)
 
-إذا لم يكن لديك حساب على Hosted Service ، فيمكنك التسجيل باستخدام حساب Github الخاص بك. وبمجرد المصادقة ، يمكنك البدء في إنشاء subgraphs من خلال واجهة المستخدم ونشرها من الـ terminal الخاص بك. يدعم Graph Node عددا من Ethereum testnets (Rinkeby و Ropsten و Kovan) بالإضافة إلى mainnet.
+إذا لم يكن لديك حساب على Hosted Service ، فيمكنك التسجيل باستخدام حساب Github الخاص بك. وبمجرد المصادقة ، يمكنك البدء في إنشاء subgraphs من خلال واجهة المستخدم ونشرها من الـ terminal الخاص بك. يدعم Graph Node عددا من Ethereum testnets (Rinkeby و Goerli) بالإضافة إلى mainnet.
 
 ## إنشاء الـ Subgraph
 
@@ -47,9 +47,7 @@ graph init --from-example --product hosted-service <GITHUB_USER>/<SUBGRAPH_NAME>
 يرجى ملاحظة أن الشبكات التالية مدعومة على Hosted Service. والشبكات خارج Ethereum mainnet ('mainnet') غير مدعومة حاليا على [The Graph Explorer.](https://thegraph.com/explorer)
 
 - `mainnet`
-- `kovan`
 - `rinkeby`
-- `ropsten`
 - `goerli`
 - `poa-core`
 - `poa-sokol`
@@ -73,7 +71,7 @@ graph init --from-example --product hosted-service <GITHUB_USER>/<SUBGRAPH_NAME>
 - `arbitrum-one`
 - `arbitrum-rinkeby`
 - `optimism`
-- `optimism-kovan`
+- `optimism-goerli`
 - `aurora`
 - `aurora-testnet`
 - `harmony`

pages/ar/deploying/hosted-service.mdx

@@ -15,9 +15,7 @@ title: إنشاء الـ Subgraph
 **يتم دعم الشبكات الإضافية في الإصدار beta على Hosted Service**:
 
 - `mainnet`
-- `kovan`
 - `rinkeby`
-- `ropsten`
 - `goerli`
 - `poa-core`
 - `poa-sokol`
@@ -40,7 +38,7 @@ title: إنشاء الـ Subgraph
 - `arbitrum-one`
 - `arbitrum-rinkeby`
 - `optimism`
-- `optimism-kovan`
+- `optimism-goerli`
 - `aurora`
 - `aurora-testnet`
 - `harmony`

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

@@ -62,7 +62,7 @@ docker pull graphprotocol/graph-node:latest
 
 ضمن ال Subgraph ، تتم معالجة الأحداث دائمًا بالترتيب الذي تظهر به في الكتل ، بغض النظر عما إذا كان ذلك عبر عقود متعددة أم لا.
 
-### 13. هل من الممكن التفريق بين الشبكات (mainnet، Kovan، Ropsten، local) من داخل معالجات الأحداث؟
+### 13. هل من الممكن التفريق بين الشبكات (mainnet، Goerli، local) من داخل معالجات الأحداث؟
 
 نعم. يمكنك القيام بذلك عن طريق استيراد `graph-ts` كما في المثال أدناه:
 
@@ -108,9 +108,7 @@ curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"or
 في ال Hosted Service ، يتم دعم الشبكات التالية:
 
 - Ethereum mainnet
-- Kovan
 - Rinkeby
-- Ropsten
 - Goerli
 - PoA-Core
 - PoA-Sokol
@@ -133,7 +131,7 @@ curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"or
 - Arbitrum One
 - (Arbitrum Testnet (on Rinkeby
 - Optimism
-- (Optimism Testnet (on Kovan
+- (Optimism Testnet (on Goerli)
 
 هناك عمل قيد التقدم من أجل دمج ال blockchain الأخرى ، يمكنك قراءة المزيد في مرجعنا: [RFC-0003: Multi-Blockchain Support](https://github.com/graphprotocol/rfcs/pull/8/files).
 

pages/ar/developing/developer-faqs.mdx

@@ -11,9 +11,7 @@ The following networks are supported in beta on the Hosted Service:
 ### Ethereum
 
 - `mainnet`
-- `kovan`
 - `rinkeby`
-- `ropsten`
 - `goerli`
 - `poa-core`
 - `poa-sokol`
@@ -34,7 +32,7 @@ The following networks are supported in beta on the Hosted Service:
 - `arbitrum-one`
 - `arbitrum-rinkeby`
 - `optimism`
-- `optimism-kovan`
+- `optimism-goerli`
 - `aurora`
 - `aurora-testnet`
 - `boba`
@@ -148,7 +146,7 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 **Note:** You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `ropsten` networks, and this is your `subgraph.yaml`:
+Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `goerli` networks, and this is your `subgraph.yaml`:
 
 ```yaml
 # ...
@@ -172,7 +170,7 @@ This is what your networks config file should look like:
       "address": "0x123..."
     }
   },
-  "ropsten": {
+  "goerli": {
     "Gravity": {
       "address": "0xabc..."
     }
@@ -184,20 +182,20 @@ Now we can run one of the following commands:
 
 ```sh
 # Using default networks.json file
-yarn build --network ropsten
+yarn build --network goerli
 
 # Using custom named file
-yarn build --network ropsten --network-file path/to/config
+yarn build --network goerli --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `ropsten` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+The `build` command will update your `subgraph.yaml` with the `goerli` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
 
 ```yaml
 # ...
 dataSources:
   - kind: ethereum/contract
     name: Gravity
-    network: ropsten
+    network: goerli
     source:
       address: '0xabc...'
       abi: Gravity
@@ -211,17 +209,17 @@ Now you are ready to `yarn deploy`.
 
 ```sh
 # Using default networks.json file
-yarn deploy --network ropsten
+yarn deploy --network goerli
 
 # Using custom named file
-yarn deploy --network ropsten --network-file path/to/config
+yarn deploy --network goerli --network-file path/to/config
 ```
 
 ### Using subgraph.yaml template
 
 One solution for older graph-cli versions that allows to parameterize aspects like contract addresses is to generate parts of it using a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Ropsten using different contract addresses. You could then define two config files providing the addresses for each network:
+To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Goerli using different contract addresses. You could then define two config files providing the addresses for each network:
 
 ```json
 {
@@ -234,7 +232,7 @@ and
 
 ```json
 {
-  "network": "ropsten",
+  "network": "goerli",
   "address": "0xabc..."
 }
 ```
@@ -264,7 +262,7 @@ In order to generate a manifest to either network, you could add two additional
   "scripts": {
     ...
     "prepare:mainnet": "mustache config/mainnet.json subgraph.template.yaml > subgraph.yaml",
-    "prepare:ropsten": "mustache config/ropsten.json subgraph.template.yaml > subgraph.yaml"
+    "prepare:goerli": "mustache config/goerli.json subgraph.template.yaml > subgraph.yaml"
   },
   "devDependencies": {
     ...
@@ -273,14 +271,14 @@ In order to generate a manifest to either network, you could add two additional
 }
 ```
 
-To deploy this subgraph for mainnet or Ropsten you would now simply run one of the two following commands:
+To deploy this subgraph for mainnet or Goerli you would now simply run one of the two following commands:
 
 ```sh
 # Mainnet:
 yarn prepare:mainnet && yarn deploy
 
-# Ropsten:
-yarn prepare:ropsten && yarn deploy
+# Goerli:
+yarn prepare:goerli && yarn deploy
 ```
 
 A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).

pages/en/deploying/deploying-a-subgraph-to-hosted.mdx

@@ -6,7 +6,7 @@ title: What is the Hosted Service?
 
 This section will walk you through deploying a subgraph to the [Hosted Service](https://thegraph.com/hosted-service/).
 
-If you don't have an account on the Hosted Service, you can sign up with your Github account. Once you authenticate, you can start creating subgraphs through the UI and deploying them from your terminal. Graph Node supports a number of Ethereum testnets (Rinkeby, Ropsten, Kovan) in addition to mainnet.
+If you don't have an account on the Hosted Service, you can sign up with your Github account. Once you authenticate, you can start creating subgraphs through the UI and deploying them from your terminal. Graph Node supports a number of Ethereum testnets (Rinkeby, Goerli) in addition to mainnet.
 
 ## Create a Subgraph
 

pages/en/deploying/hosted-service.mdx

@@ -62,7 +62,7 @@ If only one entity is created during the event and if there's nothing better ava
 
 Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
 
-### 13. Is it possible to differentiate between networks (mainnet, Kovan, Ropsten, local) from within event handlers?
+### 13. Is it possible to differentiate between networks (mainnet, Goerli, local) from within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 

pages/en/developing/developer-faqs.mdx

@@ -98,7 +98,7 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 **Note:** You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `ropsten` networks, and this is your `subgraph.yaml`:
+Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `goerli` networks, and this is your `subgraph.yaml`:
 
 ```yaml
 # ...
@@ -122,7 +122,7 @@ This is what your networks config file should look like:
       "address": "0x123..."
     }
   },
-  "ropsten": {
+  "goerli": {
     "Gravity": {
       "address": "0xabc..."
     }
@@ -134,20 +134,20 @@ Now we can run the following command:
 
 ```sh
 # Using default networks.json file
-yarn build --network ropsten
+yarn build --network goerli
 
 # Using custom named file
-yarn build --network ropsten --network-file path/to/config
+yarn build --network goerli --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `ropsten` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+The `build` command will update your `subgraph.yaml` with the `goerli` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
 
 ```yaml
 # ...
 dataSources:
   - kind: ethereum/contract
     name: Gravity
-    network: ropsten
+    network: goerli
     source:
       address: '0xabc...'
       abi: Gravity
@@ -161,7 +161,7 @@ Now you are ready to `yarn deploy`
 
 One solution for older graph-cli versions that allows to parameterize aspects like contract addresses is to generate parts of it using a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Ropsten using different contract addresses. You could then define two config files providing the addresses for each network:
+To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Goerli using different contract addresses. You could then define two config files providing the addresses for each network:
 
 ```json
 {
@@ -174,7 +174,7 @@ and
 
 ```json
 {
-  "network": "ropsten",
+  "network": "goerli",
   "address": "0xabc..."
 }
 ```
@@ -204,7 +204,7 @@ In order generate a manifest to either network, you could add two additional com
   "scripts": {
     ...
     "prepare:mainnet": "mustache config/mainnet.json subgraph.template.yaml > subgraph.yaml",
-    "prepare:ropsten": "mustache config/ropsten.json subgraph.template.yaml > subgraph.yaml"
+    "prepare:goerli": "mustache config/goerli.json subgraph.template.yaml > subgraph.yaml"
   },
   "devDependencies": {
     ...
@@ -213,14 +213,14 @@ In order generate a manifest to either network, you could add two additional com
 }
 ```
 
-To deploy this subgraph for mainnet or Ropsten you would now simply run one of the two following commands:
+To deploy this subgraph for mainnet or Goerli you would now simply run one of the two following commands:
 
 ```sh
 # Mainnet:
 yarn prepare:mainnet && yarn deploy
 
-# Ropsten:
-yarn prepare:ropsten && yarn deploy
+# Goerli:
+yarn prepare:goerli && yarn deploy
 ```
 
 A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).