Last push

Author: fauhse

articles/storage-discovery/deployment-planning.md

@@ -90,7 +90,7 @@ The Discovery service covers only storage accounts located in the following regi
 [!INCLUDE [data-plane-regions](includes/data-plane-regions.md)]
 
 > [!WARNING]
-> The Discovery service currently can't consider storage accounts located in regions other than those previously listed. Including storage accounts from unsupported regions in a scope can lead to an incomplete set of insights. A short-term limitation of the preview period.
+> The Discovery service currently can't consider storage accounts located in regions not included in the previously listed locations. Including storage accounts from unsupported regions in a scope can lead to an incomplete set of insights. A short-term limitation of the preview period.
 
 ## Permissions
 
@@ -110,7 +110,7 @@ In the workspace root, you list at least one and at most 100 Azure resources of
 The person deploying the workspace must have at least the RBAC role assignment *Reader* for every resource in the workspace root.
 *Reader* is the minimum permission level required. *Contributor* and *Owner* are also supported.
 
-It is possible that you see a subscription listed in the Azure portal, for which you don't have this direct *Reader* role assignment. When you can see a resource you don't have a role assignment to, then most likely you have permissions to a sub resource in this subscription. In this case, the existence of this "parent" was revealed to you, but you have no rights on the subscription resource itself. This example can be extended to resource groups as well. Missing a *Reader* or higher direct role assignment disqualifies an Azure resource from being the basis (root) of a workspace.
+It's possible that you see a subscription listed in the Azure portal, for which you don't have this direct *Reader* role assignment. When you can see a resource you don't have a role assignment to, then most likely you have permissions to a sub resource in this subscription. In this case, the existence of this "parent" was revealed to you, but you have no rights on the subscription resource itself. This example can be extended to resource groups as well. Missing a *Reader* or higher direct role assignment disqualifies an Azure resource from being the basis (root) of a workspace.
 
 Permissions are only validated when a workspace is created. Any change to permissions of the Azure account that created the workspace, including its deletion, has no effect on the workspace or the Discovery service functionality.