Fixing Command (#816)

* removing --studio from all commands

Author: idalithb

website/pages/en/cookbook/arweave.mdx

@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

website/pages/en/cookbook/cosmos.mdx

@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

website/pages/en/cookbook/near.mdx

@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

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

@@ -70,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 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>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -86,7 +86,7 @@ Before you can deploy your subgraph to Subgraph Studio, you need to log into you
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
@@ -98,7 +98,7 @@ Once you are ready, you can deploy your subgraph to Subgraph Studio.
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.

website/pages/en/developing/creating-a-subgraph.mdx

@@ -66,7 +66,7 @@ graph init \
 The following command initializes a new project from an example subgraph:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG> --from-example=example-subgraph
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
 ```
 
 - The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.

website/pages/en/querying/querying-from-an-application.mdx

@@ -26,7 +26,6 @@ With your GraphQL endpoint, you can use various GraphQL Client libraries to quer
 
 ### Graph Client
 
-
 The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query

website/pages/en/quick-start.mdx

@@ -57,7 +57,7 @@ For additional information on subgraph creation and the Graph CLI, see [Creating
 The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 > Note: If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
@@ -113,9 +113,9 @@ Remember, deploying is not the same as publishing.
 
     ```sh
 
-    graph auth --studio <DEPLOY_KEY>
+    graph auth <DEPLOY_KEY>
 
-    graph deploy --studio <SUBGRAPH_SLUG>
+    graph deploy <SUBGRAPH_SLUG>
     ```
 
 - The CLI will ask for a version label.