edit pass: six-bicep-articles

Author: paulth1

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

@@ -1,6 +1,6 @@
 ---
 title: User-defined types in Bicep
-description: Describes how to define and use user-defined data types in Bicep.
+description: This article describes how to define and use user-defined data types in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 08/20/2024
@@ -14,14 +14,14 @@ Learn how to create user-defined data types in Bicep. For system-defined data ty
 
 ## Define types
 
-You can use the `type` statement to create user-defined data types. In addition, you can also use type expressions in some places to define custom types.
+You can use the `type` statement to create user-defined data types. You can also use type expressions in some places to define custom types.
 
 ```bicep
 @<decorator>(<argument>)
 type <user-defined-data-type-name> = <type-expression>
 ```
 
-The [`@allowed`](./parameters.md#use-decorators) decorator is only permitted on [`param` statements](./parameters.md). To declare a type with a set of predefined values in a `type`, use [union type syntax](./data-types.md#union-types).
+The [`@allowed`](./parameters.md#use-decorators) decorator is permitted only on [`param` statements](./parameters.md). To declare a type with a set of predefined values in a `type`, use [union type syntax](./data-types.md#union-types).
 
 The valid type expressions include:
 
@@ -35,7 +35,7 @@ The valid type expressions include:
     type myOtherStringType = myStringType
     ```
 
-- Primitive literals, including strings, integers, and booleans, are valid type expressions. For example:
+- Primitive literals, including strings, integers, and Booleans, are valid type expressions. For example:
 
     ```bicep
     // a string type with three allowed values.
@@ -71,7 +71,7 @@ The valid type expressions include:
     }
     ```
 
-    Each property in an object consists of a key and a value, separated by a colon `:`. The key can be any string, with nonidentifier values enclosed in quotes, and the value can be any type of expression.
+    Each property in an object consists of a key and a value separated by a colon `:`. The key can be any string, with nonidentifier values enclosed in quotation marks. The value can be any type of expression.
 
     Properties are required unless they have an optionality marker `?` after the property value. For example, the `sku` property in the following example is optional:
 
@@ -82,7 +82,7 @@ The valid type expressions include:
     }
     ```
 
-  Decorators can be used on properties. `*` can be used to make all values require a constraint. Additional properties can still be defined when using `*`. This example creates an object that requires a key of type `int` named *id*, and that all other entries in the object must be a string value at least 10 characters long.
+  You can use decorators on properties. You can use an asterisk (`*`) to make all values require a constraint. You can define more properties by using `*`. This example creates an object that requires a key of type `int` named `id`. All other entries in the object must be a string value at least 10 characters long.
 
     ```bicep
     type obj = {
@@ -105,9 +105,9 @@ The valid type expressions include:
     }
     ```
 
-    **Recursion**
+  ### Recursion
 
-    Object types can use direct or indirect recursion so long as at least leg of the path to the recursion point is optional. For example, the `myObjectType` definition in the following example is valid because the directly recursive `recursiveProp` property is optional:
+    Object types can use direct or indirect recursion if at least the leg of the path to the recursion point is optional. For example, the `myObjectType` definition in the following example is valid because the directly recursive `recursiveProp` property is optional:
 
     ```bicep
     type myObjectType = {
@@ -116,7 +116,7 @@ The valid type expressions include:
     }
     ```
 
-    But the following type definition wouldn't be valid because none of `level1`, `level2`, `level3`, `level4`, or `level5` is optional.
+    The following type definition wouldn't be valid because none of `level1`, `level2`, `level3`, `level4`, or `level5` is optional.
 
     ```bicep
     type invalidRecursiveObjectType = {
@@ -132,7 +132,7 @@ The valid type expressions include:
     }
     ```
 
-- [Bicep unary operators](./operators.md) can be used with integer and boolean literals or references to integer or boolean literal-typed symbols:
+- You can use [Bicep unary operators](./operators.md) with integer and Boolean literals or references to integer or Boolean literal-typed symbols:
 
     ```bicep
     type negativeIntLiteral = -10
@@ -149,7 +149,7 @@ The valid type expressions include:
     type mixedTypeArray = ('fizz' | 42 | {an: 'object'} | null)[]
     ```
 
-In addition to be used in the `type` statement, type expressions can also be used in these places for creating user-defined data types:
+You can use type expressions in the `type` statement, and you can also use type expressions to create user-defined data types, as shown in the following places:
 
 - As the type clause of a `param` statement. For example:
 
@@ -204,7 +204,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 }
 ```
 
-By using user-defined data types, it can look like:
+With user-defined data types, it can look like:
 
 ```bicep
 param location string = resourceGroup().location
@@ -239,21 +239,21 @@ Decorators are written in the format `@expression` and are placed above the decl
 | [export](#export) | all | none | Indicates that the user-defined data type is available for import by another Bicep file. |
 | [maxLength](#length-constraints) | array, string | int | The maximum length for string and array data types. The value is inclusive. |
 | [maxValue](#integer-constraints) | int | int | The maximum value for the integer data types. This value is inclusive. |
-| [metadata](#metadata) | all | object | Custom properties to apply to the data types. Can include a description property that is equivalent to the description decorator. |
+| [metadata](#metadata) | all | object | Custom properties to apply to the data types. Can include a description property that's equivalent to the description decorator. |
 | [minLength](#length-constraints) | array, string | int | The minimum length for string and array data types. The value is inclusive. |
 | [minValue](#integer-constraints) | int | int | The minimum value for the integer data types. This value is inclusive. |
-| [sealed](#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](#elevate-error-level).|
+| [sealed](#sealed) | object | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a user-defined data type is likely a typo. For more information, see [Elevate error level](#elevate-error-level).|
 | [secure](#secure-types) | string, object | none | Marks the types as secure. The value for a secure type 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). |
 
-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 variable named `description`, you must add the sys namespace when using the **description** decorator.
+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 variable named `description`, you must add the `sys` namespace when you use the `description` decorator.
 
 ### Discriminator
 
 See [Tagged union data type](#tagged-union-data-type).
 
 ### Description
 
-Add a description to the user-defined data type. Decorators can be used on properties. For example:
+Add a description to the user-defined data type. You can use decorators on properties. For example:
 
 ```bicep
 @description('Define a new object type.')
@@ -267,7 +267,7 @@ type obj = {
 }
 ```
 
-Markdown-formatted text can be used for the description text.
+You can use Markdown-formatted text for the description text.
 
 ### Export
 
@@ -287,7 +287,7 @@ type month int
 
 You can specify minimum and maximum lengths for string and array types. You can set one or both constraints. For strings, the length indicates the number of characters. For arrays, the length indicates the number of items in the array.
 
-The following example declares two type. One type is for a storage account name that must have 3-24 characters. The other type is an array that must have from 1-5 items.
+The following example declares two types. One type is for a storage account name that must have 3 to 24 characters. The other type is an array that must have from one to five items.
 
 ```bicep
 @minLength(3)
@@ -314,15 +314,15 @@ You might use this decorator to track information about the data type that doesn
 type 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 is replaced. For more information, see [No conflicting metadata](./linter-rule-no-conflicting-metadata.md).
 
 ### Sealed
 
 See [Elevate error level](#elevate-error-level).
 
 ### Secure types
 
-You can mark string or object user-defined data type as secure. The value of a secure type isn't saved to the deployment history and isn't logged.
+You can mark a string or object user-defined data type as secure. The value of a secure type isn't saved to the deployment history and isn't logged.
 
 ```bicep
 @secure()
@@ -334,7 +334,7 @@ type demoSecretObject object
 
 ## Elevate error level
 
-By default, declaring an object type in Bicep allows it to accept additional properties of any type. For example, the following Bicep is valid but raises a warning of [BCP089] - `The property "otionalProperty" is not allowed on objects of type "{ property: string, optionalProperty: null | string }". Did you mean "optionalProperty"?`:
+By default, declaring an object type in Bicep allows it to accept more properties of any type. For example, the following Bicep is valid but raises a warning of [BCP089]: `The property "otionalProperty" is not allowed on objects of type "{ property: string, optionalProperty: null | string }". Did you mean "optionalProperty"?`:
 
 ```bicep
 type anObject = {
@@ -348,7 +348,7 @@ param aParameter anObject = {
 }
 ```
 
-The warning informs you that the *anObject* type doesn't include a property named *otionalProperty*. While no errors occur during deployment, the Bicep compiler assumes *otionalProperty* is a typo, that you intended to use *optionalProperty* but misspelled it, and alert you to the inconsistency.
+The warning informs you that the `anObject` type doesn't include a property named `otionalProperty`. Although no errors occur during deployment, the Bicep compiler assumes that `otionalProperty` is a typo and that you intended to use `optionalProperty` but misspelled it. Bicep alerts you to the inconsistency.
 
 To escalate these warnings to errors, apply the `@sealed()` decorator to the object type:
 
@@ -375,7 +375,7 @@ param aParameter anObject = {
 }
 ```
 
-The ARM deployment engine also checks sealed types for additional properties. Providing any extra properties for sealed parameters results in a validation error, causing the deployment to fail. For example:
+The Azure Resource Manager deployment engine also checks sealed types for other properties. Providing any extra properties for sealed parameters results in a validation error, which causes the deployment to fail. For example:
 
 ```bicep
 @sealed()
@@ -414,6 +414,6 @@ output config object = serviceConfig
 
 For more information, see [Custom tagged union data type](./data-types.md#custom-tagged-union-data-type).
 
-## Next steps
+## Related content
 
-- For a list of the Bicep data types, see [Data types](./data-types.md).
+For a list of the Bicep data types, see [Data types](./data-types.md).