updates casing and table consolidated

Author: Rich Thorn

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

@@ -31,13 +31,13 @@ To connect resources, resource groups, or subscriptions to a Service Group (prev
 For REST API, use the
 [Service Groups Member- Create or Update]() endpoint to create a new service group member.
 
-In this example, we're connecting a Virtual Machine [VM1] to a Service Group [Contoso].
+In this example, we're connecting a Virtual Machine [VM1] to a service group [Contoso].
 
 1. Service Group: **groupId** is _Contoso_
 1. Virtual Machine: The **resourceID** is _VM1_
 1. Service Group Member: The **relationshipID** is _SGM1_
 
-When you're adding a resource to a Service Group, you create service group member by extending the resource.  
+When you're adding a resource to a service group, you create service group member by extending the resource.  
 
 - REST API URI
 
@@ -52,7 +52,7 @@ specify the service group as the parent, use the **TargetID** property.
 - REST API URI
 
   ```http
-  PUT https://management.azure.com/subscriptions/[SUBID]/resourceGroups/[RGID]/providers/microsoft.compute/virtualmachine/[VMID]/providers/Microsoft.Management/serviceGroups/SGM1?api-version=2024-02-01-preview
+  PUT https://management.azure.com/subscriptions/[SUBID]/resourceGroups/[RGID]/providers/microsoft.compute/virtualmachine/[VMID]/providers/Microsoft.Relationships/serviceGroupMember/SGM1?api-version=2024-02-01-preview
   ```
 
 - Request Body

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

@@ -11,7 +11,7 @@ ms.date: 5/19/2025
 
 # Quickstart: Create a service group (preview) in the portal
 
-Azure Service Groups offer a flexible way to organize and manage resources across subscriptions and resource groups, parallel to any existing Azure resource hierarchy. They're ideal for scenarios requiring cross-boundary grouping, minimal permissions, and aggregations of data across resources. These features empower teams to create tailored resource collections that align with operational, organizational, or persona-based needs. This article helps give you an overview of what Service Groups are, the scenarios to use them for, and provide guidance on how to get started. For more information on service groups, see [Getting started with Service Groups](overview.md).
+Azure Service Groups offer a flexible way to organize and manage resources across subscriptions and resource groups, parallel to any existing Azure resource hierarchy. They're ideal for scenarios requiring cross-boundary grouping, minimal permissions, and aggregations of data across resources. These features empower teams to create tailored resource collections that align with operational, organizational, or persona-based needs. This article helps give you an overview of what service groups are, the scenarios to use them for, and provide guidance on how to get started. For more information on service groups, see [Getting started with Service Groups](overview.md).
 
 > [!IMPORTANT]
 > Azure Service Groups is currently in PREVIEW. 
@@ -26,35 +26,31 @@ Azure Service Groups offer a flexible way to organize and manage resources acros
 ## Create in Azure portal
 
 1. Log into the [Azure portal](https://portal.azure.com).
-
-1. Select **All services** > **Management + governance**.
-
-1. Select **Service Groups**.
-
-1. Select **+ Add service group**.
+2. Select **All services** > **Management + governance**.
+3. Select **Service Groups**.
+4. Select **+ Add Service Group**.
 
   ![Screenshot of new SG screen](./media/create_SG.png)
 
-1. Fill in the service group ID field
+5. Fill in the service group ID field
 
-    - The **Service Group ID** is the directory unique identifier that is used to submit commands
+   * The **Service Group ID** is the directory unique identifier that is used to submit commands
          on this service group. This identifier isn't editable after creation as it's used throughout
          the Azure system to identify this group. The
          [root service group](./overview.md#the-root-service-group) is
          automatically created with an ID that is the Microsoft Entra ID. For all other
          service groups, assign a unique ID.
-    - The display name field is the name that is displayed within the Azure portal. A separate
+   * The display name field is the name that is displayed within the Azure portal. A separate
          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]"_
 
-1. Select the **Parent Service Group**. 
-
-1. Select "Next" 
-
-1. The review page shows
+7. Select "Next" 
+8. The review page shows
 
 ![The review page for creating a new service group](./media/create_review_sg.png)
-
-1. If all information is correct, select **Create**
+9. If all information is correct, select **Create**
 
 ## Clean up resources
 

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

@@ -28,9 +28,7 @@ With Azure Service Groups (preview) you can create low-privilege-based groupings
 
 ## Create in REST API
 
-For REST API, use the
-[Service Groups - Create or Update]()
-endpoint to create a new service group. In this example, the service group **groupId** is
+In this example, the service group **groupId** is
 _Contoso_.
 
 - REST API URI
@@ -84,17 +82,17 @@ specify a different service group as the parent, use the **properties.parent.id*
   ```
 
 ## Verify your Service Group was created
-Service Groups PUT or create call is an Asynchronous call which means that the response to the initial create call is an HTTP status code 201: Accepted. This response doesn't mean the Service group was successfully created, only that the Azure successfully received the request to create the Service Group.  
+Service Groups PUT or create call is an Asynchronous call which means that the response to the initial create call is that it was accepted. This response doesn't mean the service group was successfully created, only that the Azure successfully received the request to create the service group.  
 
 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.  
+> 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.  
 
 ## Clean up resources
 
 To remove the service group created in this document, use the
-[Management Groups - Delete]() endpoint:
+Service Group Delete endpoint:    
 
 - REST API URI