diff --git a/README.md b/README.md
index b3d4987526a46be3304ca649d90166566c03029e..eed8dd4d91c249dfa4de57f47d79c6ad1e2749e9 100644
--- a/README.md
+++ b/README.md
@@ -83,9 +83,7 @@ foreman start
 If you want to run Zed pointed at the local servers, you can run:
 
 ```
-script/zed-with-local-servers
-# or...
-script/zed-with-local-servers --release
+script/zed-local
 ```
 
 ### Dump element JSON
diff --git a/docs/building-zed.md b/docs/building-zed.md
index 6981913285b5ec8aab22cc73813b86301237e120..ec4538cf85f47d99ee11b24bb876b602eba8249e 100644
--- a/docs/building-zed.md
+++ b/docs/building-zed.md
@@ -75,8 +75,7 @@ Expect this to take 30min to an hour! Some of these steps will take quite a whil
     - If you are just using the latest version, but not working on zed:
       - `cargo run --release`
     - If you need to run the collaboration server locally:
-      - `script/zed-with-local-servers`
-    - If you need to test collaboration with mutl
+      - `script/zed-local`
 
 ## Troubleshooting
 
diff --git a/docs/local-collaboration.md b/docs/local-collaboration.md
index 7d8054af673b5fb38c68bfff0c04a08ded7c2f0a..4c059c0878b4df38a3450a5e4d44787ee10aaf0f 100644
--- a/docs/local-collaboration.md
+++ b/docs/local-collaboration.md
@@ -17,6 +17,6 @@
 ## Testing collab locally
 
 1. Run `foreman start` from the root of the repo.
-1. In another terminal run `script/start-local-collaboration`.
+1. In another terminal run `script/zed-local -2`.
 1. Two copies of Zed will open. Add yourself as a contact in the one that is not you.
 1. Start a collaboration session as normal with any open project.