minor fix to history PATCH documentation

Author: dtroberts

api-usage-docs/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-A subscription connects a data source product, a storage destination, and data source credentials (remote identity). This guide walks you through the full sequence — from looking up your account details to optionally backfilling historical data.
+A subscription connects a data source product, data source credentials (remote identity), and a storage destination. This guide walks you through the full sequence — from looking up your account details to optionally backfilling historical data.
 
 ---
 

api-usage-docs/history-api.md

@@ -120,10 +120,10 @@ GET https://service.api.openbridge.io/service/history/production/history/status/
 
 ### Update Transaction Status
 
-Updates the status of a specific transaction. The primary use case is cancellation.
+Updates the status of the specified history transaction. The primary use case is cancellation.
 
 ```
-PATCH https://service.api.openbridge.io/service/history/production/history/status/{transaction_id}
+PATCH https://service.api.openbridge.io/service/history/production/history/{transaction_id}
 ```
 
 **Request body:**
@@ -142,6 +142,30 @@ PATCH https://service.api.openbridge.io/service/history/production/history/statu
 
 ---
 
+### Update Transaction Status by Subscription ID
+
+Updates the status of all history transactions associated with the specified subscription. The primary use case is cancellation.
+
+```
+PATCH https://service.api.openbridge.io/service/history/production/history/status/{subscription_id}
+```
+
+**Request body:**
+
+```json
+{
+  "data": {
+    "type": "HistoryTransaction",
+    "id": 999999,
+    "attributes": {
+      "status": "cancelled"
+    }
+  }
+}
+```
+
+---
+
 ### Get Max Request Metadata
 
 Returns the maximum number of history requests permitted.