edits

Author: idalithb

website/pages/en/network/developing.mdx

@@ -2,7 +2,7 @@
 title: Developing
 ---
 
-Learn developer fundamentals and review the basics of a subgraph’s lifecycle. To start coding right away and build on The Graph, go to [Developer Quick Start](/quick-start/).
+To start coding right away and build on The Graph, go to [Developer Quick Start](/quick-start/).
 
 ## Overview
 
@@ -17,11 +17,11 @@ On The Graph, you can:
 
 - [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
+### Developer Actions
 
 - Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
 - Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
-- Deploy, publish, and signal your subgraphs within The Graph Network.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
 ## Subgraph Specifics
 
@@ -37,57 +37,54 @@ A subgraph primarily consists of the following files:
 
 Learn the detailed specifics to [create a subgraph](/developing/creating-a-subgraph/).
 
-### Subgraph Lifecycle
+## Subgraph Lifecycle
 
-Here is a general view of a subgraph’s lifecycle:
+Here is a general overview of a subgraph’s lifecycle:
 
 ![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
-### Context for Subgraph Development
+### Build locally
 
 Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs in The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs that deploy to The Graph Network.
 
-## Deploy to Subgraph Studio
+### 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:
 
 - 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.
 
-## Publish to the Network
+### Publish to the Network
 
-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.
+When you're 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 associated metadata, which provides other network participants with useful context and information.
 
-## Add Curation Signal for Indexing
+### Add Curation Signal for Indexing
 
 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?
+#### What is signal?
 
-- Signal is locked GRT associated with a given subgraph. It indicates to indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
 - Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
 
-## Querying & Application Development
+### Querying & Application Development
 
 Once a subgraph has been processed by Indexers and is ready to [query](/querying/querying-the-graph/), developers can start using their subgraph in their dapps.
 
 - When a query is made, The Graph Network selects an Indexer who has processed the subgraph to serve that query. Query fees are paid in GRT.
 - Developers must generate an API key and fund it with GRT to make queries, which can be done in [Subgraph Studio](https://thegraph.com/studio/).
-- Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain.
-  - Subgraph Studio provides API key usage data.
-- Developers can express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
 
-## Updating Subgraphs
+### Updating Subgraphs
 
 To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
 
 - If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
 - This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
 
-## Deprecating & Transferring Subgraphs
+### 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).
+If you no longer need a published subgraph, you can [deprecate or transfer a subgraph](managing/transfer-and-deprecate-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).