update toc, redirection, and change article name

Author: erik-ha-msft

.openpublishing.redirection.json

@@ -2385,7 +2385,12 @@
     },
     {
       "source_path_from_root": "/articles/aks/aks-ssh.md",
-      "redirect_url": "/azure/aks/ssh",
+      "redirect_url": "/azure/aks/node-access",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/aks/node-access.md",
+      "redirect_url": "/azure/aks/node-access",
       "redirect_document_id": true
     },
     {

articles/aks/TOC.yml

@@ -474,7 +474,7 @@
         - name: Common issues
           href: troubleshooting.md
         - name: Node access
-          href: ssh.md
+          href: node-access.md
         - name: Linux performance tools
           href: troubleshoot-linux.md
         - name: Check for Resource Health events (preview)

articles/aks/ssh.md renamed to articles/aks/node-access.md

@@ -57,6 +57,14 @@ This privileged container gives access to the node.
 > [!NOTE]
 > You can interact with the node session by running `chroot /host` from the privileged container.
 
+### Remove Linux node access
+
+When done, `exit` the interactive shell session. After the interactive container session closes, delete the pod used for access with `kubectl delete pod`.
+
+```output
+kubectl delete pod node-debugger-aks-nodepool1-12345678-vmss000000-bkmmx
+```
+
 ## Create the SSH connection to a Windows node
 
 At this time, you can't connect to a Windows Server node directly by using `kubectl debug`. Instead, you need to first connect to another node in the cluster, then connect to the Windows Server node from that node using SSH. Alternatively, you can [connect to Windows Server nodes using remote desktop protocol (RDP) connections][aks-windows-rdp] instead of using SSH.
@@ -125,9 +133,9 @@ The above example connects to port 22 on the Windows Server node through port 20
 >  ssh -o 'ProxyCommand ssh -p 2022 -W %h:%p [email protected]' -o PreferredAuthentications=password [email protected]
 > ```
 
-## Remove SSH access
+### Remove SSH access
 
-When done, `exit` the SSH session, stop any port forwarding, and then `exit` the interactive container session. After the interactive container session closes, delete the pod used for access with `kubectl delete pod`.
+When done, `exit` the SSH session, stop any port forwarding, and then `exit` the interactive container session. After the interactive container session closes, delete the pod used for SSH access with `kubectl delete pod`.
 
 ```output
 kubectl delete pod node-debugger-aks-nodepool1-12345678-vmss000000-bkmmx