acrolinx

Author: mumian

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

@@ -11,7 +11,7 @@ Bicep supports a configuration file named `bicepconfig.json`. Within this file,
 
 To customize values, create this file in the directory where you store Bicep files. You can add `bicepconfig.json` files in multiple directories. The configuration file closest to the Bicep file in the directory hierarchy is used.
 
-## Create the config file in VSCode
+## Create the config file in Visual Studio Code
 
 You can use any text editor to create the config file.
 
@@ -46,10 +46,10 @@ The following sample enables the [user-defined types in Bicep](https://aka.ms/bi
 The available experimental features include:
 
 - **extensibility**: Allows Bicep to use a provider model to deploy non-ARM resources. Currently, we only support a Kubernetes provider.
-- **paramsFiles**: Allows for the use of a Bicep-style parameters file with a terser syntax than the JSON equivalent parameters file. Currently, you also need a special build of Bicep to enable this feature, so is it inaccessbile to the majority of users. See [Parameters - first release](https://github.com/Azure/bicep/issues/9567).
+- **paramsFiles**: Allows for the use of a Bicep-style parameters file with a terser syntax than the JSON equivalent parameters file. Currently, you also need a special build of Bicep to enable this feature, so is it inaccessible to most users. See [Parameters - first release](https://github.com/Azure/bicep/issues/9567).
 - **sourceMapping**: Enables basic source mapping to map an error location returned in the ARM template layer back to the relevant location in the Bicep file.
 - **resourceTypedParamsAndOutputs**: Enables the type for a parameter or output to be of type resource to make it easier to pass resource references between modules. This feature is only partially implemented. See[Simplifying resource referencing](https://github.com/azure/bicep/issues/2245).
-- **symbolicNameCodegen**: Enable this feature to use a new schema in the ARM template layer to represent resources as an object dictionary instead of an array of objects. This makes the Bicep and ARM template more semantically equivalent and leads to more reliable code generation. Enabling this does not result in any functionality changes in the Bicep layer.
+- **symbolicNameCodegen**: Enable this feature to use a new schema in the ARM template layer to represent resources as an object dictionary instead of an array of objects. This feature makes the Bicep and ARM template more semantically equivalent and leads to more reliable code generation. Enabling this feature doesn't result in any functionality changes in the Bicep layer.
 - **userDefinedTypes**: Define your own custom types for parameters. See [User-defined types in Bicep](https://aka.ms/bicepCustomTypes).
 
 ## Next steps