Fine tuning

Author: RoseHJM

articles/dev-box/how-to-configure-dev-center-imaging.md

@@ -127,6 +127,8 @@ During the image build process, Dev Box creates a temporary storage account in y
 > [!IMPORTANT]
 > When an image is built from an image definition, a dev box is created to apply all the customizations and generate an image. By default, if no custom network is configured at the image definition level, the dev box is connected to a virtual network that Microsoft manages. Use the [network configuration](./reference-dev-box-customizations.md#networkconnection) property in image definitions for tasks that need access to on-premises or private resources to ensure that image generation is successful.
 
+
+
 ## Configure a dev box pool to use an image definition
 
 To use an image definition, you must configure a dev box pool to reference it. When developers create dev boxes from the pool, the customizations from the image definition are applied automatically.

articles/dev-box/how-to-configure-team-customizations.md

@@ -206,6 +206,9 @@ Set up your project to sync image definitions from the catalog. This setting let
 
 To use an image definition file, attach the catalog containing the file to your project. This makes the image definition available for selection when configuring your dev box pools.
 
+> [!NOTE]
+> Image definitions are only supported at the project level. You must attach catalogs containing image definitions to a project, not to a dev center.
+
 The **Image definitions** pane shows the image definitions your project can use.
 
 :::image type="content" source="media/how-to-configure-team-customizations/team-customizations-image-definitions-small.png" alt-text="Screenshot of the Azure portal pane showing image definitions available for a project.":::

articles/dev-box/how-to-customizations-connect-resource-repository.md

@@ -30,9 +30,9 @@ To use a secret, like a PAT, in your customization files, store it as a key vaul
 
 ### Configure key vault access for customizations
 
-To configure key vault secrets for use in your team or user customizations, make sure the Dev Center project's managed identity has the Key Vault Secrets User role on your key vault.
+Your dev center needs access to your key vault. To configure key vault secrets for use in your team or user customizations, make sure the Dev Center project's managed identity has the Key Vault Secrets User role on your key vault.
 
-If your organization's policies require you to keep your Key Vault private from the internet, you can create a firewall rule to disable or limit public access. You will need to let trusted Microsoft services bypass the firewall because Dev Center doesn't yet support service tags. Key vaults with private endpoints or private link integration are not currently supported for this scenario.
+If your organization's policies require you to keep your Key Vault private from the internet, you can create a firewall rule to disable or limit public access. You will need to let trusted Microsoft services bypass the firewall because Dev Center doesn't support service tags. Key vaults with private endpoints or private link integration are not currently supported for this scenario.
 
 The following screenshot shows the option to allow trusted Microsoft services to bypass the firewall in Azure Key Vault settings.