diff --git a/docs/deploying.rst b/docs/deploying.rst
index cdfe666..8b72707 100644
--- a/docs/deploying.rst
+++ b/docs/deploying.rst
@@ -144,7 +144,7 @@ and configure routing in front of your interface and WSGI servers to route
 requests appropriately.
 
 If you use Daphne for all traffic, it auto-negotiates between HTTP and WebSocket,
-so there's no need to have your WebSockets on a separate port or path (and
+so there's no need to have your WebSockets on a separate domain or path (and
 they'll be able to share cookies with your normal view code, which isn't
 possible if you separate by domain rather than path).
 
diff --git a/docs/getting-started.rst b/docs/getting-started.rst
index e674f5d..fd63fa4 100644
--- a/docs/getting-started.rst
+++ b/docs/getting-started.rst
@@ -492,7 +492,7 @@ chat to people with the same first letter of their username::
 
 If you're just using ``runserver`` (and so Daphne), you can just connect
 and your cookies should transfer your auth over. If you were running WebSockets
-on a separate port, you'd have to remember to provide the
+on a separate domain, you'd have to remember to provide the
 Django session ID as part of the URL, like this::
 
     socket = new WebSocket("ws://127.0.0.1:9000/?session_key=abcdefg");