fixing broken bookmark

Author: paulth1

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

@@ -49,7 +49,7 @@ You can use functionality that was imported from another file without restrictio
 
 ### Example
 
-exports.bicep
+*exports.bicep*
 
 ```bicep
 @export()
@@ -65,7 +65,7 @@ var myConstant = 'This is a constant value'
 func sayHello(name string) string => 'Hello ${name}!'
 ```
 
-main.bicep
+*main.bicep*
 
 ```bicep
 import * as myImports from 'exports.bicep'

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

@@ -29,7 +29,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   using '<path>/<file-name>.json'
   ```
 
-- To use [public modules](./modules.md#path-to-module):
+- To use [public modules](./modules.md#path-to-a-module):
 
   ```bicep
   using 'br/public:<file-path>:<tag>'

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

@@ -18,8 +18,8 @@ Within Bicep, you can use these data types:
 * [bool](#booleans)
 * [int](#integers)
 * [object](#objects)
-* [secureObject is indicated by a decorator in Bicep](#secure-strings-and-objects)
-* [secureString is indicated by a decorator in Bicep](#secure-strings-and-objects)
+* [secureObject (indicated by a decorator in Bicep](#secure-strings-and-objects))
+* [secureString (indicated by a decorator in Bicep](#secure-strings-and-objects))
 * [string](#strings)
 
 ## Arrays
@@ -274,16 +274,16 @@ All strings in Bicep support interpolation. To inject an expression, surround it
 var storageName = 'storage${uniqueString(resourceGroup().id)}'
 ```
 
-### Multiline strings
+### Multi-line strings
 
-In Bicep, multiline 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.
+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 all characters as 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 multiline strings. Because of this limitation, you might need to use the [`concat`](./bicep-functions-string.md#concat) function instead of using [interpolation](#strings).
+> 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).
 >
-> Multiline strings containing `'''` aren't supported.
+> Multi-line strings that contain `'''` aren't supported.
 
 ```bicep
 // evaluates to "hello!"

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

@@ -118,7 +118,7 @@ You can add one or more decorators for each of the following elements:
 * [func](#functions)
 * [type](#types)
 
-The decorators include:
+The following table lists the decorators.
 
 | Decorator | Apply to element | Apply to data type | Argument | Description |
 | --------- | ---- | ----------- | ------- |

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

@@ -63,7 +63,7 @@ module stgModule '../storageAccount.json' = {
 
 Use the symbolic name to reference the module in another part of the Bicep file. For example, you can use the symbolic name to get the output from a module. The symbolic name might contain a-z, A-Z, 0-9, and underscore (`_`). The name can't start with a number. A module can't have the same name as a parameter, variable, or resource.
 
-The path can be either a local file or a file in a registry. The local file can be either a Bicep file or an ARM template for JSON. For more information, see [Path to module](#path-to-module).
+The path can be either a local file or a file in a registry. The local file can be either a Bicep file or an ARM template for JSON. For more information, see [Path to a module](#path-to-a-module).
 
 The `name` property is required. It becomes the name of the nested deployment resource in the generated template.
 

articles/azure-resource-manager/bicep/template-specs.md

@@ -438,7 +438,7 @@ Both the template and its versions can have tags. The tags are applied or inheri
 
 ## Link to template specs
 
-After creating a template spec, you can link to that template spec in a Bicep module. The template spec is deployed when you deploy the Bicep file containing that module. For more information, see [File in template spec](./modules.md#path-to-module).
+After creating a template spec, you can link to that template spec in a Bicep module. The template spec is deployed when you deploy the Bicep file containing that module. For more information, see [File in template spec](./modules.md#path-to-a-module).
 
 To create aliases for template specs intended for module linking, see [Aliases for modules](./bicep-config-modules.md#aliases-for-modules).
 

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

@@ -105,7 +105,7 @@ The valid type expressions include:
     }
     ```
 
-  ### Recursion
+  #### Recursion
 
     Object types can use direct or indirect recursion if at least the leg of the path to the recursion point is optional. For example, the `myObjectType` definition in the following example is valid because the directly recursive `recursiveProp` property is optional: