From 43a48314acf3a9c66124cb499fbc540ff5906d34 Mon Sep 17 00:00:00 2001
From: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
Date: Wed, 5 Oct 2022 10:54:58 +0100
Subject: [PATCH] Remove reference to a `room_id` key for typing events (#1265)

---
 changelogs/client_server/newsfragments/1265.clarification | 1 +
 content/client-server-api/modules/typing_notifications.md | 5 +++--
 2 files changed, 4 insertions(+), 2 deletions(-)
 create mode 100644 changelogs/client_server/newsfragments/1265.clarification

diff --git a/changelogs/client_server/newsfragments/1265.clarification b/changelogs/client_server/newsfragments/1265.clarification
new file mode 100644
index 00000000..ca5f3aea
--- /dev/null
+++ b/changelogs/client_server/newsfragments/1265.clarification
@@ -0,0 +1 @@
+Fix various typos throughout the specification.
\ No newline at end of file
diff --git a/content/client-server-api/modules/typing_notifications.md b/content/client-server-api/modules/typing_notifications.md
index 722c011f..b3ce2372 100644
--- a/content/client-server-api/modules/typing_notifications.md
+++ b/content/client-server-api/modules/typing_notifications.md
@@ -6,8 +6,9 @@ type: module
 
 Users may wish to be informed when another user is typing in a room.
 This can be achieved using typing notifications. These are ephemeral
-events scoped to a `room_id`. This means they do not form part of the
-[Event Graph](index.html#event-graphs) but still have a `room_id` key.
+events, so they do not form part of the
+[Event Graph](index.html#event-graphs). Typing notifications are scoped
+to a room.
 
 #### Events