Added stop pod network volume info tip (#290)

Co-authored-by: Mo King <[email protected]>

Author: therealadityashankar

pods/manage-pods.mdx

@@ -17,7 +17,7 @@ runpodctl config --apiKey [RUNPOD_API_KEY]
 
 <Tabs>
 <Tab title="Web">
-To create a Pod using the web interface:
+To create a Pod using the Runpod console:
 
 1. Open the [Pods page](https://www.runpod.io/console/pods) in the Runpod console and click the **Deploy** button.
 2. (Optional) Specify a [network volume](/pods/storage/create-network-volumes) if you need to share data between multiple Pods, or to save data for later use.
@@ -70,19 +70,22 @@ With custom templates, you can:
 
 ## Stop a Pod
 
-<Warning>
-
-When a Pod is stopped, data in the container volume is cleared, but data in the `/workspace` directory is preserved. To learn more, see [Storage options](/pods/storage/types).
+<Tip>
+If your Pod has a [network volume](/pods/storage/create-network-volumes) attached, it cannot be stopped, only terminated. When you terminate the Pod, data in the `/workspace` directory will be preserved in the network volume, and you can regain access by deploying a new Pod with the same network volume attached.
+</Tip>
 
-After a Pod is stopped, you will still be charged for its [disk volume storage](/pods/storage/types#disk-volume). If you don't need to retain your Pod environment, you should terminate it completely.
+When a Pod is stopped, data in the container volume is cleared, but data in the `/workspace` directory is preserved. To learn more about how Pod storage works, see [Storage overview](/pods/storage/types).
 
-By stopping a Pod you are releasing the GPU on the machine, and you may be reallocated 0 GPUs when you start the Pod again. For more info, see the [FAQ](/references/faq#why-do-i-have-zero-gpus-assigned-to-my-pod%3F).
+By stopping a Pod you are effectively releasing the GPU on the machine, and you may be reallocated 0 GPUs when you start the Pod again. For more info, see the [FAQ](/references/faq#why-do-i-have-zero-gpus-assigned-to-my-pod%3F).
 
+<Warning>
+After a Pod is stopped, you will still be charged for its [disk volume](/pods/storage/types#disk-volume) storage. If you don't need to retain your Pod environment, you should terminate it completely.
 </Warning>
 
-
 <Tabs>
 <Tab title="Web">
+To stop a Pod:
+
 1. Open the [Pods page](https://www.runpod.io/console/pods).
 2. Find the Pod you want to stop and expand it.
 3. Click the **Stop button** (square icon).
@@ -101,9 +104,10 @@ runpodctl stop pod $RUNPOD_POD_ID
 
 </Tabs>
 
+
 ### Stop a Pod after a period of time
 
-You can also stop a Pod after a specified period of time. The examples below show how to use the CLI and the [web terminal](/pods/connect-to-a-pod#web-terminal) to schedule a Pod to stop after 2 hours of runtime.
+You can also stop a Pod after a specified period of time. The examples below show how to use the CLI or [web terminal](/pods/connect-to-a-pod#web-terminal) to schedule a Pod to stop after 2 hours of runtime.
 
 <Tabs>
 <Tab title="Command line">
@@ -136,6 +140,8 @@ Pods start as soon as they are created, but you can resume a Pod that has been s
 
 <Tabs>
 <Tab title="Web">
+To start a Pod:
+
 1. Open the [Pods page](https://www.runpod.io/console/pods).
 2. Find the Pod you want to start and expand it.
 3. Click the **Start** button (play icon).
@@ -157,12 +163,14 @@ runpodctl start pod $RUNPOD_POD_ID
 
 <Warning>
 
-Terminating a Pod permanently deletes all data outside of a [network volume](/pods/storage/create-network-volumes). Be sure to export or download any data that you'll need to access again.
+Terminating a Pod permanently deletes all associated data that isn't stored in a [network volume](/pods/storage/create-network-volumes). Be sure to export or download any data that you'll need to access again.
 
 </Warning>
 
 <Tabs>
 <Tab title="Web">
+To terminate a Pod:
+
 1. Open the [Pods page](https://www.runpod.io/console/pods).
 2. Find the Pod you want to terminate and expand it.
 3. [Stop the Pod](#stop-a-pod) if it's running.