Content review changes

Author: Rich Thorn

articles/governance/service-groups/create-service-group-portal.md

@@ -30,8 +30,7 @@ Azure Service Groups offer a flexible way to organize and manage resources acros
 3. Select **Service Groups**.
 4. Select **+ Add Service Group**.
 
-  ![Screenshot of new SG screen](./media/create_SG.png)
-
+:::image type="content" source="./media/create-service-group.png" alt-text="Screenshot of new Service Group screen." Lightbox = "./media/create-service-group.png" :::
 5. Fill in the service group ID field
 
    * The **Service Group ID** is the directory unique identifier that is used to submit commands
@@ -44,12 +43,13 @@ Azure Service Groups offer a flexible way to organize and manage resources acros
          display name is an optional field when creating the service group and can be changed at any time.
 6. Select the **Parent Service Group**. 
 
-   * If you don't have a parent service group, or don't know what to pick, select the Root Service Group which has same ID as the tenant's ID. _"Microsoft.Management/serviceGroups/]tenantId]"_
+   * If you don't have a parent service group, or don't know what to pick, select the Root Service Group which has same ID as the tenant's ID. _"Microsoft.Management/serviceGroups[tenantId]"_
 
 7. Select "Next" 
 8. The review page shows
 
-![The review page for creating a new service group](./media/create_review_sg.png)
+:::image type="content" source="./media/create-review-service-group.png" alt-text="Screenshot of the review page for creating a new service group" Lightbox="./media/create-review-service-group.png":::
+
 9. If all information is correct, select **Create**
 
 ## Clean up resources

articles/governance/service-groups/create-service-group-rest-api.md

@@ -86,8 +86,9 @@ Service Groups PUT or create call is an Asynchronous call which means that the r
 
 To check the operation was successful, you should do a GET call on the value returned in the **azure-asyncoperation** header. The URL provides the status of the created operation. 
 
-> ![NOTE]
-> To avoid issues within scripts or templates, the automation should poll this provided URL before moving to the next step. If the automation moves to the next step before the operation has responded successful, the next operation will fail as the service group has not been created.  
+> [!NOTE]
+> To avoid issues within scripts or templates, the automation should poll this provided URL before moving to the next step. 
+> If the automation moves to the next step before the operation has responded successfully, the next operation will fail as the service group has not been created.  
 
 ## Clean up resources
 

articles/governance/service-groups/manage-service-groups.md

@@ -287,11 +287,11 @@ All **PUT**, **PATCH**, and **DELETE** API calls to Service Groups and Service G
 
 For example, if the customer created a REST API call to [Create a Service Group](#create-service-group). The API Request comes to Azure and the Service Groups Resource Provider to be processed. The response to the customer is that the request was received or it failed. 
 
-![Request Received](./media/requestReceived.png)
+:::image type="content" source="./media/request-received.png" alt-text="Diagram that shows request received process" Lightbox="./media/request-received.png":::
 
 To get the status of the operation to see if the service group was created or not, the customer makes a separate call. The status returned is for the entire operation.
 
-:::image type="content" source="./media/operationStatus.png" alt-text="Image showing the operation status as succeeded or failed.":::
+:::image type="content" source="./media/operation-status.png" alt-text="Image showing the operation status as succeeded or failed.":::
 
 ### How to get the operation status
 The URL used to get the operation status is returned as a header of the initial request's response.