Updating migrating a subgraph (#297)

* Updating migration tut

* Fixing pickle

Author: MichaelMacaulay

pages/en/cookbook/migrating-a-subgraph.mdx

@@ -4,7 +4,7 @@ title: Migrating an Existing Subgraph to The Graph Network
 
 ## Introduction
 
-This is a guide on how to migrate your subgraph from the Hosted Service to The Graph's decentralized network. Migration to The Graph Network has been successful for projects like Opyn, UMA, mStable, Audius, PoolTogether, Livepeer, RAI, Enzyme, DODO, Pickle, and BadgerDAO all of which are relying on data served by Indexers on the network. There are now over 600 subgraphs live on The Graph's decentralized network, generating query fees and actively indexing web3 data.
+This is a guide on how to migrate your subgraph from the Hosted Service to The Graph's decentralized network. Migration to The Graph Network has been successful for projects like Opyn, UMA, mStable, Audius, PoolTogether, Livepeer, RAI, Enzyme, DODO, Pickle, and BadgerDAO all of which are relying on data served by Indexers on the network. There are now over 700 subgraphs live on The Graph's decentralized network, generating query fees and actively indexing web3 data.
 
 The process of migration is quick and your subgraphs will forever benefit from the reliability and performance that you can only get on The Graph Network.
 
@@ -16,6 +16,8 @@ The process of migration is quick and your subgraphs will forever benefit from t
 
 ## Migrating an Existing Subgraph to The Graph Network
 
+> You can find specific commands for your subgraph in the [Subgraph Studio](https://thegraph.com/studio/).
+
 1. Get the latest version of the graph-cli installed:
 
 ```sh
@@ -26,7 +28,7 @@ npm install -g @graphprotocol/graph-cli
 yarn global add @graphprotocol/graph-cli
 ```
 
-Also make sure your `apiVersion` in subgraph.yaml is `0.0.5` or greater.
+Make sure your `apiVersion` in subgraph.yaml is `0.0.5` or greater.
 
 2. Inside the subgraph's main project repository, authenticate the subgraph to deploy and build on the studio:
 
@@ -67,8 +69,8 @@ graph deploy --studio <SUBGRAPH_SLUG>
 
 6. At this point, your subgraph is now deployed on Subgraph Studio, but not yet published to the decentralized network. You can now test the subgraph to make sure it is working as intended using the temporary query URL as seen on top of the right column above. As this name already suggests, this is a temporary URL and should not be used in production.
 
-- Remember that publishing is an on-chain action and will require gas to be paid for in Ethereum - see an example transaction [here](https://etherscan.io/tx/0xd0c3fa0bc035703c9ba1ce40c1862559b9c5b6ea1198b3320871d535aa0de87b). Prices are roughly around 0.0425 ETH at 100 gwei.
-- Any time you need to upgrade your subgraph, you will be charged an upgrade fee. Remember, upgrading is just publishing another version of your existing subgraph on-chain. Because this incurs a cost, it is highly recommended to deploy and test your subgraph on Goerli before deploying to mainnet. It can, in some cases, also require some GRT if there is no signal on that subgraph. In the case there is signal/curation on that subgraph version (using auto-migrate), the taxes will be split.
+- Publishing is an on-chain action and will require gas to be paid for in Ethereum - see an example transaction [here](https://etherscan.io/tx/0xd0c3fa0bc035703c9ba1ce40c1862559b9c5b6ea1198b3320871d535aa0de87b). Prices are roughly around 0.0425 ETH at 100 gwei.
+- Any time you need to upgrade your subgraph, you will be charged an upgrade fee. Upgrading is just publishing another version of your existing subgraph on-chain. Because this incurs a cost, it is highly recommended to deploy and test your subgraph on Goerli before deploying to mainnet. It can, in some cases, also require some GRT if there is no signal on that subgraph. In the case there is signal/curation on that subgraph version (using auto-migrate), the taxes will be split.
 
 7. Publish the subgraph on The Graph's decentralized network by hitting the "Publish" button.
 
@@ -201,7 +203,7 @@ While this is not a live feature in the product UI, you can set your maximum bud
 
 While you get to decide on your query budget, there is no guarantee that an Indexer will be willing to serve queries at that price. If a Gateway can match you to an Indexer willing to serve a query at, or lower than, the price you are willing to pay, you will pay the delta/difference of your budget **and** their price. As a consequence, a lower query price reduces the pool of Indexers available to you, which may affect the quality of service you receive. It's beneficial to have high query fees, as that may attract curation and big-name Indexers to your subgraph.
 
-Remember that it's a dynamic and growing market, but how you interact with it is in your control. There is no maximum or minimum price specified in the protocol or the Gateways. For example, you can look at the price paid by a few of the dapps on the network (on a per-week basis), below. See the last column, which shows query fees in GRT. For example, [Pickle Finance](https://www.pickle.finance/) has 8 requests per second and paid 2.4 GRT for one week.
+Remember that it's a dynamic and growing market, but how you interact with it is in your control. There is no maximum or minimum price specified in the protocol or the Gateways. For example, you can look at the price paid by a few of the dapps on the network (on a per-week basis), below. See the last column, which shows query fees in GRT.
 
 ![QueryFee](/img/QueryFee.png)