First round of Acrolinx improvements.

Author: fauhse

articles/storage-discovery/deployment-planning.md

@@ -25,7 +25,7 @@ Discovery currently doesn't work for [Azure Files](../storage/files/storage-file
 Your Azure Storage resources (like storage accounts) experience no transactions or performance impact when analyzing them with Azure Storage Discovery.
 
 Deploying the service means deploying and configuring a *Storage Discovery workspace resource* into a resource group in one of your subscriptions.
-The Discovery service works to compute and store insights about your Azure Blob Storage estate. These computed insights are stored in the region of the workspace you've created. Other than the Storage Discovery workspace, no additional infrastructure needs to be deployed.
+The Discovery service works to compute and store insights about your Azure Blob Storage estate. These computed insights are stored in the region of the workspace you created. Other than the Storage Discovery workspace, no other infrastructure needs to be deployed.
 
 The workspace can be configured to aggregate insights across any subscriptions in the Azure tenant the workspace is deployed in.
 To generate insights about Azure Storage resources, such as storage accounts, you need to be a member of the RBAC (Role Based Access Control) Reader role for every storage resource.
@@ -35,7 +35,7 @@ To generate insights about Azure Storage resources, such as storage accounts, yo
 
 ## Getting your subscription ready
 
-The subscription you choose for your Storage Discovery workspace deployment must be governed by the same Azure tenant as the Azure Storage resources (like storage accounts) you want to receive insights for. When you've decided on an Azure subscription and resource group for your Storage Discovery workspace, you need to prepare a few things, depending on how you deploy and which actions you or another admin perform.
+You need to choose a subscription that is governed by the same Azure tenant as the Azure Storage resources (such as storage accounts) you want to receive insights for. When you decided on an Azure subscription and resource group for your Storage Discovery workspace, review the following sections to ensure your subscription is prepared.
 
 ### Resource provider namespace
 
@@ -51,31 +51,31 @@ Register a resource provider:
 - [via Azure CLI](../azure-resource-manager/management/resource-providers-and-types.md#azure-cli)
 
 > [!TIP]
-> When you deploy a Storage Discovery workspace as a subscription *Owner* or *Contributor* through the Azure portal, your subscription is automatically registered with this resource provider namespace. You'll only have to perform the registration manually when using Azure PowerShell or CLI.
+> When you deploy a Storage Discovery workspace as a subscription *Owner* or *Contributor* through the Azure portal, your subscription is automatically registered with this resource provider namespace. You only need to perform the registration manually when using Azure PowerShell or CLI.
 
 Once a subscription is enabled for this resource provider namespace, it remains enabled until manually unregistered. You can even delete the last Storage Discovery workspace and your subscription still remains enabled. Subsequent Storage Discovery workspace deployments then require reduced permissions from an admin. The following section contains a breakdown of different management scenarios and their required permissions.
 
-### Decide on the number of workspaces you'll need
+### Decide on the number of workspaces you need
 
 A Storage Discovery workspace needs to be configured with *scopes*. The management components article shares [details about workspace scopes](management-components.md).
 Scopes are logical groups of storage resources. For instance, a scope can refer to all the storage resources of a specific workload or department that you want to get insights for separately. 
 
 Since you can only configure a limited number of scopes in a workspace, you may need more than one workspace to cover your insights reporting needs.
 
-If a workspace is to be used for higher-level insights, you can create one with one scope for your entire Azure Storage estate and then add additional scopes for each department.
+If a workspace is to be used for higher-level insights, you can create one with one scope for your entire Azure Storage estate and then add scopes for each department.
 If a workspace is designated to provide insights for specific workloads, then you can create a workspace containing a scope for each workload.
 
 > [!IMPORTANT]
-> During the Azure Storage Discovery preview period, only storage accounts in select regions can be covered by the Discovery service. <br>The Understand region limitations section in this article has details.
+> During the Azure Storage Discovery preview period, the Discovery service covers only storage accounts located in select regions. <br>The [Understand region limitations](#understand-region-limitations) section in this article has details.
 
 ### Review your Azure resource tags
 
 You can select which storage resources are included in a [workspace scope](management-components.md) by first selecting specific subscriptions or resource groups, and then filtering the storage resources within them by [Azure resource tags](../azure-resource-manager/management/tag-resources.md).
-It's important that you familiarize yourself with the available resource tags on your storage resources, ensure they are consistently applied, and catalog them for building the scopes that support you with the insights for your business decisions.
+It's important that you familiarize yourself with the available resource tags on your storage resources. Ensure they are consistently applied and then catalog them for building the scopes in your workspace. Plan the scopes you need in order to have insights available per department, workload, or other grouping you have a use for.
 
 ## Select an Azure region for your deployment
 
-When you deploy an Storage Discovery workspace, you need to choose a region. The region you select determines where the computed insights about your Azure Storage resources are stored. You can still capture insights for Azure Storage resources that are located in other regions. A general best practice is to choose the region for your workspace according to metadata residency requirements that apply to you and in closer proximity to your location. Visualizing your insights from a workspace closer to you can have a slight performance advantage.
+When you deploy a Storage Discovery workspace, you need to choose a region. The region you select determines where the computed insights about your Azure Storage resources are stored. You can still capture insights for Azure Storage resources that are located in other regions. A general best practice is to choose the region for your workspace according to metadata residency requirements that apply to you and in closer proximity to your location. Visualizing your insights from a workspace closer to you can have a slight performance advantage.
 
 Storage Discovery workspaces can be created in the following regions. This list will expand throughout the preview period.
 
@@ -85,12 +85,12 @@ Storage Discovery workspaces can be created in the following regions. This list
 
 While a Storage Discovery workspace can cover storage accounts from other subscriptions and resource groups, and even other regions, there is an important region limitation you need to be aware of for a successful Storage Discovery deployment.
 
-Only storage accounts located in the following regions can be covered by the Discovery service:
+The Discovery service covers only storage accounts located in the following regions:
 
 [!INCLUDE [data-plane-regions](includes/data-plane-regions.md)]
 
 > [!WARNING]
-> Storage accounts in regions other than these previously listed, will not be considered by the Discovery service. That can lead to an incomplete set of insights if such storage accounts are listed in a workspace scope. This is a short-term limitation during the preview period.
+> Storage accounts in regions other than previously listed, can't be considered by the Discovery service. 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,13 +110,13 @@ 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. This can happen when 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 is possible that you see a subscription listed in the Azure portal, for which you don't have this direct *Reader* role assignment. This can happen when 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 it's deletion, has no effect on the workspace or the Discovery service functionality.
+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.
 
 ### Permission considerations for a workspace resource
 
-The Azure Storage Discovery workspace stores the computed insights for your storage estate. You can access reports in the Azure portal, or leverage these insights from the Azure Copilot. In order to access insights stored in a workspace, a user must have at least the RBAC role *Reader* on the workspace. *Contributor* and *Owner* role assignments also work. You can provide insights-access to another user by assigning them one of the three previously listed roles on the workspace.
+The Azure Storage Discovery workspace stores the computed insights for your storage estate. You can access reports in the Azure portal, or use these insights via the Azure Copilot. In order to access insights stored in a workspace, a user must have at least the RBAC role *Reader* on the workspace. *Contributor* and *Owner* role assignments also work. You can provide insights-access to another user by assigning them one of the three previously listed roles on the workspace.
 
 
 |Scenario |Minimal RBAC role assignments needed                                             |
@@ -128,7 +128,7 @@ The Azure Storage Discovery workspace stores the computed insights for your stor
 |Enable a person to share these insights with others | Storage Discovery workspace: `Owner`|
 
 > [!CAUTION]
-> When you provide other users access to a workspace, be aware that they might not have been privileged to know the Azure resources they'll see in the workspace existed. You are disclosing all insights of the workspace - there are no further permission checks. Providing access to a workspace does not provide access to an individual storage account, resource group, or subscription. Individual resources remain governed by RBAC.
+> When you provide other users access to a workspace they might not be privileged to know about the existence of the Azure resources they'll see in the workspace. You are disclosing all insights of the workspace - there are no further permission checks. Providing access to a workspace does not provide access to an individual storage account, resource group, or subscription. Individual resources remain governed by RBAC.
 
 ## Next steps