edit

Author: mumian

articles/azure-resource-manager/bicep/private-module-registry.md

@@ -55,7 +55,7 @@ A Bicep registry is hosted on [Azure Container Registry (ACR)](../../container-r
 
 ## Publish files to registry
 
-After setting up the container registry, you can publish files to it. Use the [publish](bicep-cli.md#publish) command and provide any Bicep files you intend to use as modules. Specify the target location for the module in your registry. The publish command will create an ARM template which will be stored in the registry. This means if publishing a Bicep file that references other local modules, these modules will be fully expanded as one JSON file and published to the registry.
+After setting up the container registry, you can publish files to it. Use the [publish](bicep-cli.md#publish) command and provide any Bicep files you intend to use as modules. Specify the target location for the module in your registry. The publish command creates an ARM template, which is stored in the registry. This means if publishing a Bicep file that references other local modules, these modules are fully expanded as one JSON file and published to the registry.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -91,11 +91,11 @@ az bicep publish --file storage.bicep --target br:exampleregistry.azurecr.io/bic
 
 ---
 
-With the with source switch, you see an additional layer in the manifest:
+With the with source switch, you see an another layer in the manifest:
 
 :::image type="content" source="./media/private-module-registry/bicep-module-with-source-manifest.png" lightbox="./media/private-module-registry/bicep-module-with-source-manifest.png" alt-text="Screenshot of bicep module registry with source.":::
 
-Note that if the Bicep module references a module in a Private Registry, the ACR endpoint will be visible. To hide the full endpoint, you can configure an alias for the private registry.
+If the Bicep module references a module in a Private Registry, the ACR endpoint is visible. To hide the full endpoint, you can configure an alias for the private registry.
 
 ## View files in registry
 
@@ -105,9 +105,9 @@ To see the published module in the portal:
 1. Search for **container registries**.
 1. Select your registry.
 1. Select **Services** -> **Repositories** from the left menu.
-1. Select the module path (repository).  In the preceding example, the module path name is **bicep/modules/storage**.
+1. Select the module path (repository). In the preceding example, the module path name is **bicep/modules/storage**.
 1. Select the tag. In the preceding example, the tag is **v1**.
-1. The **Artifact reference** matches the reference you'll use in the Bicep file.
+1. The **Artifact reference** matches the reference you use in the Bicep file.
 
    ![Bicep module registry artifact reference](./media/private-module-registry/bicep-module-registry-artifact-reference.png)
 
@@ -116,7 +116,7 @@ You're now ready to reference the file in the registry from a Bicep file. For ex
 ---
 ## Working with Bicep registry files
 
-When leveraging bicep files that are hosted in a remote registry, it's important to understand how your local machine will interact with the registry. When you first declare the reference to the registry, your local editor will try to communicate with the Azure Container Registry and download a copy of the registry to your local cache.
+When using bicep files that are hosted in a remote registry, it's important to understand how your local machine interacts with the registry. When you first declare the reference to the registry, your local editor tries to communicate with the Azure Container Registry and download a copy of the registry to your local cache.
 
 The local cache is found in:
 
@@ -138,17 +138,16 @@ The local cache is found in:
     ~/.bicep
     ```
 
-Any changes made to the remote registry will not be recognized by your local machine until a `restore` has been ran with the specified file that includes the registry reference.
+Your local machine can recognize any changes made to the remote registry until you run a `restore` with the specified file that includes the registry reference.
 
 ```azurecli
 az bicep restore --file <bicep-file> [--force]
 ```
 
-For more information refer to the [`restore` command.](bicep-cli.md#restore)
-
+For more information, see the [`restore` command.](bicep-cli.md#restore)
 
 ## Next steps
 
-* To learn about modules, see [Bicep modules](modules.md).
-* To configure aliases for a module registry, see [Add module settings in the Bicep config file](bicep-config-modules.md).
-* For more information about publishing and restoring modules, see [Bicep CLI commands](bicep-cli.md).
+- To learn about modules, see [Bicep modules](modules.md).
+- To configure aliases for a module registry, see [Add module settings in the Bicep config file](bicep-config-modules.md).
+- For more information about publishing and restoring modules, see [Bicep CLI commands](bicep-cli.md).