Merge pull request #291545 from LiSeda/LS-params1

LS_Bicep parameters_batch 1

Author: prmerger-automator[bot]

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

@@ -3,7 +3,7 @@ title: Bicep CLI commands and overview
 description: Describes the commands that you can use in the Bicep CLI. These commands include building Azure Resource Manager templates from Bicep.
 ms.topic: reference
 ms.custom: devx-track-azurecli, devx-track-bicep, devx-track-arm-template
-ms.date: 10/30/2024
+ms.date: 12/06/2024
 ---
 
 # Bicep CLI commands
@@ -116,13 +116,13 @@ The `generate-params` command builds a parameters file from the given Bicep file
 az bicep generate-params --file main.bicep --output-format bicepparam --include-params all
 ```
 
-The command creates a Bicep parameters file named _main.bicepparam_. The parameter file contains all parameters in the Bicep file, whether configured with default values or not.
+The command creates a Bicep parameters file named _main.bicepparam_. The parameters file contains all parameters in the Bicep file, whether configured with default values or not.
 
 ```azurecli
 az bicep generate-params --file main.bicep --outfile main.parameters.json
 ```
 
-The command creates a parameter file named _main.parameters.json_. The parameter file only contains the parameters without default values configured in the Bicep file.
+The command creates a parameters file named _main.parameters.json_. The parameters file only contains the parameters without default values configured in the Bicep file.
 
 ## install
 

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

@@ -1,9 +1,9 @@
 ---
 title: Bicep functions - parameters file
-description: This article describes the Bicep functions to be used in Bicep parameter files.
+description: This article describes the Bicep functions to be used in Bicep parameters files.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 08/09/2024
+ms.date: 12/06/2024
 ---
 
 # Parameters file function for Bicep

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

@@ -3,7 +3,7 @@ title: Bicep functions
 description: Describes the functions to use in a Bicep file to retrieve values, work with strings and numerics, and retrieve deployment information.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 05/21/2024
+ms.date: 12/06/2024
 ---
 
 # Bicep functions
@@ -128,7 +128,7 @@ The following functions are available for working with objects. All of these fun
 
 ## Parameters file functions
 
-The following functions are available to be used in Bicep parameter files. All of these functions are in the `sys` namespace.
+The following functions are available to be used in Bicep parameters files. All of these functions are in the `sys` namespace.
 
 * [getSecret](./bicep-functions-parameters-file.md)
 * [readEnvironmentVariable](./bicep-functions-parameters-file.md)

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

@@ -3,12 +3,12 @@ title: Using statement
 description: Describes how to use the using statement in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/28/2024
+ms.date: 12/06/2024
 ---
 
 # Using statement
 
-The `using` statement in [Bicep parameter files](./parameter-files.md) ties the [Bicep parameters file](./parameter-files.md) to a [Bicep file](./file.md), an [ARM JSON template](../templates/syntax.md), or a [Bicep module](./modules.md), or a [template spec](./template-specs.md). A `using` declaration must be present in any Bicep parameters file.
+The `using` statement in [Bicep parameters files](./parameter-files.md) ties the [Bicep parameters file](./parameter-files.md) to a [Bicep file](./file.md), an [ARM JSON template](../templates/syntax.md), or a [Bicep module](./modules.md), or a [template spec](./template-specs.md). A `using` declaration must be present in any Bicep parameters file.
 
 > [!NOTE]
 > The Bicep parameters file is only supported in [Bicep CLI](./install.md) version 0.18.4 or newer, [Azure CLI](/cli/azure/install-azure-cli) version 2.47.0 or newer, and [Azure PowerShell](/powershell/azure/install-azure-powershell) version 9.7.1 or newer.

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

@@ -3,7 +3,7 @@ title: Data types in Bicep
 description: This article describes the data types that are available in Bicep.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 11/12/2024
+ms.date: 12/06/2024
 ---
 
 # Data types in Bicep
@@ -111,7 +111,7 @@ When you specify integer values, don't use quotation marks.
 param exampleInt int = 1
 ```
 
-Bicep integers are 64-bit integers. When they're passed as inline parameters, the SDK or command-line tool you use for deployment can limit the range of values. For example, when you use PowerShell to deploy 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 they're passed as inline parameters, the SDK or command-line tool you use for deployment can limit the range of values. For example, when you use PowerShell to deploy Bicep, integer types can range from -2147483648 to 2147483647. To avoid this limitation, specify large integer values in a [parameters file](parameter-files.md). Resource types apply their own limits for integer properties.
 
 Bicep supports an integer literal type that refers to a specific value that's an exact integer. In the following example, `1` is an integer literal type, and `foo` can only be assigned the value `1` and no other value.