Merge pull request #239963 from James-Green-Microsoft/trial-feedback-fixes

Trial feedback fixes

Author: prmerger-automator[bot]

articles/private-5g-core/commission-cluster.md

@@ -54,14 +54,12 @@ WinRM may already be enabled on your machine, as you only need to do it once. En
 
 1. At the prompt, enter your Azure Stack Edge password. Ignore the following message:
 
-    ```powershell
-   WARNING: The Windows PowerShell interface of your device is intended to
+    `WARNING: The Windows PowerShell interface of your device is intended to
    be used only for the initial network configuration. Please
    engage Microsoft Support if you need to access this interface
    to troubleshoot any potential issues you may be experiencing.
    Changes made through this interface without involving Microsoft
-   Support could result in an unsupported configuration.
-    ```
+   Support could result in an unsupported configuration.`
 
 You now have a minishell session set up ready to enable your Azure Kubernetes Service in the next step.
 
@@ -177,12 +175,18 @@ The page should now look like the following image:
 :::image type="content" source="media/commission-cluster/commission-cluster-kubernetes-preview-enabled.png" alt-text="Screenshot showing Kubernetes (Preview) with two tables. The first table is called Compute virtual switch and the second is called Virtual network. A green tick shows that the virtual networks are enabled for Kubernetes.":::
 :::zone-end
 
-## Start the cluster and set up Arc
+## Enable VM management on the ASE
 
-Access the Azure portal and go to the **Azure Stack Edge** resource created in the Azure portal.
+1. Access the Azure portal and go to the **Azure Stack Edge** resource created in the Azure portal.
+1. Select **Edge services**.
+1. Select **Virtual machines**.
+1. Select **Enable**.
+
+## Start the cluster and set up Arc
 
 If you're running other VMs on your Azure Stack Edge, we recommend that you stop them now, and start them again once the cluster is deployed. The cluster requires access to specific CPU resources that running VMs may already be using.
 
+1. Access the Azure portal and go to the **Azure Stack Edge** resource created in the Azure portal.
 1. To deploy the cluster, select the **Kubernetes** option and then select the **Add** button to configure the cluster.
 
    :::image type="content" source="media/commission-cluster/commission-cluster-add-kubernetes.png" alt-text="Screenshot of Kubernetes Overview pane, showing the Add button to configure Kubernetes service.":::
@@ -194,7 +198,7 @@ If you're running other VMs on your Azure Stack Edge, we recommend that you stop
 
 The creation of the Kubernetes cluster takes about 20 minutes. During creation, there may be a critical alarm displayed on the **Azure Stack Edge** resource. This alarm is expected and should disappear after a few minutes.
 
-Once deployed, the portal should show  **Kubernetes service is healthy** on the overview page.
+Once deployed, the portal should show  **Kubernetes service is running** on the overview page.
 
 ## Set up kubectl access
 
@@ -240,13 +244,17 @@ You can now view information about what’s running on the cluster – the follo
 
 You should verify that the AKS cluster is set up correctly by running the following *kubectl* commands using the *kubeconfig* downloaded from the UI in [Set up kubectl access](#set-up-kubectl-access):
 
-`kubectl get nodes`
+```azurecli
+kubectl get nodes
+```
 
 This command should return two nodes, one named *nodepool-aaa-bbb* and one named *target-cluster-control-plane-ccc*.
 
 To view all the running pods, run:
 
-`kubectl get pods -A`
+```azurecli
+kubectl get pods -A
+```
 
 Additionally, your AKS cluster should now be visible from your Azure Stack Edge resource in the portal.
 
@@ -302,8 +310,10 @@ The Azure Private 5G Core private mobile network requires a custom location and
       "helm.release-namespace": "azurehybridnetwork",
       "managed-by": "helm"
     }
-    "@
+    "@ 
+    ```
 
+    ```azurecli
     az k8s-extension create `
     --name networkfunction-operator `
     --cluster-name "$ARC_CLUSTER_RESOURCE_NAME" `

articles/private-5g-core/data-plane-packet-capture.md

@@ -29,11 +29,15 @@ Data plane packet capture works by mirroring packets to a Linux kernel interface
 
 1. In a command line with kubectl access to the Azure Arc-enabled Kubernetes cluster, enter the UPF-PP troubleshooter pod:
 
-    `kubectl exec -it -n core core-upf-pp-0 -c troubleshooter -- bash`
+    ```azurecli
+    kubectl exec -it -n core core-upf-pp-0 -c troubleshooter -- bash
+    ```
 
 1. View the list of interfaces that can be monitored:
 
-    `upft list`
+    ```azurecli
+    upft list
+    ```
 
 1. Run `upftdump` with any parameters that you would usually pass to tcpdump. In particular, `-i` to specify the interface, and `-w` to specify where to write to. Close the UPFT tool when done by pressing <kbd>Ctrl + C</kbd>. The following examples are common use cases:
     - To run capture packets on all interfaces run `upftdump -i any -w any.pcap`
@@ -43,17 +47,23 @@ Data plane packet capture works by mirroring packets to a Linux kernel interface
     > Packet capture files may be large, particularly when running packet capture on all interfaces. Specify filters when running packet capture to reduce the file size - see the tcpdump documentation for the available filters.
 1. Leave the container:
 
-    `exit`
+    ```azurecli
+    exit
+    ```
 
 1. Copy the output files:
 
-    `kubectl cp -n core core-upf-pp-0: <path to output file> <location to copy to> -c troubleshooter`
+    ```azurecli
+    kubectl cp -n core core-upf-pp-0:<path to output file> <location to copy to> -c troubleshooter
+    ```
 
     The `tcpdump` may have been stopped in the middle of writing a packet, which can cause this step to produce an error stating `unexpected EOF`. However, your file should have copied successfully, but you can check your target output file to confirm.
 
 1. Remove the output files:
 
-    `kubectl exec -it -n core core-upf-pp-0 -c troubleshooter -- rm <path to output file>`
+    ```azurecli
+        kubectl exec -it -n core core-upf-pp-0 -c troubleshooter -- rm <path to output file>`
+    ```
 
 ## Next steps