From f23d3182a63f5b4a1cfe00b575aff50f05ff1a25 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 13:10:35 +0000
Subject: [PATCH 1/2] docs: clarify pod shutdown behavior and MCP network
 volume attachment

---
 get-started/mcp-servers.mdx | 14 ++++++++++++++
 pods/manage-pods.mdx        |  4 ++++
 2 files changed, 18 insertions(+)

diff --git a/get-started/mcp-servers.mdx b/get-started/mcp-servers.mdx
index ab38c90e3..2c0c52d37 100644
--- a/get-started/mcp-servers.mdx
+++ b/get-started/mcp-servers.mdx
@@ -179,6 +179,20 @@ Create a new Runpod Pod with the following specifications:
 - Cloud Type: SECURE
 ```
 
+To attach an existing [network volume](/storage/network-volumes) at Pod creation, include its ID and mount path. The MCP server forwards these to the REST API's `networkVolumeId` and `volumeMountPath` fields on [`POST /pods`](/api-reference/pods/POST/pods):
+
+```
+Create a new Runpod Pod with the following specifications:
+- Name: ml-training-pod
+- Image: runpod/pytorch:2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04
+- GPU Type: NVIDIA GeForce RTX 4090
+- GPU Count: 1
+- Network Volume ID: vol_abc123
+- Volume Mount Path: /workspace
+```
+
+The network volume's data center constrains where the Pod can run, so pick a GPU type that is available in the volume's region.
+
 ```
 Create a Runpod Serverless endpoint with the following configuration:
 - Name: image-generation-endpoint
diff --git a/pods/manage-pods.mdx b/pods/manage-pods.mdx
index 626ade90c..5b8629570 100644
--- a/pods/manage-pods.mdx
+++ b/pods/manage-pods.mdx
@@ -107,6 +107,10 @@ You'll still be charged for [volume disk storage](/pods/storage/types#volume-dis
 When using a [network volume](/storage/network-volumes), your `/workspace` data is preserved whether you stop or terminate the Pod.
 </Tip>
 
+<Warning>
+Linux commands like `shutdown`, `poweroff`, and `halt` do not stop a Pod. Pods run as containers, so those commands only affect the container's init process and can cause the container to restart instead of stopping the Pod. To stop a Pod from inside itself, use `runpodctl pod stop $RUNPOD_POD_ID` from the CLI tab below, or call the REST API from within the Pod.
+</Warning>
+
 <Tabs>
 <Tab title="Web">
 

From b880a4dbdc281b3162b2c0ca30b67c0ea45a64f3 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 13:11:34 +0000
Subject: [PATCH 2/2] docs: tighten pod shutdown warning wording

---
 pods/manage-pods.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pods/manage-pods.mdx b/pods/manage-pods.mdx
index 5b8629570..9c88873e4 100644
--- a/pods/manage-pods.mdx
+++ b/pods/manage-pods.mdx
@@ -108,7 +108,7 @@ When using a [network volume](/storage/network-volumes), your `/workspace` data
 </Tip>
 
 <Warning>
-Linux commands like `shutdown`, `poweroff`, and `halt` do not stop a Pod. Pods run as containers, so those commands only affect the container's init process and can cause the container to restart instead of stopping the Pod. To stop a Pod from inside itself, use `runpodctl pod stop $RUNPOD_POD_ID` from the CLI tab below, or call the REST API from within the Pod.
+Linux commands like `shutdown`, `poweroff`, and `halt` do not stop a Pod. Pods run as containers, not VMs, so these commands only affect the container's init process. The container may restart instead of stopping. To stop a Pod from inside itself, use `runpodctl pod stop $RUNPOD_POD_ID` from the CLI tab below, or call the REST API.
 </Warning>
 
 <Tabs>