update

Author: mumian

articles/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md

@@ -177,8 +177,8 @@ Use the following procedure to add the application definition:
 
     :::image type="content" source="./media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/bicep-extensibility-kubernetes-provider-import-kubernetes-manifest.png" alt-text="Screenshot of Visual Studio Code import Kubernetes Manifest":::
 
-1. In the prompt, select **azure-vote.yml**. This process creates an **azure-vote.bicep** in the same folder.
-1. At the end of **azure-vote.bicep**, add the following line to output the load balancer public IP.
+1. Select **azure-vote.yml** from the prompt. This process creates an **azure-vote.bicep** in the same folder.
+1. Open **azure-vote.bicep**, add the following line at the end of the file to output the load balancer public IP.
 
     ```bicep
     output frontendIp string = coreService_azureVoteFront.status.loadBalancer.ingress[0].ip

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

@@ -46,8 +46,8 @@ You can enable preview features by adding:
 
 The preceding sample enables two features:
 
-- userDefineType: enable [user-defined types in Bicep](https://aka.ms/bicepCustomTypes).
-- extensibility: enable [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
+- **userDefineType**: enable [user-defined types in Bicep](https://aka.ms/bicepCustomTypes).
+- **extensibility**: enable [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
 
 ## Next steps
 

articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md

@@ -23,7 +23,7 @@ This preview feature can be enabled by configuring the [bicepconfig.json](./bice
 
 ## Import Kubernetes provider
 
-Deployments of Kubernetes must be contained within a [Bicep module file](./modules.md). To import the Kubernetes provider, use the [import statement](./bicep-import-providers.md). After importing the provider, you can refactor the Bicep module file as usual, such as by using variables and parameters. The Kubernetes manifest in YML does not include any programmability support by contract.
+Deployments of Kubernetes must be contained within a [Bicep module file](./modules.md). To import the Kubernetes provider, use the [import statement](./bicep-import-providers.md). After importing the provider, you can refactor the Bicep module file as usual, such as by using variables, parameters, and output. By contract, The Kubernetes manifest in YML does not include any programmability support.
 
 The following sample imports the Kubernetes provider:
 
@@ -55,7 +55,7 @@ module kubernetes './kubernetes.bicep' = {
 }
 ```
 
-The AKS cluster can be a new resource or an existing resource. The [Import Kubernetes manifest command](./visual-studio-code.md#bicep-commands) from Visual Studio Code can automatically add the import snippet automatically.
+The AKS cluster can be a new resource or an existing resource. The [Import Kubernetes manifest command](./visual-studio-code.md#bicep-commands) from Visual Studio Code can automatically add the import snippet.
 
 ## Visual Studio Code import