Editing Quick Start (#823)

* Edit Quick Start

* tiny copy change

* Update website/pages/en/quick-start.mdx

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

---------

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

Author: MichaelMacaulay

website/pages/en/quick-start.mdx

@@ -66,20 +66,20 @@ You can find commands for your specific subgraph on the subgraph page in [Subgra
 
 When you initialize your subgraph, the CLI will ask you for the following information:
 
-- 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.
-- 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.
+- **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**: Choose a directory to create your subgraph in.
+- **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.
 
 See the following screenshot for an example for what to expect when initializing your subgraph:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![Subgraph command](/img/CLI-Example.png)
 
 ### 4. Write your subgraph