acrolinx

Author: mumian

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

@@ -325,7 +325,7 @@ var storageName = 'storage${uniqueString(resourceGroup().id)}'
 In Bicep, multi-line strings are defined between three single quotation marks (`'''`) followed optionally by a newline (the opening sequence) and three single quotation marks (`'''` is the closing sequence). Characters that are entered between the opening and closing sequence are read verbatim. Escaping isn't necessary or possible.
 
 > [!NOTE]
-> The Bicep parser reads every characters as it is. Depending on the line endings of your Bicep file, newlines are interpreted as either `\r\n` or `\n`.
+> The Bicep parser reads every character as it is. Depending on the line endings of your Bicep file, newlines are interpreted as either `\r\n` or `\n`.
 >
 > Interpolation isn't currently supported in multi-line strings. Because of this limitation, you might need to use the [`concat`](./bicep-functions-string.md#concat) function instead of using [interpolation](#strings).
 >

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

@@ -442,7 +442,7 @@ The preceding example is equivalent to:
 type accountKind = 'BlobStorage' | 'BlockBlobStorage' | 'FileStorage' | 'Storage' | 'StorageV2'
 ```
 
-The following example shows how to use `resourceInput<>` to create a strongly-typed parameter based on the `properties` of a storage account resource. This allows you to define a parameter that matches the writable properties of a storage account, such as `accessTier`, `minimumTlsVersion`, and others:
+The following example shows how to use `resourceInput<>` to create a strongly typed parameter based on the `properties` of a storage account resource. This allows you to define a parameter that matches the writable properties of a storage account, such as `accessTier`, `minimumTlsVersion`, and others:
 
 ```bicep
 // Strongly typed variable using the .properties path of a storage account
@@ -465,7 +465,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
 }
 ```
 
-The following example shows how to use `resourceOutput<>` to create a strongly-typed output based on the `primaryEndPoints` of a storage account resource.
+The following example shows how to use `resourceOutput<>` to create a strongly typed output based on the `primaryEndPoints` of a storage account resource.
 
 ```bicep
 output storageEndpoints resourceOutput<'Microsoft.Storage/storageAccounts@2024-01-01'>.properties.primaryEndpoints = ...