Update troubleshoot.md

Author: SoniaLopezBravo

articles/iot-operations/troubleshoot/troubleshoot.md

@@ -25,7 +25,7 @@ For general deployment and configuration troubleshooting, you can use the Azure
 
 ### You see an UnauthorizedNamespaceError error message
 
-If you see the following error message, you either didn't enable the required azure-arc custom locations feature, or you enabled the custom locations feature with an incorrect custom locations RP OID.
+If you see the following error message, you either didn't enable the required Azure-arc custom locations feature, or you enabled the custom locations feature with an incorrect custom locations RP OID.
 
 ```ouput
 Message: Microsoft.ExtendedLocation resource provider does not have the required permissions to create a namespace on the cluster.
@@ -51,7 +51,7 @@ If you see the following error message, the logged-in principal doesn't have the
 Message: The client {principal Id} with object id {principal object Id} has permission to perform action Microsoft.ExtendedLocation/customLocations/resourceSyncRules/write on scope {resource sync resource Id}; however, it does not have permission to perform action(s) Microsoft.Authorization/roleAssignments/write on the linked scope(s) {resource sync resource group} (respectively) or the linked scope(s) are invalid.
 ```
 
-Deployment of resource sync rules require the logged-in principal to have the `Microsoft.Authorization/roleAssignments/write` permission against the resource group that resources are being deployed to. This is a necessary security constraint as edge to cloud resource hydration will create new resources in the target resource group. 
+Deployment of resource sync rules requires the logged-in principal to have the `Microsoft.Authorization/roleAssignments/write` permission against the resource group that resources are being deployed to. This is a necessary security constraint as edge to cloud resource hydration will create new resources in the target resource group. 
 
 To resolve, either elevate principal permissions, or don't deploy resource sync rules. Current AIO CLI has an opt-in mechanism to deploy resource sync rules via `--enable-rsync`. Simply omit this flag. Legacy AIO CLIs had an opt-out mechanism via `--disable-rsync-rules`.