add top-level metadata

Author: mumian

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

@@ -3,7 +3,7 @@ title: Bicep file structure and syntax
 description: Describes the structure and properties of a Bicep file using declarative syntax.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 05/01/2023
+ms.date: 05/24/2023
 ---
 
 # Understand the structure and syntax of Bicep files
@@ -84,8 +84,6 @@ module webModule './webApp.bicep' = {
 
 Metadata in Bicep is an untyped value that can be included in Bicep files. It allows you to provide supplementary information about your Bicep files, including details like its name, description, author, creation date, and more.
 
-When assigning identifiers for metadata, [`param`](#parameters), [`var`](#variables), [`resource`](#resources), [`module`](#modules), and [`output`](#outputs), it's important to note that they share the same namespace as [decorators](./parameters.md#decorators) and [Bicep functions](./bicep-functions.md). Therefore, using the same identifier for metadata and a decorator (or a Bicep function) can cause confusion. It's advisable to choose a unique identifier that doesn't conflict with a decorator or a function. For instance, instead of using **description** as the metadata identifier, you could use **bicepDescription** to differentiate it from the **@description** decorator in the preceding example.
-
 ## Target scope
 
 By default, the target scope is set to `resourceGroup`. If you're deploying at the resource group level, you don't need to set the target scope in your Bicep file.