update

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/10/2024
+ms.date: 06/11/2024
 ---
 
 # Add module settings in the Bicep config file
@@ -100,13 +100,16 @@ For a template spec, use:
 module stgModule  'ts/CoreSpecs:storage:v1' = {
 ```
 
-An alias has been predefined for [Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/). To reference an Azure verified module, you can use the format:
+An alias has been predefined for [public modules](./modules.md#file-in-registry). To reference a public module, you can use the format:
 
 ```bicep
 br/public:<file>:<tag>
 ```
 
-You can override the public module registry alias definition in the bicepconfig.json file:
+> [!NOTE]
+> Non-AVM (Azure Verified Modules) modules are retired from the public module registry.
+
+You can override the public module registry alias definition in the [bicepconfig.json file](./bicep-config.md):
 
 ```json
 {

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/10/2024
+ms.date: 06/11/2024
 ---
 
 # Using statement
@@ -29,7 +29,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   using '<path>/<file-name>.json'
   ```
 
-- To use [Azure Verified Modules](./modules.md##path-to-module):
+- To use [public modules](./modules.md#path-to-module):
 
   ```bicep
   using 'br/public:<file-path>:<tag>'

articles/azure-resource-manager/bicep/media/modules/bicep-azure-verified-modules-avm.png

@@ -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/06/2024
+ms.date: 06/11/2024
 ---
 
 # Bicep modules
@@ -93,26 +93,28 @@ For example, to deploy a file that is up one level in the directory from your ma
 
 ### File in registry
 
-#### Azure Verified Modules
+#### Public module registry
 
 > [!NOTE]
-> Non-AVM modules are retired from the public registry.
+> 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 pre-built, pre-tested, and pre-verified modules for deploying resources on Azure. These modules are created by Microsoft or trusted partners and are designed to simplify and accelerate the deployment process for common Azure resources and configurations. Select the highlighted numbers in the following screenshot to see the list of modules.
+[Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) are pre-built, pre-tested, and pre-verified modules for deploying resources on Azure. These modules are created by Microsoft or trusted partners and are designed to simplify and accelerate the deployment process for common Azure resources and configurations.
+
+Browse to the [Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) site, and select the highlighted numbers in the following screenshot to see the list of modules.
 
 :::image type="content" source="./media/modules/bicep-azure-verified-modules-avm.png" alt-text="The screenshot of Azure Verified Modules(AVM).":::
 
 The module list shows the latest version. Select the version number to see a list of available versions:
 
-:::image type="content" source="./media/modules/bicep-azure-verified-modules-avm-version.png" alt-text="The screenshot of Azure Verified Modules(AVM).":::
+:::image type="content" source="./media/modules/bicep-azure-verified-modules-avm-version.png" alt-text="The screenshot of Azure Verified Modules(AVM) versions.":::
 
-To link to an Azure verified module, specify the module path with the following syntax:
+To link to a public module, specify the module path with the following syntax:
 
 ```bicep
 module <symbolic-name> 'br/public:<file-path>:<tag>' = {}
 ```
 
-- **br/public** is the alias for Azure Verfied Modules. This alias is predefined in your configuration.
+- **br/public** is the alias for public modules. You can customize this alias in the [Bicep configuration file](./bicep-config-modules.md).
 - **file path** can contain segments that can be separated by the `/` character.
 - **tag** is used for specifying a version for the module.
 
@@ -128,7 +130,7 @@ module storage 'br/public:avm/res/storage/storage-account:0.9.0' = {
 ```
 
 > [!NOTE]
-> **br/public** is the alias for Azure Verified Modules. It can also be written as:
+> **br/public** is the alias for public modules. It can also be written as:
 >
 > ```bicep
 > module <symbolic-name> 'br:mcr.microsoft.com/bicep/<file-path>:<tag>' = {}

articles/azure-resource-manager/bicep/modules.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/10/2024
+ms.date: 06/11/2024
 ---
 
 # Create parameters files for Bicep deployment

articles/azure-resource-manager/bicep/parameter-files.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/10/2024
+ms.date: 06/11/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 Azure Verified Modules, see [Bicep Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/).
+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 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/private-module-registry.md

@@ -1,7 +1,7 @@
 ---
 title: Publish modules to private module registry
 description: Publish Bicep modules to private module registry and use the modules.
-ms.date: 06/10/2024
+ms.date: 06/11/2024
 ms.topic: quickstart
 ms.custom: mode-api, devx-track-bicep
 #Customer intent: As a developer new to Azure deployment, I want to learn how to publish Bicep modules to private module registry.