diff --git a/windows/deployment/update/deployment-service-drivers.md b/windows/deployment/update/deployment-service-drivers.md
index 19692f9cba..45814a4275 100644
--- a/windows/deployment/update/deployment-service-drivers.md
+++ b/windows/deployment/update/deployment-service-drivers.md
@@ -90,7 +90,7 @@ Response returning the policy, without any additional settings specified, that h
 
 ```json
 HTTP/1.1 202 Accepted
-Content-type: application/json
+content-type: application/json
 {
   "@odata.context": "https://graph.microsoft.com/beta/$metadata#admin/windows/updates/updatePolicies/$entity",
   "id": "9011c330-1234-5678-9abc-def012345678",
@@ -119,8 +119,7 @@ To create a policy with additional settings, in the request body:
    ```msgraph-interactive
    POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies
    content-type: application/json
-   
-   Content-length: 967
+      
    {
      "@odata.type": "#microsoft.graph.windowsUpdates.updatePolicy",
      "audience": {
@@ -139,17 +138,7 @@ To create a policy with additional settings, in the request body:
          },
          "durationBeforeDeploymentStart": "P7D"
        }
-     ],
-     "deploymentSettings": {
-       "@odata.type": "microsoft.graph.windowsUpdates.deploymentSettings",
-       "schedule": {
-         "gradualRollout": {
-           "@odata.type": "#microsoft.graph.windowsUpdates.rateDrivenRolloutSettings",
-           "durationBetweenOffers": "P1D",
-           "devicePerOffer": 1000
-         }
-       }
-     }
+     ]
    }
    ```
 
@@ -166,6 +155,7 @@ To edit the policy settings, **PATCH** the policy using the **Policy ID**. Run t
 
 ``` msgraph-interactive
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678
+content-type: application/json
 
 {
     "complianceChangeRules": [
diff --git a/windows/deployment/update/deployment-service-expedited-updates.md b/windows/deployment/update/deployment-service-expedited-updates.md
index ae8c818be9..00b8b774eb 100644
--- a/windows/deployment/update/deployment-service-expedited-updates.md
+++ b/windows/deployment/update/deployment-service-expedited-updates.md
@@ -174,6 +174,12 @@ content-type: application/json
 }
 ```
 
+To verify the devices were added to the audience, run the following query using the **Audience ID** of `d39ad1ce-0123-4567-89ab-cdef01234567`:
+
+   ```msgraph-interactive
+   GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/members
+   ```
+
 ## Pause a deployment
 
 To pause a deployment, PATCH the deployment to have a `requestedValue` of `paused` for the [deploymentState](/graph/api/resources/windowsupdates-deploymentstate). To resume the deployment, use the value `none` and the state will either update to `offering` or `scheduled` if the deployment hasn't reached the start date yet.
diff --git a/windows/deployment/update/deployment-service-feature-updates.md b/windows/deployment/update/deployment-service-feature-updates.md
index 87f4c2e0a2..7259780621 100644
--- a/windows/deployment/update/deployment-service-feature-updates.md
+++ b/windows/deployment/update/deployment-service-feature-updates.md
@@ -248,6 +248,12 @@ The following example adds three devices to the deployment audience using the **
    }
    ```
 
+To verify the devices were added to the audience, run the following query using the **Audience ID** of `d39ad1ce-0123-4567-89ab-cdef01234567`:
+
+   ```msgraph-interactive
+   GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/members
+   ```
+
 ## Pause a deployment
 
 To pause a deployment, PATCH the deployment to have a `requestedValue` of `paused` for the [deploymentState](/graph/api/resources/windowsupdates-deploymentstate). To resume the deployment, use the value `none` and the state will either update to `offering` or `scheduled` if the deployment hasn't reached the start date yet.
diff --git a/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md b/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
index 9d5e531e42..fda5f5a881 100644
--- a/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
+++ b/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
@@ -14,7 +14,8 @@ A deployment audience is a collection of devices that you want to deploy updates
 1. To create a new audience, **POST** to the [deployment audience](/graph/api/resources/windowsupdates-deploymentaudience) resource with a request body of `{}`.
 
    ```msgraph-interactive
-   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences   
+   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences 
+   content-type: application/json  
 
    {}
    ```
@@ -34,7 +35,8 @@ A deployment audience is a collection of devices that you want to deploy updates
 1. Add devices, using their **Azure AD ID**, to the deployment audience so they become audience members. Specify the deployment **Audience ID** in the URL field and the devices to add in the request body. The `id` property specifies the **Azure AD ID** of the device.
 
    ```msgraph-interactive
-   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience   
+   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience 
+   content-type: application/json  
 
    {
      "addMembers": [
diff --git a/windows/deployment/update/includes/wufb-deployment-graph-explorer.md b/windows/deployment/update/includes/wufb-deployment-graph-explorer.md
index d06da8e611..34f811aaad 100644
--- a/windows/deployment/update/includes/wufb-deployment-graph-explorer.md
+++ b/windows/deployment/update/includes/wufb-deployment-graph-explorer.md
@@ -31,4 +31,4 @@ For this article, you'll use Graph Explorer to make requests to the [Microsoft G
    1. Select the **Run query** button. The results will appear in the **Response** window.
   
    > [!TIP]
-   > When reviewing [Microsoft Graph documentation](/graph/), you may notice example requests usually list `Content-type: application/json`. Specifying `content-type` typically isn't required for Graph Explorer, but you can add it to the request by selecting the **Headers** tab and adding the `content-type` to the **Request headers** field as the **Key** and `application/json` as the **Value**.
+   > When reviewing [Microsoft Graph documentation](/graph/), you may notice example requests usually list `content-type: application/json`. Specifying `content-type` typically isn't required for Graph Explorer, but you can add it to the request by selecting the **Headers** tab and adding the `content-type` to the **Request headers** field as the **Key** and `application/json` as the **Value**.