updating suggested changes

Author: idalithb

website/pages/en/quick-start.mdx

@@ -2,19 +2,18 @@
 title: Quick Start
 ---
 
-This guide walks you through the basics of publishing and querying a subgraph on The Graph easily.
+Learn how to easily publish and query a subgraph on The Graph.
 
-**Prerequisites for this guide:**
+## Prerequisites for this guide
 
 - A crypto wallet
-- A smart contract address on the [supported network](/developing/supported-networks/) of your choice
-- An API key
+- A smart contract address on one of the [supported networks](/developing/supported-networks/)
 
 ## Step-by-Step
 
 ### 1. Install the Graph CLI
 
-You must have [Node.js](https://nodejs.org/en) and package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use the Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+You must have [Node.js](https://nodejs.org/) and package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use the Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
 On your local machine, run one of the following commands:
 
@@ -30,26 +29,30 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-### 2. Create your subgraph
+### 2. Create Your Subgraph
 
 If your contract has events, the `init` command will automatically create a scaffold of a subgraph.
 
-#### Create via CLI
+#### Create via Graph CLI
 
-Use the following command to create a subgraph in Subgraph Studio using CLI: `init --product subgraph-studio`
+Use the following command to create a subgraph in Subgraph Studio using CLI:
 
-#### **Create via Subgraph Studio**
+```sh
+init --product subgraph-studio
+```
+
+#### Create via Subgraph Studio
 
-Subgraph Studio is a staging environment where you can create, manage, deploy, and publish subgraphs and API Keys.
+Subgraph Studio has a staging environment where you can create, manage, deploy, and publish subgraphs and API Keys.
 
-1. Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
-2. Click “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+1.  Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+2.  Click “Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-For additional information on subgraph creation and CLI, see [Creating a Subgraph](developing/creating-a-subgraph).
+For additional information on subgraph creation and CLI, see [Creating a Subgraph](/developing/creating-a-subgraph).
 
 ### 3. Initialize Your Subgraph
 
-#### **From an existing contract**
+#### From an existing contract
 
 The following command initializes your subgraph from an existing contract:
 
@@ -63,58 +66,58 @@ You can find commands for your specific subgraph on the subgraph page in [Subgra
 
 When you initialize your subgraph, the CLI tool will ask you for the following information:
 
-- Protocol: Choose the protocol your subgraph will be indexing data from
+- Protocol: Choose the protocol your subgraph will be indexing data from.
 - Subgraph slug: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: Choose your local directory
-- Ethereum network(optional): You may need to specify which EVM-compatible network your subgraph will be indexing data from
-- Contract address: Locate the smart contract address you’d like to query data from
-- ABI: If the ABI is not auto-populated, you will need to input it manually as a JSON file
+- Directory to create the subgraph in: Choose your local directory.
+- Ethereum network (optional): You may need to specify which EVM-compatible network your subgraph will be indexing data from.
+- Contract address: Locate the smart contract address you’d like to query data from.
+- ABI: If the ABI is not auto-populated, you will need to input it manually as a JSON file.
 - Start Block: You should input the start block to optimize subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed.
-- Contract Name: Input the name of your contract
-- Index contract events as entities: It is suggested that you set this to true, as it will automatically add mappings to your subgraph for every emitted event
-- Add another contract(optional): You can add another contract.
+- Contract Name: Input the name of your contract.
+- Index contract events as entities: It is suggested that you set this to true, as it will automatically add mappings to your subgraph for every emitted event.
+- Add another contract (optional): You can add another contract.
 
 See the following screenshot for an example for what to expect when initializing your subgraph:
 
 ![Subgraph command](/img/subgraph-init-example.png)
 
-### 4. Write your subgraph
+### 4. Write Your Subgraph
 
 The `init` command in the previous step creates a scaffold subgraph that you can use as a starting point to build your subgraph.
 
 When making changes to the subgraph, you will mainly work with three files:
 
-- Manifest (`subgraph.yaml`)- defines what datasources your subgraphs will index.
+- Manifest (`subgraph.yaml`) - defines what datasources your subgraphs will index.
 - Schema (`schema. graphql`) - defines what data you wish to retrieve from the subgraph.
 - AssemblyScript Mappings (`mapping.ts`) - translates data from your datasources to the entities defined in the schema.
 
 For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-### 5. Deploy to your subgraph
+### 5. Deploy Your Subgraph
 
 Remember, deploying is not the same as publishing.
 
 - When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
 - When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
-1. Once your subgraph is written, run the following commands:
+1.  Once your subgraph is written, run the following commands:
 
-   ```sh
-   $ graph codegen
-   $ graph build
-   ```
+    ```sh
+    graph codegen
+    graph build
+    ```
 
-2. Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+2.  Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
 
-   ```sh
-   $ graph auth --studio <DEPLOY_KEY>
-   $ graph deploy --studio <SUBGRAPH_SLUG>
-   ```
+    ```sh
+    graph auth --studio <DEPLOY_KEY>
+    graph deploy --studio <SUBGRAPH_SLUG>
+    ```
 
 - The CLI will ask for a version label.
-  - It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1.` That said, you can choose any string as version such as: `v1, version1, asdf`.
+  - It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. That said, you can choose any string for the version such as: `v1, version1, asdf`, ect.
 
-### 6. Review your subgraph
+### 6. Review Your Subgraph
 
 If you’d like to examine your subgraph before publishing it to the network, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following:
 
@@ -125,46 +128,56 @@ If you’d like to examine your subgraph before publishing it to the network, yo
 
 ![Subgraph logs](/img/subgraph-logs-image.png)
 
-### 7. Publish Your Subgraph to The Graph
+### 7. Publish Your Subgraph to The Graph Network
 
-Publishing a subgraph to the decentralized network makes it available for [Curators](/network/curating/) to begin curating it and [Indexers](/network/indexing/) to index it.
+Publishing a subgraph to the decentralized network makes it available for [Curators](/network/curating/) to begin curating it and [Indexers](/network/indexing/) to begin indexing it.
 
 #### Publishing with Subgraph Studio
 
-1. To publish your subgraph, click the publish button in the dashboard.
-2. Select the network to which you would like to publish your subgraph.
-   - Subgraphs are published to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](https://thegraph.com/docs/en/arbitrum/arbitrum-faq/).
+1.  To publish your subgraph, click the Publish button in the dashboard.
+2.  Select the network to which you would like to publish your subgraph.
 
 #### Publishing from the CLI
 
-As of version 0.73.0, you can also publish your subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
+As of version 0.73.0, you can also publish your subgraph with the Graph CLI.
+
+1.  Open the `graph-cli`.
+2.  Use the following commands:
+
+```sh
+graph codegen && graph build
+```
+
+Then,
+
+```sh
+graph publish
+```
 
-1. Open the `graph-cli`.
-2. Use the following commands: `graph codegen && graph build` then `graph publish`.
-3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized subgraph to a network of your choice.
+3.  A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized subgraph to a network of your choice.
 
 ![cli-ui](/img/cli-ui.png)
 
-To customize your deployment see [publishing a subgraph](/publishing/publishing-a-subgraph/)
+To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/).
 
 #### Adding signal to your subgraph
 
-1. To attract indexers to query your subgraph, you should add GRT curation signal to it.
+1.  To attract indexers to query your subgraph, you should add GRT curation signal to it.
 
-   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraphs.
+    - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraphs.
 
-2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
+2.  If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-   - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks.
+    - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks.
 
 To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this button:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
 ![Subgraph publish](/img/publish-and-signal-tx.png)
 
 ### 8. Query Your Subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking the query button.
+Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking the Query button.
 
 For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).