acrolinx

Author: mumian

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

@@ -39,7 +39,7 @@ var mixedArray = ['abc', 'def'
     'ghi']
 ```
 
-In an array, each item is represented by the [any type](bicep-functions-any.md). You can have an array where each item is the same data type, or an array that holds different data types.
+Each array element can be of any type. You can have an array where each item is the same data type, or an array that holds different data types.
 
 The following example shows an array of integers and an array different types.
 
@@ -58,7 +58,7 @@ var mixedArray = [
 ]
 ```
 
-Arrays in Bicep are zero-based. In the following example, the expression `exampleArray[0]` evaluates to 1 and `exampleArray[2]` evaluates to 3. The index of the indexer may itself be another expression. The expression `exampleArray[index]` evaluates to 2. Integer indexers are only allowed on expression of array types.
+Arrays in Bicep are zero-based. In the following example, the expression `exampleArray[0]` evaluates to 1 and `exampleArray[2]` evaluates to 3. The index of the indexer can be another expression. The expression `exampleArray[index]` evaluates to 2. Integer indexers are only allowed on expression of array types.
 
 ```bicep
 var index = 1
@@ -102,15 +102,15 @@ When specifying integer values, don't use quotation marks.
 param exampleInt int = 1
 ```
 
-In Bicep, integers are 64-bit integers. When passed as inline parameters, the range of values may be limited by the SDK or command-line tool you use for deployment. For example, when using PowerShell to deploy a Bicep, integer types can range from -2147483648 to 2147483647. To avoid this limitation, specify large integer values in a [parameter file](parameter-files.md). Resource types apply their own limits for integer properties.
+Bicep integers are 64-bit integers. When passed as inline parameters, the range of values can be limited by the SDK or command-line tool you use for deployment. For example, when using PowerShell to deploy a Bicep, integer types can range from -2147483648 to 2147483647. To avoid this limitation, specify large integer values in a [parameter file](parameter-files.md). Resource types apply their own limits for integer properties.
 
-Bicep supports integer literal type which refers to a specific value that is an exact integer. In the following example, `1` is an integer literal type, `foo` can only be assigned the value `1` and no other value. 
+Bicep supports integer literal type that refers to a specific value that is an exact integer. In the following example, _1_ is an integer literal type, _foo_ can only be assigned the value _1_ and no other value.
 
 ```bicep
 output foo 1 = 1
 ```
 
-An integer literal type can either be declared inline, as shown in the preceeding example,  or in a [`type` statement](./user-defined-data-types.md).  
+An integer literal type can either be declared inline, as shown in the preceding example,  or in a [`type` statement](./user-defined-data-types.md).  
 
 ```bicep
 type oneType = 1
@@ -119,9 +119,9 @@ output foo oneType = 1
 output bar oneType = 2
 ```
 
-In the preceeding example, assigning `2` to `bar` will result in results in a [BCP033](./bicep-error-bcp033.md) error - _Expected a value of type "1" but the provided value is of type "2"_.
+In the preceding example, assigning _2_ to _bar_ results in a [BCP033](./bicep-error-bcp033.md) error - _Expected a value of type "1" but the provided value is of type "2"_.
 
-The following example, shows using integer literal type with [union type](#union-types):
+The following example shows using integer literal type with [union type](#union-types):
 
 ```bicep
 output bar 1 | 2 | 3 = 3
@@ -155,7 +155,7 @@ var test = {
 }
 ```
 
-In the preceding example, quotes are used when the object property keys contain special characters.  For example space, '-', or '.'. The following example shows how to use interpolation in object property keys.
+In the preceding example, quotes are used when the object property keys contain special characters. For example space, '-', or '.'. The following example shows how to use interpolation in object property keys.
 
 ```bicep
 var stringVar = 'example value'
@@ -199,7 +199,7 @@ output accessorResult string = environmentSettings['dev'].name
 
 [!INCLUDE [JSON object ordering](../../../includes/resource-manager-object-ordering-bicep.md)]
 
-You will get the following error when accessing an nonexisting property of an object:
+You get the following error when accessing a nonexisting property of an object:
 
 ```error
 The language expression property 'foo' doesn't exist
@@ -219,7 +219,7 @@ output bar bool = contains(objectToTest, 'four') && objectToTest.four == 4
 
 ## Strings
 
-In Bicep, strings are marked with singled quotes, and must be declared on a single line. All Unicode characters with code points between *0* and *10FFFF* are allowed.
+In Bicep, strings are marked with singled quotes, and must be declared on a single line. All Unicode characters with code points between _0_ and _10FFFF_ are allowed.
 
 ```bicep
 param exampleString string = 'test value'
@@ -234,21 +234,21 @@ The following table lists the set of reserved characters that must be escaped by
 | `\n` | line feed (LF) ||
 | `\r` | carriage return (CR) ||
 | `\t` | tab character ||
-| `\u{x}` | Unicode code point `x` | **x** represents a hexadecimal code point value between *0* and *10FFFF* (both inclusive). Leading zeros are allowed. Code points above *FFFF* are emitted as a surrogate pair.
+| `\u{x}` | Unicode code point `x` | **x** represents a hexadecimal code point value between _0_ and _10FFFF_ (both inclusive). Leading zeros are allowed. Code points above _FFFF_ are emitted as a surrogate pair. |
 | `\$` | `$` | Only escape when followed by `{`. |
 
 ```bicep
 // evaluates to "what's up?"
 var myVar = 'what\'s up?'
 ```
 
-Bicep supports string literal type which refers to a specific string value. In the following example, `red` is a string literal type, `redColor` can only be assigned the value `red` and no other value. 
+Bicep supports string literal type that refers to a specific string value. In the following example, _red_ is a string literal type, _redColor_ can only be assigned the value _red_ and no other value.
 
 ```bicep
 output redColor 'red' = 'red'
 ```
 
-An string literal type can either be declared inline, as shown in the preceeding example, or in a [`type` statement](./user-defined-data-types.md).  
+A string literal type can either be declared inline, as shown in the preceding example, or in a [`type` statement](./user-defined-data-types.md).  
 
 ```bicep
 type redColor = 'red'
@@ -257,9 +257,9 @@ output colorRed redColor = 'red'
 output colorBlue redColor = 'blue'
 ```
 
-In the preceeding example, assigning `blue` to `colorBlue` will result in results in a [BCP033](./bicep-error-bcp033.md) error - _Expected a value of type "'red'" but the provided value is of type "'blue'"_.
+In the preceding example, assigning _blue_ to _colorBlue_ results in a [BCP033](./bicep-error-bcp033.md) error - _Expected a value of type "'red'" but the provided value is of type "'blue'"_.
 
-The following example, shows using string literal type with [union type](#union-types):
+The following example shows using string literal type with [union type](#union-types):
 
 ```bicep
 type direction = 'north' | 'south' | 'east' | 'west'
@@ -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 constraint in Bicep, so only literals are permitted as members. Unions may include any number of literal-typed expressions.
+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 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'
@@ -362,11 +362,11 @@ type BarConfig = {
 param ServiceConfig  FooConfig | BarConfig | { type: 'baz', *: string } = { type: 'bar', value: true }
 ```
 
-The parameter value is validated based on the discriminated property value. For instance, in the preceding example, if the _serviceConfig_ parameter is of type _foo_, it is validated using the _FooConfig_ type. Similarly, if the parameter is of type _bar_, it is validated using the _BarConfig_ type. This pattern applies to other types as well.
+The parameter value is validated based on the discriminated property value. For instance, in the preceding example, if the _serviceConfig_ parameter is of type _foo_, it's validated using the _FooConfig_ type. Similarly, if the parameter is of type _bar_, it's validated using the _BarConfig_ type. This pattern applies to other types as well.
 
 There are some limitations with union type.
 
-* Union types must be reduceable to a single ARM type.  The following definition is invalid:
+* Union types must be reducible to a single Azure Resource Manager (ARM) type.  The following definition is invalid:
 
   ```bicep
   type foo = 'a' | 1

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

@@ -14,7 +14,7 @@ Resource Manager resolves parameter values before starting the deployment operat
 
 Each parameter must be set to one of the [data types](data-types.md).
 
-You're limited to 256 parameters in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+Bicep allows a maximum of 256 parameters. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 For parameter best practices, see [Parameters](./best-practices.md#parameters).
 
@@ -59,7 +59,7 @@ param storageAccountConfig {
 }
 ```
 
-For more information, see [User-defined data types](./user-defined-data-types.md#user-defined-data-type-syntax).
+For more information, see [User-defined data types](./user-defined-data-types.md#syntax).
 
 ## Default value
 
@@ -105,7 +105,7 @@ The following table describes the available decorators and how to use them.
 
 | Decorator | Apply to | Argument | Description |
 | --------- | ---- | ----------- | ------- |
-| [allowed](#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 may also be used in `param` statements.|
+| [allowed](#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.|
 | [description](#description) | all | string | Text that explains how to use the parameter. The description is displayed to users through the portal. |
 | [maxLength](#length-constraints) | array, string | int | The maximum length for string and array parameters. The value is inclusive. |
 | [maxValue](#integer-constraints) | int | int | The maximum value for the integer parameter. This value is inclusive. |
@@ -203,7 +203,7 @@ When you hover your cursor over **storageAccountName** in VS Code, you see the f
 
 :::image type="content" source="./media/parameters/vscode-bicep-extension-description-decorator-markdown.png" alt-text="Use Markdown-formatted text in VSCode":::
 
-Make sure the text follows proper Markdown formatting; otherwise, it may not display correctly when rendered
+Make sure the text follows proper Markdown formatting; otherwise, it may not display correctly when rendered.
 
 ### Metadata
 
@@ -220,7 +220,7 @@ You might use this decorator to track information about the parameter that doesn
 param settings object
 ```
 
-When you provide a `@metadata()` decorator with a property that conflicts with another decorator, that decorator always takes precedence over anything in the `@metadata()` decorator. So, the conflicting property within the @metadata() value is redundant and will be replaced. For more information, see [No conflicting metadata](./linter-rule-no-conflicting-metadata.md).
+When you provide a `@metadata()` decorator with a property that conflicts with another decorator, that decorator always takes precedence over anything in the `@metadata()` decorator. So, the conflicting property within the `@metadata()` value is redundant and will be replaced. For more information, see [No conflicting metadata](./linter-rule-no-conflicting-metadata.md).
 
 ## Use parameter
 

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

@@ -12,7 +12,7 @@ Learn how to use user-defined data types in Bicep. For system-defined data types
 
 [Bicep CLI version 0.12.X or higher](./install.md) is required to use this feature.
 
-## The syntax
+## Syntax
 
 You can use the `type` statement to define user-defined data types. In addition, you can also use type expressions in some places to define custom types.