Updated pricing.mdx to include capacity update behavior with suspended endpoint groups

documentation/serverless/pricing.mdx

@@ -34,13 +34,22 @@ Visit the [Billing Help](/documentation/reference/billing#ugwiY) page to see det
 
 ## Suspending an Endpoint
 
-By suspending an Endpoint, the Endpoint will no longer recruit any new GPU instances, but will continue to use the instances it currently has. This is a way to cap the 
-number of instances an Endpoint can manage, and therefore limit costs. 
+When an Endpoint is **suspended**:
+- The Serverless Engine will no longer manage the GPU instances contained within the Endpoint.
+- GPU instances in this Endpoint will still be able to receive requests. 
 
 ## Stopping an Endpoint
 
-Stopping an Endpoint will pause the recruitment of GPU instances, and put the existing instances into the "Stopped" state, preventing any work from being sent to 
-the Endpoint group. The instances will still charge the small storage cost, but active rental and bandwidth costs will not be charged to the user account. 
+**Stopping** an Endpoint will:
+- Cause the Serverless Engine to no longer manage the GPU instances contained within the Endpoint.
+- Put all existing GPU instances into the Inactive state.
+
+An **Inactive** GPU instance will:
+- Not receive any work. 
+- Not charge GPU compute costs.
+- Charge the user's account for **storage** and **bandwidth**. 
+
+
 
 ## Billing by Instance State