update

Author: mumian

articles/azure-resource-manager/bicep/linter-rule-secure-params-in-nested-deploy.md

@@ -7,7 +7,7 @@ ms.date: 09/21/2022
 
 # Linter rule - secure params in nested deploy
 
-Outer-scoped nested deployment resources should not be used for secure parameters or list* functions. You could expose the secure parameter values in the deployment history.
+Outer-scoped nested deployment resources shouldn't be used for secure parameters or list* functions. You could expose the secure parameter values in the deployment history.
 
 ## Linter rule code
 
@@ -17,7 +17,7 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
 
 ## Solution
 
-Either set the [deployment's properties.expressionEvaluationOptions.scope](/azure/templates/microsoft.resources/deployments?pivots=deployment-language-bicep) to 'inner' or use a Bicep module instead.
+Either set the [deployment's properties.expressionEvaluationOptions.scope](/azure/templates/microsoft.resources/deployments?pivots=deployment-language-bicep) to `inner` or use a Bicep module instead.
 
 The following example fails this test because a secure parameter is used in an outer-scoped nested deployment resource.
 

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

@@ -72,15 +72,15 @@ You can integrate these checks as a part of your CI/CD pipelines. You can use a
 
 ## Silencing false positives
 
-Sometimes a rule can have false positives. For example you may need to include a link to a blob storage directly without using the [environment()](./bicep-functions-deployment.md#environment) function.
+Sometimes a rule can have false positives. For example, you may need to include a link to a blob storage directly without using the [environment()](./bicep-functions-deployment.md#environment) function.
 In this case you can disable the warning for one line only, not the entire document, by adding `#disable-next-line <rule name>` before the line with the warning.
 
 ```bicep
 #disable-next-line no-hardcoded-env-urls //Direct download link to my toolset
 scriptDownloadUrl: 'https://mytools.blob.core.windows.net/...'
 ```
 
-It is good practice to add a comment explaining why the rule does not apply to this line.
+It's good practice to add a comment explaining why the rule doesn't apply to this line.
 
 ## Next steps