Edits

Author: idalithb

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

@@ -4,18 +4,19 @@ title: Deploy Using Subgraph Studio
 
 Learn how to deploy your subgraph in Subgraph Studio.
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to stage it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you are publishing it on-chain.
+> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to stage it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
 
 ## Subgraph Studio Overview
 
 In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - Create and manage your API keys for specific subgraphs
-- Create your subgraph
-- Authenticate your account from the CLI
-- Deploy your subgraph
+- Create your subgraph through Studio UI
+- Deploy your subgraph using the 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:
 
@@ -43,23 +44,21 @@ yarn global add @graphprotocol/graph-cli
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create your subgraph
+## Create your Subgraph
 
-### Create an account
+### Create an Account
 
 Before deploying your subgraph you need to create a subgraph in [Subgraph Studio](https://thegraph.com/studio/).
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet.
-   - You can do this via MetaMask, WalletConnect, Coinbase Wallet, or Safe.
-3. After you connect your wallet, your unique deploy key will be displayed on your "My Subgraphs" page or your “subgraph details” page in the Studio.
+2. Connect your wallet to sign in.
+   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
+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.
-4. You can create one or multiple API keys by clicking the API keys tab at the top of your homepage. See image below:
-   - You can limit API keys to a specific domain in the security section.
 
 > Important: You need API keys to query subgraphs
 
-#### How to create a subgraph in Subgraph Studio
+#### How to Create a Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
@@ -75,31 +74,31 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
   - Non-fatal errors
   - Grafting
 
-## Initialize your subgraph
+## Initialize your Subgraph
 
-Once your subgraph has been created in Subgraph Studio you can initialize the subgraph code using this command:
+Once your subgraph has been created in Subgraph Studio, you can initialize the subgraph code through the CLI using this command:
 
 ```bash
 graph init --studio <SUBGRAPH_SLUG>
 ```
 
-You can view the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
 ## Graph Auth
 
-Before can deploy your subgraph to Subgraph Studio, you must login into your account using 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 on your "My Subgraphs" page or under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
 graph auth --studio <DEPLOY KEY>
 ```
 
-## Deploying a subgraph
+## Deploying a Subgraph
 
 Once you are ready, you can deploy your subgraph to Subgraph Studio.
 
@@ -116,14 +115,30 @@ 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`.
 - 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
+## 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.
 
 Use Subgraph Studio’s playground to check your subgraph logs and see where a subgraph fails.
 
-## Publish your subgraph
-
-You are now ready to publish your subgraph!
+## Publish your Subgraph
 
 In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+
+## Versioning your Subgraph with the CLI
+
+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).
+- 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.
+
+> 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.
+
+> Note: Previous versions of non-published subgraphs deployed to the Studio will be automatically archived.