incorporate comments

Author: mumian

articles/azure-resource-manager/bicep/bicep-config-modules.md

@@ -3,7 +3,7 @@ title: Module setting for Bicep config
 description: Describes how to customize configuration values for modules in Bicep deployments.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/11/2024
+ms.date: 06/28/2024
 ---
 
 # Add module settings in the Bicep config file
@@ -107,7 +107,7 @@ br/public:<file>:<tag>
 ```
 
 > [!NOTE]
-> Non-AVM (Azure Verified Modules) modules are retired from the public module registry.
+> Non-AVM (Azure Verified Modules) modules are retired from the public module registry with most of them available as AVM modules.
 
 You can override the public module registry alias definition in the [bicepconfig.json file](./bicep-config.md):
 

articles/azure-resource-manager/bicep/bicep-using.md

@@ -3,7 +3,7 @@ title: Using statement
 description: Describes how to use the using statement in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/11/2024
+ms.date: 06/28/2024
 ---
 
 # Using statement

articles/azure-resource-manager/bicep/modules.md

@@ -3,7 +3,7 @@ title: Bicep modules
 description: Describes how to define a module in a Bicep file, and how to use module scopes.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/11/2024
+ms.date: 06/28/2024
 ---
 
 # Bicep modules
@@ -98,9 +98,9 @@ For example, to deploy a file that is up one level in the directory from your ma
 > [!NOTE]
 > Non-AVM (Azure Verified Modules) modules are retired from the public module registry.
 
-[Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) are prebuilt, pretested, and preverified modules for deploying resources on Azure. Created by Microsoft or trusted partners, these modules are designed to simplify and accelerate the deployment process for common Azure resources and configurations.
+[Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/) are prebuilt, pretested, and preverified modules for deploying resources on Azure. Created and owned by Microsoft employees, these modules are designed to simplify and accelerate the deployment process for common Azure resources and configurations whilst also aligning to best practices; such as the Well-Architected Framework.
 
-Browse to the [Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) site.  To see the list of modules, select the highlighted numbers in the following screenshot.
+Browse to the [Azure Verified Modules Bicep Index](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/)to see the list of modules available, select the highlighted numbers in the following screenshot to be taken directly to that filtered view.
 
 :::image type="content" source="./media/modules/bicep-azure-verified-modules-avm.png" alt-text="The screenshot of Azure Verified Modules(AVM).":::
 

articles/azure-resource-manager/bicep/parameter-files.md

@@ -3,7 +3,7 @@ title: Create parameters files for Bicep deployment
 description: Create parameters file for passing in values during deployment of a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 06/11/2024
+ms.date: 06/28/2024
 ---
 
 # Create parameters files for Bicep deployment

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

@@ -3,12 +3,12 @@ title: Create private registry for Bicep module
 description: Learn how to set up an Azure container registry for private Bicep modules
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 06/11/2024
+ms.date: 06/28/2024
 ---
 
 # Create private registry for Bicep modules
 
-To share [modules](modules.md) within your organization, you can create a private module registry. You publish modules to that registry and give read access to users who need to deploy the modules. After the modules are shared in the registries, you can reference them from your Bicep files. To use public modules, see [Bicep Modules](./modules.md#file-in-registry).
+To share [modules](modules.md) within your organization, you can create a private module registry. You can then publish modules to that registry and give read access to users who need to deploy the modules. After the modules are shared in the registries, you can reference them from your Bicep files. To use public modules, see [Bicep Modules](./modules.md#file-in-registry).
 
 To work with module registries, you must have [Bicep CLI](./install.md) version **0.4.1008 or later**. To use with Azure CLI, you must also have version **2.31.0 or later**; to use with Azure PowerShell, you must also have version **7.0.0** or later.
 

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

@@ -9,7 +9,7 @@ ms.custom: mode-api, devx-track-bicep
 
 # Quickstart: Publish Bicep modules to private module registry
 
-Learn how to publish Bicep modules to private modules registry, and how to call the modules from your Bicep files. Private module registry allows you to share Bicep modules within your organization.  To learn more, see [Create private registry for Bicep modules](./private-module-registry.md). 
+Learn how to publish Bicep modules to private modules registry, and how to call the modules from your Bicep files. Private module registry allows you to share Bicep modules within your organization. To learn more, see [Create private registry for Bicep modules](./private-module-registry.md). 
 
 ## Prerequisites