updating call out

Author: idalithb

website/src/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx

@@ -4,6 +4,8 @@ title: Deploying Using Subgraph Studio
 
 Learn how to deploy your Subgraph to Subgraph Studio.
 
+> [!IMPORTANT] Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones.
+
 > Note: When you deploy a Subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a Subgraph, you're publishing it onchain.
 
 ## Subgraph Studio Overview
@@ -87,9 +89,9 @@ graph auth <DEPLOY KEY>
 
 Once you are ready, you can deploy your Subgraph to Subgraph Studio.
 
-> Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network.
+> [!IMPORTANT] Limit: 3 deployed (unpublished) Subgraphs per account. Publish or archive to free a slot.
 
-> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones.
+> [!NOTE] Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network.
 
 Use the following CLI command to deploy your Subgraph: