update

Author: mumian

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

@@ -8,7 +8,7 @@ ms.date: 08/20/2024
 
 # Imports in Bicep
 
-This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensions.
+This article describes the syntax you use to export and import shared functionality, and namespaces for Bicep extensions.
 
 ## Export variables, types, and functions
 

articles/azure-resource-manager/bicep/data-types.md

@@ -319,7 +319,7 @@ is ${blocked}'''
 
 ## Union types
 
-In Bicep, a union type allows the creation of a combined type consisting of a set of sub-types. An assignment is valid if any of the individual sub-type assignments are permitted. The `|` character separates individual sub-types using an _or_ condition. For example, the syntax _'a' | 'b'_ means that a valid assignment could be either _'a'_ or _'b'_. Union types are translated into the [allowed-value](../templates/definitions.md#allowed-values) constraint in Bicep, so only literals are permitted as members. Unions can include any number of literal-typed expressions.
+In Bicep, a union type allows the creation of a combined type consisting of a set of subtypes. An assignment is valid if any of the individual subtype assignments are permitted. The `|` character separates individual subtypes using an _or_ condition. For example, the syntax _'a' | 'b'_ means that a valid assignment could be either _'a'_ or _'b'_. Union types are translated into the [allowed-value](../templates/definitions.md#allowed-values) constraint in Bicep, so only literals are permitted as members. Unions can include any number of literal-typed expressions.
 
 ```bicep
 type color = 'Red' | 'Blue' | 'White'
@@ -335,7 +335,7 @@ Type unions must be reducible to a single ARM type, such as 'string', 'int', or
 type foo = 'a' | 1
 ```
 
-Any type expression can be used as a sub-type in a union type declaration (between `|` characters). For example, the following examples are all valid:
+Any type expression can be used as a subtype in a union type declaration (between `|` characters). For example, the following examples are all valid:
 
 ```bicep
 type foo = 1 | 2
@@ -379,7 +379,7 @@ There are some limitations with union type.
   ```
 
 * Only literals are permitted as members.
-* All literals must be of the same primitive data type (e.g., all strings or all integers).
+* All literals must be of the same primitive data type (for example, all strings or all integers).
 
 The union type syntax can be used in [user-defined data types](./user-defined-data-types.md).
 

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

@@ -104,31 +104,32 @@ The allowed values are:
 
 In a module, you can specify a scope that is different than the scope for the rest of the Bicep file. For more information, see [Configure module scope](modules.md#set-module-scope)
 
-## Decorator
+## Decorators
 
 You can add one or more decorators for each of the following elements:
 
-* [Parameter](#parameters)
-* [Variable](#variables)
-* [Resource](#resources)
-* [Module](#modules)
-* [Output](#outputs)
-* [Type](#types)
+* [param](#parameters)
+* [var](#variables)
+* [resource](#resources)
+* [module](#modules)
+* [output](#outputs)
+* [func](#functions)
+* [type](#types)
 
 | Decorator | Apply to element | Apply to data type | Argument | Description |
 | --------- | ---- | ----------- | ------- |
-| allowed | [parameter](./parameters.md#allowed-values) | all | array | Use this decorator to make sure the user provides correct values. This decorator is only permitted on `param` statements. To declare that a property must be one of a set of predefined values in a [`type`](./user-defined-data-types.md) or [`output`](./outputs.md) statement, use [union type syntax](./data-types.md#union-types). Union type syntax can also be used in `param` statements.|
+| allowed | [param](./parameters.md#allowed-values) | all | array | Use this decorator to make sure the user provides correct values. This decorator is only permitted on `param` statements. To declare that a property must be one of a set of predefined values in a [`type`](./user-defined-data-types.md) or [`output`](./outputs.md) statement, use [union type syntax](./data-types.md#union-types). Union type syntax can also be used in `param` statements.|
 | batchSize |[resource](./resource-declaration.md#batchsize), [module](./modules.md#batchsize)| N/A | integer | Set up instances to deploy sequentially. |
-| description | [parameter](./parameters.md#description), [variable](./variables.md#description), [resource](./resource-declaration.md#description), [module](./modules.md#description), [output](./outputs.md#description), [type](./user-defined-data-types.md#description), [function](./user-defined-functions.md#description) | all | string | Text that explains how to use the element. |
-| discriminator | [parameter](./parameters.md#discriminator, [type](./user-defined-data-types.md#discriminator), [output](./outputs.md#discriminator) | object | string | Use this decorator to ensure the correct subclass is identified and managed. For more information, see [Custom-tagged union data type](./data-types.md#custom-tagged-union-data-type).|
-| export | [variable](./variables.md#export), [type](./user-defined-data-types.md#export), [function](./user-defined-functions.md#export) | all | none| Indicates that the element can be imported by another Bicep file. |
-| maxLength | [parameter](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The maximum length for string and array elemenets. The value is inclusive. |
-| maxValue | [parameter](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The maximum value for the integer elements. This value is inclusive. |
-| metadata | [parameter](./parameters.md#metadata), [output](./outputs.md#metadata) | all | object | Custom properties to apply to the elements. Can include a description property that is equivalent to the description decorator. |
-| minLength | [parameter](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The minimum length for string and array elements. The value is inclusive. |
-| minValue | [parameter](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The minimum value for the integer elements. This value is inclusive. |
-| sealed | [parameter](./parameters.md#sealed), [type](./user-defined-data-types.md#sealed), [output](./outputs.md#sealed) | object | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a use-define data type is likely a typo. For more information, see [Elevate error level](./user-defined-data-types.md#elevate-error-level). |
-| secure | [parameter](./parameters.md#secure-parameters) | string, object | none | Marks the parameter as secure. The value for a secure parameter isn't saved to the deployment history and isn't logged. For more information, see [Secure strings and objects](data-types.md#secure-strings-and-objects). |
+| description | [param](./parameters.md#description), [var](./variables.md#description), [resource](./resource-declaration.md#description), [module](./modules.md#description), [output](./outputs.md#description), [type](./user-defined-data-types.md#description), [func](./user-defined-functions.md#description) | all | string | Text that explains how to use the element. |
+| discriminator | [param](./parameters.md#discriminator), [type](./user-defined-data-types.md#discriminator), [output](./outputs.md#discriminator) | object | string | Use this decorator to ensure the correct subclass is identified and managed. For more information, see [Custom-tagged union data type](./data-types.md#custom-tagged-union-data-type).|
+| export | [var](./variables.md#export), [type](./user-defined-data-types.md#export), [func](./user-defined-functions.md#export) | all | none| Indicates that the element can be imported by another Bicep file. |
+| maxLength | [param](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The maximum length for string and array elements. The value is inclusive. |
+| maxValue | [param](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The maximum value for the integer elements. This value is inclusive. |
+| metadata | [param](./parameters.md#metadata), [output](./outputs.md#metadata) | all | object | Custom properties to apply to the elements. Can include a description property that is equivalent to the description decorator. |
+| minLength | [param](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The minimum length for string and array elements. The value is inclusive. |
+| minValue | [param](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The minimum value for the integer elements. This value is inclusive. |
+| sealed | [param](./parameters.md#sealed), [type](./user-defined-data-types.md#sealed), [output](./outputs.md#sealed) | object | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a use-define data type is likely a typo. For more information, see [Elevate error level](./user-defined-data-types.md#elevate-error-level). |
+| secure | [param](./parameters.md#secure-parameters) | string, object | none | Marks the parameter as secure. The value for a secure parameter isn't saved to the deployment history and isn't logged. For more information, see [Secure strings and objects](data-types.md#secure-strings-and-objects). |
 
 ## Parameters
 
@@ -435,7 +436,7 @@ The preceding example is equivalent to the following JSON.
 
 ## Multiple-line declarations
 
-You can now use multiple lines in function, array and object declarations. This feature requires [Bicep CLI version 0.7.X or higher](./install.md).
+You can now use multiple lines in function, array, and object declarations. This feature requires [Bicep CLI version 0.7.X or higher](./install.md).
 
 In the following example, the `resourceGroup()` definition is broken into multiple lines.
 
@@ -450,7 +451,7 @@ See [Arrays](./data-types.md#arrays) and [Objects](./data-types.md#objects) for
 ## Known limitations
 
 * No support for the concept of apiProfile, which is used to map a single apiProfile to a set apiVersion for each resource type.
-* User-defined functions are not supported at the moment. However, an experimental feature is currently accessible. For more information, see [User-defined functions in Bicep](./user-defined-functions.md).
+* User-defined functions aren't supported at the moment. However, an experimental feature is currently accessible. For more information, see [User-defined functions in Bicep](./user-defined-functions.md).
 * Some Bicep features require a corresponding change to the intermediate language (Azure Resource Manager JSON templates). We announce these features as available when all of the required updates have been deployed to global Azure. If you're using a different environment, such as Azure Stack, there may be a delay in the availability of the feature. The Bicep feature is only available when the intermediate language has also been updated in that environment.
 
 ## Next steps

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

@@ -132,7 +132,7 @@ module <symbolic-name> '<path-to-file>' = {
 
 ## Path to module
 
-The file for the module can be either a local file or an external file. The external file can be in template spec or a Bicep module registry. 
+The file for the module can be either a local file or an external file. The external file can be in template spec or a Bicep module registry.
 
 ### Local file
 
@@ -156,7 +156,7 @@ module stgModule '../storageAccount.bicep' = {
 > [!NOTE]
 > Non-AVM (Azure Verified Modules) modules are retired from the public module registry.
 
-[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.
+[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 while also aligning to best practices; such as the Well-Architected Framework.
 
 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.
 
@@ -275,44 +275,44 @@ Decorators are written in the format `@expression` and are placed above module d
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string |Provide descriptions for the module.|
 | [batchSize](./bicep-import.md#export-variables-types-and-functions) | none | Set up instances to deploy sequentially. |
+| [description](#description) | string |Provide descriptions for the module.|
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a parameter named `description`, you must add the sys namespace when using the **description** decorator.
 
-### Description
+### BatchSize
 
-To add explaination, add a description to module declarations. For example:
+You can only apply `@batchSize()` to a resource or module definition that uses a [`for` expression](./loops.md).
+
+By default, modules are deployed in parallel. When you add the `@batchSize(int)` decorator, you deploy instances serially.
 
 ```bicep
-@description('Create storage accounts referencing an AVM.')
-module storage 'br/public:avm/res/storage/storage-account:0.9.0' = {
+@batchSize(3)
+module storage 'br/public:avm/res/storage/storage-account:0.11.1' = [for storageName in storageAccounts: {
   name: 'myStorage'
   params: {
     name: 'store${resourceGroup().name}'
   }
-}
+}]
 ```
 
-Markdown-formatted text can be used for the description text.
-
-### BatchSize
+For more information, see [Deploy in batches](loops.md#deploy-in-batches).
 
-You can only apply `@batchSize()` to a resource or module definition that uses a [`for` expression](./loops.md).
+### Description
 
-By default, modules are deployed in parallel. When you add the `@batchSize(int)` decorator, you deploy instances serially.
+To add explanation, add a description to module declarations. For example:
 
 ```bicep
-@batchSize(3)
-module storage 'br/public:avm/res/storage/storage-account:0.11.1' = [for storageName in storageAccounts: {
+@description('Create storage accounts referencing an AVM.')
+module storage 'br/public:avm/res/storage/storage-account:0.9.0' = {
   name: 'myStorage'
   params: {
     name: 'store${resourceGroup().name}'
   }
-}]
+}
 ```
 
-For more information, see [Deploy in batches](loops.md#deploy-in-batches).
+Markdown-formatted text can be used for the description text.
 
 ## Parameters
 

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

@@ -8,7 +8,7 @@ ms.date: 08/20/2024
 
 # Outputs in Bicep
 
-This article describes how to define output values in a Bicep file. You use outputs when you need to return values from the deployed resources. You are limited to 64 outputs in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+This article describes how to define output values in a Bicep file. You use outputs when you need to return values from the deployed resources. You're limited to 64 outputs in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Define outputs
 
@@ -58,7 +58,7 @@ For more information, see [User-defined data types](./user-defined-data-types.md
 
 ## Use decorators
 
-Decorators are written in the format `@expression` and are placed above ouput declarations. The following table shows the available decorators for outputs.
+Decorators are written in the format `@expression` and are placed above output declarations. The following table shows the available decorators for outputs.
 
 | Decorator | Apply to | Argument | Description |
 | --------- | ---- | ----------- | ------- |
@@ -82,7 +82,7 @@ param description string
 
 ### Description
 
-To add explaination, add a description to output declarations. For example:
+To add explanation, add a description to output declarations. For example:
 
 ```bicep
 @description('Conditionally output the endpoint.')

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

@@ -60,7 +60,7 @@ param storageAccountConfig {
 }
 ```
 
-For more information, see [User-defined data types](./user-defined-data-types.md#syntax).
+For more information, see [User-defined data types](./user-defined-data-types.md#define-types).
 
 ## Set default values
 

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

@@ -8,7 +8,7 @@ ms.date: 08/20/2024
 
 # Resource declaration in Bicep
 
-This article describes the syntax you use to add a resource to your Bicep file. You are limited to 800 resources in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+This article describes the syntax you use to add a resource to your Bicep file. You're limited to 800 resources in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Define resources
 
@@ -66,38 +66,38 @@ Decorators are written in the format `@expression` and are placed above resource
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string | Provide descriptions for the resource. |
 | [batchSize](./bicep-import.md#export-variables-types-and-functions) | none | Set up instances to deploy sequentially. |
+| [description](#description) | string | Provide descriptions for the resource. |
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a parameter named `description`, you must add the sys namespace when using the **description** decorator.
 
-### Description
+### BatchSize
+
+You can only apply `@batchSize()` to a resource or module definition that uses a [`for` expression](./loops.md).
 
-To add explaination, add a description to resource declarations. For example:
+By default, resources are deployed in parallel. When you add the `batchSize(int)` decorator, you deploy instances serially.
 
 ```bicep
-@description('Create a number of storage accounts')
+@batchSize(3)
 resource storageAccountResources 'Microsoft.Storage/storageAccounts@2023-04-01' = [for storageName in storageAccounts: {
   ...
 }]
 ```
 
-Markdown-formatted text can be used for the description text.
-
-### BatchSize
+For more information, see [Deploy in batches](loops.md#deploy-in-batches).
 
-You can only apply `@batchSize()` to a resource or module definition that uses a [`for` expression](./loops.md).
+### Description
 
-By default, resources are deployed in parallel. When you add the `batchSize(int)` decorator, you deploy instances serially.
+To add explanation, add a description to resource declarations. For example:
 
 ```bicep
-@batchSize(3)
+@description('Create a number of storage accounts')
 resource storageAccountResources 'Microsoft.Storage/storageAccounts@2023-04-01' = [for storageName in storageAccounts: {
   ...
 }]
 ```
 
-For more information, see [Deploy in batches](loops.md#deploy-in-batches).
+Markdown-formatted text can be used for the description text.
 
 ## Resource name