diff --git a/Doc/library/asyncio-tutorial/case-study-chat-client-gui.rst b/Doc/library/asyncio-tutorial/case-study-chat-client-gui.rst
deleted file mode 100644
index 0f693d7613bcc9..00000000000000
--- a/Doc/library/asyncio-tutorial/case-study-chat-client-gui.rst
+++ /dev/null
@@ -1,20 +0,0 @@
-Asyncio Case Study: Chat Application with GUI client
-====================================================
-
-TODO
-
-Notes:
-
-- server code remains identical to prior case study
-- focus is on making a nice client
-- The focus area here is: can you use asyncio if there is another
-  blocking "loop" in the main thread? (common with GUIs and games)
-  How do you do that?
-- Mention any special considerations
-- Show and discuss strategies for passing data between main thread
-  (GUI) and the asyncio thread (IO).
-- We can demonstrate the above with tkinter, allowing the
-  case study to depend only on the stdlib
-- Towards the end, mention how the design might change if
-  the client was a browser instead of a desktop client.
-  (can refer to the 3rd party websocket library, or aiohttp)
diff --git a/Doc/library/asyncio-tutorial/index.rst b/Doc/library/asyncio-tutorial/index.rst
index 30671bb5a449da..202f2d0294f3dd 100644
--- a/Doc/library/asyncio-tutorial/index.rst
+++ b/Doc/library/asyncio-tutorial/index.rst
@@ -22,4 +22,3 @@ primarily on the "high-level" API, as described in the
    asyncio-cookbook.rst
    case-study-chat-server.rst
    case-study-chat-client-cli.rst
-   case-study-chat-client-gui.rst