diff --git a/website/pages/en/subgraphs/querying/from-an-application.mdx b/website/pages/en/subgraphs/querying/from-an-application.mdx
index 6a3a13b8d141..681f6e6ba8d5 100644
--- a/website/pages/en/subgraphs/querying/from-an-application.mdx
+++ b/website/pages/en/subgraphs/querying/from-an-application.mdx
@@ -6,21 +6,27 @@ Learn how to query The Graph from your application.
 
 ## Getting GraphQL Endpoints
 
-Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will receive two GraphQL API endpoints that look like this:
+During the development process, you will receive a GraphQL API endpoint at two different stages: one for testing in Subgraph Studio, and another for making queries to The Graph Network in production.
 
 ### Subgraph Studio Endpoint
 
+After deploying your subgraph to [Subgraph Studio](https://thegraph.com/docs/en/subgraphs/developing/deploying/using-subgraph-studio/), you will receive an endpoint that looks like this:
+
 ```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-### Network Endpoint
+> This endpoint is intended for testing purposes **only** and is rate-limited.
+
+### The Graph Network Endpoint
+
+After publishing your subgraph to the network, you will receive an endpoint that looks like this: :
 
 ```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
+> This endpoint is intended for active use on the network. It allows you to use various GraphQL client libraries to query the subgraph and populate your application with indexed data.
 
 ## Using Popular GraphQL Clients