Fixed blocking issues from PR review

Author: alkohli

azure-local/manage/disconnected-operations-arc-vm.md

@@ -59,7 +59,7 @@ Proxy servers aren't supported for outbound internet connections.
 
 Create a VM in the portal by selecting **Azure Arc** > **Machines** > **Add/Create** > **Create a machine in a connected host environment**. For more information, see step 7 under the Create Azure Local VMs section.
 
-:::image type="content" source="./media/disconnected-operations/arc-vms/create-arc-vms.png" alt-text="Screenshot showing how create an Azure Local VM from the portal." lightbox=" ./media/disconnected-operations/arc-vms/create-arc-vms.png":::
+:::image type="content" source="./media/disconnected-operations/arc-vms/create-arc-vms.png" alt-text="Screenshot showing how to create an Azure Local VM from the portal." lightbox=" ./media/disconnected-operations/arc-vms/create-arc-vms.png":::
 
 ## Create Azure Local VMs with disconnected operations
 

azure-local/manage/disconnected-operations-cli.md

@@ -51,7 +51,7 @@ For disconnected operations:
 1. Understand [public key infrastructure (PKI) for Azure Local with disconnected operations (preview)](disconnected-operations-pki.md)
 2. Set up and configure the certificate trusts for Azure CLI using PowerShell.
 
-    Here's an example script you can run in Powershell:
+    Here's an example script you can run in PowerShell:
 
     ```powershell    
         # Define the helper method

azure-local/manage/disconnected-operations-identity.md

@@ -142,7 +142,7 @@ $idpConfig = @{
 
 Consider these limitations when you plan your identity integration with disconnected operations:
 
-- **Users/Group removal after synchronization**: If you remove users and groups with memberships after the last sync, disconnected operations doesn't clean them up. This can cause errors when you query group memberships.
+- **Users/Group removal after synchronization**: If you remove users and groups with memberships after the last sync, disconnected operations don't clean them up. This can cause errors when you query group memberships.
 - **No force synchronization capability**: Sync runs every 6 hours.  
 - **No management groups or aggregate root level**: Not available for multiple subscriptions.  
 - **Supported validations**: Only Active Directory/AD FS are validated for support.

azure-local/manage/disconnected-operations-on-demand-logs.md

@@ -194,7 +194,7 @@ After you collect logs into a directory, either by using the nvoke-ApplianceLogC
 
 The Send-DiagnosticData cmdlet requires subscription details, i.e. the ResourceGroupName, SubscriptionId, TenantId, and RegistrationRegion *. It also requires credentials, either via manual login or by providing the appropriate service principal with password. (See Observability Configuration setup section for steps to create resource group, service principal required to upload logs.)
 
-You will to need to run Send-DiagnosticData on Windows machine connected to internet. You will not be able to run this on Azure Local Hosts as they can’t use Azure as Arc Control Plane when disconnected operations already configured.  When this cmdlet runs, it will connect the machine to Azure using Arc Registration so the device can upload data to Microsoft support. Note: The RegistrationRegion is equivalent to Location within ObservabilityConfiguration.
+You will need to run Send-DiagnosticData on Windows machine connected to internet. You will not be able to run this on Azure Local Hosts as they can’t use Azure as Arc Control Plane when disconnected operations already configured.  When this cmdlet runs, it will connect the machine to Azure using Arc Registration so the device can upload data to Microsoft support. Note: The RegistrationRegion is equivalent to Location within ObservabilityConfiguration.
 
 Intended for use in cases where direct log collection from appliance VM is unavailable. It could be either due to control plane appliance VM is having issues where management endpoint is not accessible or appliance VM is disconnected from Azure
 
@@ -431,7 +431,7 @@ This approach lets you share diagnostic data for support purposes without affect
 
 ### Use fallback log collection
 
-Use fallback log collection to collect and send logs when the disconnected operations with Azure Local VM is down, the management endpoint isn't accessible, and you can't invoke standard log collection.
+Use fallback log collection to collect and send logs when the disconnected operations with Azure Local VM are down, the management endpoint isn't accessible, and you can't invoke standard log collection.
 
 There are three methods used in this scenario:
 

azure-local/manage/disconnected-operations-pki.md

@@ -22,7 +22,7 @@ PKI for disconnected operations is essential for securing the endpoints provided
 
 ## PKI requirements
 
-A public certificate authorities (CA) or enterprise certificate authorities must issue certificates. Make sure your certificates are part of the Microsoft Trusted Root Program. For more information, see [List of Participants - Microsoft Trusted Root Program](/security/trusted-root/participants-list).  
+A public certificate authority (CA) or enterprise certificate authority must issue certificates. Make sure your certificates are part of the Microsoft Trusted Root Program. For more information, see [List of Participants - Microsoft Trusted Root Program](/security/trusted-root/participants-list).  
 
 Mandatory certificates are grouped by area with the appropriate subject alternate names (SAN). Before you create the certificates, review these requirements:
 
@@ -210,7 +210,7 @@ $AzLCerts = @(
 
 ### Management endpoint
 
-Here's an an example on how to create certificates for securing the management endpoint:
+Here's an example of how to create certificates for securing the management endpoint:
 
 > [!NOTE]
 > Run this script on a domain-joined machine using an account with Domain Administrator access to issue certificates.
@@ -310,7 +310,7 @@ These checks confirm that the certificates and chain for these endpoints haven
 
 You have a helper method in the **OperationsModule** that can help you populate these parameters.
 
-Here's an example on how to populate the required parameters:
+Here's an example of how to populate the required parameters:
 
 ```powershell
 $oidcCertChain = Get-CertificateChainFromEndpoint -endpoint 'https://adfs.azurestack.local'