updates

Author: idalithb

nginx.conf

@@ -94,7 +94,7 @@ http {
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$    $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/    permanent;
         rewrite ^/docs/en/substreams/(?!index\.).+$                                     https://substreams.streamingfast.io                                         permanent;
         rewrite ^/docs/en/firehose/(?!index\.).+$                                       https://firehose.streamingfast.io                                           permanent;
-
+        rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/deploying-a-subgraph-to-studio/$    $scheme://$http_host/docs/$1/deploying/deploy-using-subgraph-studio//    permanent;
         # Temporary redirects (302)
         rewrite ^/docs/en/querying/graph-client/$                                       $scheme://$http_host/docs/en/querying/graph-client/README/                  redirect;
         rewrite ^/docs/en/developing/graph-ts/$                                         $scheme://$http_host/docs/en/developing/graph-ts/README/                    redirect;

website/pages/en/deploying/_meta.js

@@ -1,4 +1,4 @@
 export default {
-  'deploying-a-subgraph-to-studio': '',
+  'deploy-using-subgraph-studio': '',
   'subgraph-studio-faqs': '',
 }

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

@@ -2,23 +2,23 @@
 title: Deploy Using Subgraph Studio
 ---
 
-Learn how to deploy your subgraph in Subgraph Studio.
+Learn how to deploy your subgraph to Subgraph Studio.
 
 > Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test 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:
 
+- View a list of subgraphs you've created
+- Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
+- Restrict your API keys to specific domains and allow only certain Indexers to query with them
 - Create your subgraph through the Studio UI
 - Deploy your subgraph using the The Graph CLI
-- Integrate your subgraph in staging using the query URL
-- Publish your subgraph with the Studio UI
 - Test your subgraph in the playground environment
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
+- Integrate your subgraph in staging using the development query URL
+- Publish your subgraph with the Studio UI
 - Manage your billing
 
 ## Install The Graph CLI
@@ -39,9 +39,9 @@ yarn global add @graphprotocol/graph-cli
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create your Subgraph
+## Create Your Subgraph
 
-Before deploying your subgraph you need to create a subgraph in [Subgraph Studio](https://thegraph.com/studio/).
+Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -67,7 +67,7 @@ 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 its code through the CLI using this command:
 
@@ -108,17 +108,17 @@ 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`, 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
+## Testing Your Subgraph
 
 After deploying, you can test 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 to check the logs on the dashboard and look for any errors with your subgraph.
 
-## 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
+## Versioning Your Subgraph with the CLI
 
 If you want to update your subgraph, you can do the following:
 
@@ -132,7 +132,7 @@ You can also update your subgraph's metadata without publishing a new version. Y
 
 ## 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 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 Subgraph Studio.
 
 > Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.