Merge pull request #287627 from paulth1/six-bicep-articles

[AQ] edit pass: Six bicep articles

Author: ShawnJackson

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

@@ -1,18 +1,18 @@
 ---
 title: Imports in Bicep
-description: Describes how to import shared functionality and namespaces in Bicep.
+description: This article describes how to import shared functionality and namespaces in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 08/20/2024
 ---
 
 # Imports in Bicep
 
-This article describes the syntax you use to export and import shared functionality, and namespaces for Bicep extensions.
+This article describes the syntax you use to export and import shared functionality and namespaces for Bicep extensions.
 
 ## Export variables, types, and functions
 
-The `@export()` decorator indicates that a given statement can be imported by another file. This decorator is only valid on [`type`](./user-defined-data-types.md), [`var`](./variables.md), and [`func`](./user-defined-functions.md) statements. Variable statements marked with `@export()` must be compile-time constants.
+The `@export()` decorator indicates that another file can import a specific statement. This decorator is only valid on [`type`](./user-defined-data-types.md), [`var`](./variables.md), and [`func`](./user-defined-functions.md) statements. Variable statements marked with `@export()` must be compile-time constants.
 
 The syntax for exporting functionality for use in other Bicep files is:
 
@@ -41,15 +41,15 @@ Using the wildcard import syntax:
 import * as <alias_name> from '<bicep_file_name>'
 ```
 
-You can mix and match the preceding syntaxes. To access imported symbols using the wildcard syntax, you must use the `.` operator: `<alias_name>.<exported_symbol>`.
+You can mix and match the preceding syntaxes. To access imported symbols by using the wildcard syntax, you must use the `.` operator: `<alias_name>.<exported_symbol>`.
 
-Only statements that have been [exported](#export-variables-types-and-functions) in the file being referenced are available to be imported.
+Only statements that were [exported](#export-variables-types-and-functions) in the file being referenced are available for import.
 
-Functionality that has been imported from another file can be used without restrictions. For example, imported variables can be used anywhere a variable declared in-file would normally be valid.
+You can use functionality that was imported from another file without restrictions. For example, you can use imported variables anywhere that a variable declared in-file would normally be valid.
 
 ### 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'
@@ -80,7 +80,7 @@ output greeting string = sayHello('Bicep user')
 output exampleObject myImports.myObjectType = exampleObject
 ```
 
-## Import namespaces and extensions (Preview)
+## Import namespaces and extensions (preview)
 
 > [!NOTE]
 > The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
@@ -110,9 +110,9 @@ import '<extension-name>@<extension-version>' with {
 
 For an example, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 
-## Next steps
+## Related content
 
-- To learn about the Bicep data types, see [Data types](./data-types.md).
-- To learn about the Bicep functions, see [Bicep functions](./bicep-functions.md).
-- To learn about how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
-- To go through a Kubernetes extension tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension.](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
+- To learn about Bicep data types, see [Data types](./data-types.md).
+- To learn about Bicep functions, see [Bicep functions](./bicep-functions.md).
+- To learn how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
+- To go through a Kubernetes extension tutorial, see [Quickstart: Deploy Azure applications to Azure Kubernetes Services by using the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).

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>'