diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md
index 5b1be1e9..2055f93e 100644
--- a/content/client-server-api/_index.md
+++ b/content/client-server-api/_index.md
@@ -1877,10 +1877,6 @@ forming a sort of chain of events.
 This specification describes the following relationship types:
 
 * [Rich replies](#rich-replies)
-<!--
-TODO: TR,MSC3440: Uncomment for threading support.
-* [Event threading](#threading)
--->
 
 {{% boxes/note %}}
 This specification does not currently define any relation type which requires
diff --git a/content/client-server-api/modules/rich_replies.md b/content/client-server-api/modules/rich_replies.md
index 78408e78..99c5969d 100644
--- a/content/client-server-api/modules/rich_replies.md
+++ b/content/client-server-api/modules/rich_replies.md
@@ -51,14 +51,6 @@ An example reply would be:
 Note that the `event_id` of the `m.in_reply_to` object has the same requirements
 as if it were to be under `m.relates_to` directly instead.
 
-<!--
-TODO: TR, MSC3440: Uncomment for threads support
-{{% boxes/note %}}
-Some event relationships, like [threads](#threading), describe what it looks like
-to both form a relationship *and* still reply to another event.
-{{% /boxes/note %}}
--->
-
 #### Fallbacks for rich replies
 
 Some clients may not have support for rich replies and therefore need a