diff --git a/Debugging-using-with-ssh-for-Github-Actions.md b/Debugging-using-with-ssh-for-Github-Actions.md
index 183f414..71f533e 100644
--- a/Debugging-using-with-ssh-for-Github-Actions.md
+++ b/Debugging-using-with-ssh-for-Github-Actions.md
@@ -5,23 +5,16 @@
 - [x] Linux (https://github.com/pytorch/pytorch/pull/62280)
 - [x] Windows (https://github.com/pytorch/pytorch/pull/63440)
 
-## Comparisons to CircleCI’s Re-run with SSH
+## Conditions and Limitations
 
-### Similarities
-
-* 2 hour time limit after job has finished for when SSH sessions will be closed out and runner will return to the regular runner pool
+* **The job must still be running when you ssh into the machine.**  If the job is finished running, you cannot ssh in.
+* Only works on your own PRs.  If you want to ssh into a job running on the main or someone else's job, see the below section about aws ssm.
+* You will be removed from the machine after 2 hours.
+* Only works for users who are connected to the Meta VPN
+  * No current planned support for outside collaborators
 * Public keys for ssh are pulled from Github using `https://github.com/${github.actor}.keys`
     * Example: https://github.com/seemethere.keys
 
-### Differences
-
-* Only works for users who are connected to the Meta VPN
-
-## Known limitations
-
-* Only works for users who are connected to the Meta VPN
-    * No current planned support for outside collaborators yet
-
 ## Workflow for users
 
 1. Push a new commit / re-run completed workflows, see below for re-running jobs through the Github UI <br>