edits

ktoliver · ktoliver · commit a2b081ceec17 · 2023-03-07T12:44:38.000-08:00
diff --git a/articles/deployment-environments/concept-common-components.md b/articles/deployment-environments/concept-common-components.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Deployment Environments and Microsoft Dev Box common elements
-description: Discover the components that are shared by Azure Deployment Environments and Microsoft Dev Box.
+description: Discover the components that are shared by Azure Deployment Environments Preview and Microsoft Dev Box.
 ms.service: deployment-environments
 ms.custom: ignite-2022
 ms.topic: conceptual
@@ -11,6 +11,8 @@ ms.date: 01/26/2022
 # Components common to Azure Deployment Environments and Microsoft Dev Box
 
 > [!TIP]
-> Welcome to the **Azure Deployment Environments** documentation. If you're looking for information about **Microsoft Dev Box**, go to [Components common to Microsoft Dev Box and Azure Deployment Environments](../dev-box/concept-common-components.md).
+> Welcome to the *Azure Deployment Environments Preview* documentation.
+>
+> If you're looking for information about *Microsoft Dev Box*, go to [Components common to Microsoft Dev Box and Azure Deployment Environments](../dev-box/concept-common-components.md).
 
-[!INCLUDE [ade-mdb-common-components](../../includes/ade-mdb-common-components/ade-mdb-common-components.md)]
+[!INCLUDE [ade-mdb-common-components](../../includes/ade-mdb-common-components/ade-mdb-common-components.md)]
diff --git a/articles/deployment-environments/how-to-create-access-environments.md b/articles/deployment-environments/how-to-create-access-environments.md
@@ -1,7 +1,7 @@
 ---
 title: Create and access an environment by using the Azure CLI
 titleSuffix: Azure Deployment Environments
-description: Learn how to create and access an environment in an Azure Deployment Environments Preview project by using the AzureCLI.
+description: Learn how to create and access an environment in an Azure Deployment Environments Preview project by using the Azure CLI.
 author: RoseHJM
 ms.author: rosemalcolm
 ms.service: deployment-environments
@@ -49,8 +49,7 @@ This article shows you how to create and access an [environment](concept-environ
 Complete the following steps in the Azure CLI to create an environment and configure resources. You can view the outputs as defined in the specific Azure Resource Manager template (ARM template).
 
 > [!NOTE]
-> Only a user who has the [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has appropriate permissions can create an environment.
-
+> Only a user who has the [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has the required permissions can create an environment.
 
 1. Sign in to the Azure CLI:
 
@@ -107,15 +106,15 @@ Complete the following steps in the Azure CLI to create an environment and confi
    ```
 
 > [!NOTE]
-> You can use `--help` to view more details about any command, accepted arguments and examples. For example, use `az devcenter dev environment create --help` to view more details about creating an environment.
+> You can use `--help` to view more details about any command, accepted arguments, and examples. For example, use `az devcenter dev environment create --help` to view more details about creating an environment.
 
-### Troubleshoot permission error
+### Troubleshoot a permissions error
 
-You must have the [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has appropriate permissions can create an environment.
+You must have the [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has the required permissions to create an environment.
 
-If you don't have the correct permissions, creation of the environment will fail, and you may receive an error message like this:
+If you don't have the correct permissions, the environment isn't created. An error message like the following example might appear:
 
-```
+```output
 (EnvironmentNotFound) The environment resource was not found.
 Code: EnvironmentNotFound
 Message: The environment resource was not found.
diff --git a/articles/deployment-environments/how-to-manage-environments.md b/articles/deployment-environments/how-to-manage-environments.md
@@ -11,14 +11,14 @@ ms.date: 02/28/2023
 
 # Manage your environment
 
-In Azure Deployment Environments Preview, a development infrastructure (dev infra) admin gives developers access to projects and the environment types that are associated with them. After a developer has access, they can create deployments environments based on the pre-configured environment types. The permissions that the creator of the environment and the rest of team have to access the environment’s resources are defined in the specific environment type.
+In Azure Deployment Environments Preview, a development infrastructure admin gives developers access to projects and the environment types that are associated with them. After a developer has access, they can create deployments environments based on the pre-configured environment types. The permissions that the creator of the environment and the rest of team have to access the environment’s resources are defined in the specific environment type.
 
 As a developer, you can create and manage your environments from the developer portal or by using the Azure CLI.  
 
 ## Prerequisites
 
 - Access to a project that has at least one environment type.
-- The [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has appropriate permissions to create an environment.
+- The [Deployment Environments User](how-to-configure-deployment-environments-user.md) role, the [DevCenter Project Admin](how-to-configure-project-admin.md) role, or a [built-in role](../role-based-access-control/built-in-roles.md) that has the required permissions to create an environment.
 
 ## Manage an environment by using the developer portal
 
diff --git a/articles/deployment-environments/index.yml b/articles/deployment-environments/index.yml
@@ -1,11 +1,11 @@
 ### YamlMime:Landing
 
-title: Azure Deployment Environments documentation
-summary: Learn how to configure self-serve environments that developers can use to deploy their code with the Azure Deployment Environments service. Tutorials, quickstarts, how-to guides, and more. 
+title: Azure Deployment Environments Preview documentation
+summary: Learn how to configure self-serve environments that developers can use to deploy their code with the Azure Deployment Environments Preview service. Tutorials, quickstarts, how-to guides, and more. 
 
 metadata:
-  title: Azure Deployment Environments documentation
-  description: Learn how to configure self-serve environments that developers can use to deploy their code with the Azure Deployment Environments service. Tutorials, quickstarts, how-to guides, and more. 
+  title: Azure Deployment Environments Preview documentation
+  description: Learn how to configure self-serve environments that developers can use to deploy their code with the Azure Deployment Environments Preview service. Tutorials, quickstarts, how-to guides, and more. 
   services: deployment-environments
   ms.service: deployment-environments
   ms.custom: ignite-2022
@@ -26,7 +26,7 @@ landingContent:
             url: overview-what-is-azure-deployment-environments.md
           - text: Key concepts
             url: concept-environments-key-concepts.md
-          - text: Usage scenarios
+          - text: Use scenarios
             url: concept-environments-scenarios.md         
 
   # Card
@@ -38,11 +38,11 @@ landingContent:
             url: quickstart-create-and-configure-devcenter.md
           - text: 'Create & configure a project'
             url: quickstart-create-and-configure-projects.md
-          - text: 'Create & access Environments'
+          - text: 'Create & access environments'
             url: quickstart-create-access-environments.md
   
   # Card
-  - title: Configure Deployment Environments service
+  - title: Configure the Deployment Environments service
     linkLists:
       - linkListType: how-to-guide
         links:
diff --git a/includes/ade-mdb-common-components/ade-mdb-common-components.md b/includes/ade-mdb-common-components/ade-mdb-common-components.md
@@ -4,7 +4,7 @@ Microsoft Dev Box and Azure Deployment Environments are complementary services t
 
 The diagram shows the components of Dev Box and Deployments Environments. Dev centers and projects are common to both services. Both use managed identities to support authentication, and both services provide access for developers through the developer portal.
 
-:::image type="content" source="media/common-elements.png" alt-text="Diagram showing components of Microsoft Dev Box and Azure Deployment Environments.":::
+:::image type="content" source="media/common-elements.png" border="false" alt-text="Diagram showing components of Microsoft Dev Box and Azure Deployment Environments.":::
 
 The following table lists Dev Box and Deployments Environments components:
 
@@ -15,34 +15,34 @@ The following table lists Dev Box and Deployments Environments components:
 |  Dev box pools         |     Yes      |         No              |
 |  Dev box definitions   |     Yes      |         No              |
 |  Dev boxes             |     Yes      |         No              |
-|  Compute Galleries     |     Yes      |         No              |
-|  Managed Identities    |     Yes      |         Yes             |
+|  Compute galleries     |     Yes      |         No              |
+|  Managed identities    |     Yes      |         Yes             |
 |  Environment types     |     No       |         Yes             |
 |  Environments          |     No       |         Yes             |
 |  Catalogs              |     No       |         Yes             |
-|  Developer Portal      |     Yes      |         Yes             |
+|  Developer portal      |     Yes      |         Yes             |
 
 ## How components appear in the Azure portal
 
 As you work with Dev Box or Deployments Environments in the Azure portal, you can access components from both services.
 
-In the dev center overview, you can access options for:
+In the dev center overview, you can access options to:
 
-1. Configuring your dev boxes
+- Configure your dev boxes.
 
-2. Configuring your environments
+- Configure your environments.
 
 :::image type="content" source="media/dev-center-overview.png" alt-text="Screenshot showing Dev Box and Deployment Environments components in a dev center.":::
 
-In the projects overview, you can access options for:
+In the projects overview, you can access options to:
 
-1. Configuring environment types for a specific project
+- Configure environment types for a specific project.
 
-2. Managing dev box pools and environments
+- Manage dev box pools and environments.
 
 :::image type="content" source="media/project-overview.png" alt-text="Screenshot showing Dev Box and Deployment Environments components in a project.":::
 
-You may also see informational messages that refer to a service you aren't using, like this one from the projects overview:
+You might also see informational messages that refer to a service you aren't using, like this one from the projects overview:
 
 :::image type="content" source="media/project-informational.png" alt-text="Screenshot showing an informational message.":::
 
@@ -56,14 +56,14 @@ You can access your dev boxes and deployment environments through the [developer
 
 You can create new dev boxes and environments through the developer portal menu at the top right.
 
-:::image type="content" source="media/developer-portal-menu.png" alt-text="Screenshot of developer portal menu.":::
+:::image type="content" source="media/developer-portal-menu.png" alt-text="Screenshot that shows the developer portal menu.":::
 
-And you can manage your existing dev boxes and environments too, selecting the more actions menu on the relevant card. Here's an example of managing an environment.
+And you can manage your existing dev boxes and environments, too. Select the **more actions** menu on the relevant card. Here's an example of managing an environment:
 
-:::image type="content" source="media/manage-environment.png" alt-text="Screenshot of options for managing an environment.":::
+:::image type="content" source="media/manage-environment.png" alt-text="Screenshot that shows options for managing an environment.":::
 
 ## Next steps
 
-- To learn how to configure Microsoft Dev Box, go to [Quickstart: Configure the Microsoft Dev Box Preview service](../../articles/dev-box/quickstart-configure-dev-box-service.md).
+- To learn how to configure Microsoft Dev Box, see [Quickstart: Configure the Microsoft Dev Box Preview service](../../articles/dev-box/quickstart-configure-dev-box-service.md).
 
-- To learn how to configure Azure Deployment Environments, go to [Quickstart: Create and configure a dev center](../../articles/deployment-environments/quickstart-create-and-configure-devcenter.md).
+- To learn how to configure Azure Deployment Environments, see [Quickstart: Create and configure a dev center](../../articles/deployment-environments/quickstart-create-and-configure-devcenter.md).
