update

Author: mumian

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

@@ -234,7 +234,7 @@ Use the following procedure to add the application definition:
 
 2. From the deployment output, look for the **outputs** section. For example:
 
-    ```bicep
+    ```json
     "outputs": {
       "controlPlaneFQDN": {
         "type": "String",

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

@@ -40,7 +40,7 @@ import '[email protected]' with {
 - **namespace**: Specify the namespace of the provider.
 - **KubeConfig**: Specify a base64 encoded value of the [Kubernetes cluster admin credentials](/rest/api/aks/managed-clusters/list-cluster-admin-credentials).
 
-The following sample shows how to pass `kubeConfig` value from parent Bicep file:
+The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
 
 ```bicep
 resource aks 'Microsoft.ContainerService/managedClusters@2022-05-02-preview' existing = {
@@ -59,7 +59,7 @@ The AKS cluster can be a new resource or an existing resource. The [Import Kuber
 
 ## Visual Studio Code import
 
-From Visual Studio Code, you can import Kubernetes manifest files to create Bicep module files. For more information, see [Visual Studio Code](./visual-studio-code.md#bicep-commands)
+From Visual Studio Code, you can import Kubernetes manifest files to create Bicep module files. For more information, see [Visual Studio Code](./visual-studio-code.md#bicep-commands).
 
 ## Next steps
 

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

@@ -19,7 +19,9 @@ import '<provider-name>@<provider-version>' with {
 }
 ```
 
-See [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md) for an example of using the Import statement.
+## Kubernetes provider
+
+See [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
 
 ## Next steps
 

articles/azure-resource-manager/bicep/toc.yml

@@ -263,7 +263,7 @@
     href: variables.md
     displayName: configuration
   - name: Import (import)
-    href: bicep-import-schemas.md
+    href: bicep-import-providers.md
   - name: Resources (resource)
     href: resource-declaration.md
   - name: Existing resources (existing)