update

Author: mumian

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

@@ -232,18 +232,18 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 
 Decorators are written in the format `@expression` and are placed above the declarations of the user-defined data type. The following table shows the available decorators for user-defined data types.
 
-| Decorator | Argument | Description |
+| Decorator | Apply to | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string | Provide descriptions for the user-defined data type. |
-| [discriminator](#discriminator) | string | Use this decorator to ensure the correct subclass is identified and managed. |
-| [export](#export) | none | Indicates that the user-defined data type is available for import by another Bicep file. |
+| [description](#description) | all |string | Provide descriptions for the user-defined data type. |
+| [discriminator](#discriminator) | object | string | Use this decorator to ensure the correct subclass is identified and managed. |
+| [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. |
 | [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) | 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).|
-| [secure](#secure-parameters) | 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). |
+| [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).|
+| [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.
 

articles/azure-resource-manager/bicep/user-defined-functions.md

@@ -110,7 +110,7 @@ Decorators are written in the format `@expression` and are placed above function
 | --------- | ----------- | ------- |
 | [description](#description) | string | Provide descriptions for the function. |
 | [export](#export) | none | Indicates that the function is available for import by another Bicep file. |
-| [metadata](#metadata) | all | object | Custom properties to apply to the function. Can include a description property that is equivalent to the description decorator. |
+| [metadata](#metadata) | object | Custom properties to apply to the function. Can include a description property that is equivalent to 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 using the **description** decorator.