Update use-pod-sandboxing.md

Author: miwithro

articles/aks/use-pod-sandboxing.md

@@ -234,7 +234,7 @@ To demonstrate the deployed application on the AKS cluster isn't isolated and is
 
     ```output
     root@untrusted:/# uname -r
-    5.15.48.1-8.cm2
+    5.15.80.mshv2-hvl1.m2
     ```
 
 3. Start a shell session to the container of the *trusted* pod to verify the kernel output:
@@ -252,7 +252,7 @@ To demonstrate the deployed application on the AKS cluster isn't isolated and is
    The following example resembles output from the VM that is running the *trusted* pod, which is a different kernel than the *untrusted* pod running within the pod sandbox:
 
     ```output
-    5.15.80.mshv2-hvl1.m2
+    5.15.48.1-8.cm2
 
 ## Cleanup
 
@@ -308,4 +308,4 @@ kubectl delete pod pod-name
 [csi-secret-store driver]: csi-secrets-store-driver.md
 [az-aks-update]: /cli/azure/aks#az-aks-update
 [mariner-cluster-config]: cluster-configuration.md#mariner-os
-[register-the-katavmisolationpreview-feature-flag]: #register-the-katavmisolationpreview-feature-flag
+[register-the-katavmisolationpreview-feature-flag]: #register-the-katavmisolationpreview-feature-flag