some updates

Author: idalithb

website/pages/en/deploying/deploying-a-subgraph-to-studio.mdx

@@ -11,26 +11,26 @@ Learn how to deploy your subgraph in Subgraph Studio.
 In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - Create and manage your API keys for specific subgraphs
-- Create your subgraph through Studio UI
-- Deploy your subgraph using the CLI
+- Create your subgraph through the Studio UI
+- Deploy your subgraph using the The Graph CLI
 - Publish your subgraph with the Studio UI
 - Stage your subgraph in the playground environment
 - Integrate your subgraph in staging using the query URL
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can view the following:
+You can also view the following:
 
 - Your user account controls
 - A list of subgraphs you've created
 - A section to manage your API keys
 - A section to manage, view details, and visualize the status of a specific subgraph
 - A section to manage your billing
 
-## Install the Graph CLI
+## Install The Graph CLI
 
 Before deploying, you must install The Graph CLI.
 
-You must have [Node.js](https://nodejs.org/) and a 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 a 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.
 
 **Install with yarn:**
 
@@ -56,13 +56,13 @@ Before deploying your subgraph you need to create a subgraph in [Subgraph Studio
 3. After you sign in, your unique deploy key will be displayed on your account home page.
    - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
 
-> Important: You need API keys to query subgraphs
+> Important: You need an API key to query subgraphs
 
 #### How to Create a Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [quick-start](/quick-start/)
+> For additional written detail, review the [Quick-Start](/quick-start/).
 
 #### Subgraph Compatibility with The Graph Network
 
@@ -76,7 +76,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 ## Initialize your Subgraph
 
-Once your subgraph has been created in Subgraph Studio, you can initialize the subgraph code through the CLI using this command:
+Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
 graph init --studio <SUBGRAPH_SLUG>
@@ -90,7 +90,7 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find on your "My Subgraphs" page or under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
@@ -112,12 +112,12 @@ graph deploy --studio <SUBGRAPH_SLUG>
 
 After running this command, 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 are free to choose any string as version such as:`v1`, `version1`, `asdf`.
+- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
 - The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
 
 ## Testing your Subgraph
 
-After deploying, you can test/stage your subgraph in Subgraph Studio, deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready.
+After deploying, you can test/stage your subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready.
 
 Use Subgraph Studio’s playground to check your subgraph logs and see where a subgraph fails.
 
@@ -129,18 +129,18 @@ In order to publish your subgraph successfully, review [publishing a subgraph](/
 
 If you want to update your subgraph, you can do the following:
 
-- You can deploy a new version to the Studio using the CLI (it will only be private at this point).
+- You can deploy a new version to Studio using the CLI (it will only be private at this point).
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that curators can start signaling on and Indexers can index.
 
-You can also update your subgraphs' metadata without publishing a new version. You can update your subgraph details in the Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in the Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
-> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if curators have not signaled on it. For more information on the risks of curation, please read more [here](/network/curating/).
+> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information on the risks of curation, please read more [here](/network/curating/).
 
 ## Automatic Archiving of Subgraph Versions
 
-Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in the Studio UI.
+Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Studio UI.
 
-> Note: Previous versions of non-published subgraphs deployed to the Studio will be automatically archived.
+> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
 
 ![Subgraph Studio - Unarchive](/img/Unarchive.png)