adjustments

Author: idalithb

website/pages/en/network/developing.mdx

@@ -10,12 +10,12 @@ As a developer, you need important data to build and power your dapps. Querying
 
 On The Graph, you can:
 
-1.  Create, deploy and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
 2.  Use GraphQL to query live subgraphs and power dapps.
 
 ### What is GraphQL?
 
-- [GraphQL](/querying/graphql-api/)is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
 ### Developer Capabilities
 
@@ -49,7 +49,7 @@ Great subgraphs start with a local development environment and unit tests. Devel
 
 ## Deploy to Subgraph Studio
 
-Once defined, a subgraph can be deployed to [Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
 
 - Use its staging environment to index the deployed subgraph and make it available for review.
 - Verify that your subgraph doesn't have any indexing errors and works as expected.
@@ -59,12 +59,12 @@ Once defined, a subgraph can be deployed to [Subgraph Studio](/deploying/deployi
 When you are happy with your subgraph, you can put it into production and [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. This ensures Indexers can index it.
 
 - This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
-- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-and-deprecate-a-subgraph) by sending the NFT.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-and-deprecate-a-subgraph/) by sending the NFT.
 - Published subgraphs have associated metadata, which provides other network participants with useful context and information.
 
-## Add Signal for Indexing
+## Add Curation Signal for Indexing
 
-Published subgraphs are unlikely to be picked up by Indexers without signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
 
 ### What is signal?
 
@@ -91,10 +91,3 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa
 ## Deprecating & Transferring Subgraphs
 
 If you no longer need a published subgraph, you can deprecate or transfer a subgraph. Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/). To deprecate or transfer a subgraph, check out [this guide](/managing/transfer-and-deprecate-a-subgraph/#deprecating-a-subgraph).
-
-## Network Economics
-
-As a developer, you can do any of the following:
-
-- Lock up GRT to encourage indexing and querying subgraphs.
-- Burn GRT whenever a subgraph is updated.