From e284d20866bc86c7c7c2758d3ac39fb13f7d463e Mon Sep 17 00:00:00 2001
From: Kim Brose <2803622+HarHarLinks@users.noreply.github.com>
Date: Fri, 19 Dec 2025 23:11:30 +0100
Subject: [PATCH] Remove unintended TeX formatting

---
 changelogs/client_server/newsfragments/2283.clarification | 1 +
 content/client-server-api/modules/instant_messaging.md    | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 changelogs/client_server/newsfragments/2283.clarification

diff --git a/changelogs/client_server/newsfragments/2283.clarification b/changelogs/client_server/newsfragments/2283.clarification
new file mode 100644
index 00000000..2dc18986
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2283.clarification
@@ -0,0 +1 @@
+Remove unintended TeX formatting. Contributed by @HarHarLinks.
diff --git a/content/client-server-api/modules/instant_messaging.md b/content/client-server-api/modules/instant_messaging.md
index d5c0cb6a..5c8a802c 100644
--- a/content/client-server-api/modules/instant_messaging.md
+++ b/content/client-server-api/modules/instant_messaging.md
@@ -119,7 +119,7 @@ Clients SHOULD verify the structure of incoming events to ensure that
 the expected keys exist and that they are of the right type. Clients can
 discard malformed events or display a placeholder message to the user.
 Redacted `m.room.message` events MUST be removed from the client. This
-can either be replaced with placeholder text (e.g. "\[REDACTED\]") or
+can either be replaced with placeholder text (e.g. "[REDACTED]") or
 the redacted message can be removed entirely from the messages view.
 
 Events which have attachments (e.g. `m.image`, `m.file`) SHOULD be