diff --git a/content/en/code-of-conduct.md b/content/en/code-of-conduct.md
index c03404e87e..2def9fb08f 100644
--- a/content/en/code-of-conduct.md
+++ b/content/en/code-of-conduct.md
@@ -7,7 +7,7 @@ aliases:
 
 ### Introduction
 
-This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, X, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
 
 This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
 
diff --git a/content/en/community.md b/content/en/community.md
index 3a45d61c74..48208ae67c 100644
--- a/content/en/community.md
+++ b/content/en/community.md
@@ -51,7 +51,7 @@ details and how to get an invite.
 
 If you would like to find a local meetup or study group to learn more about NumPy and the wider ecosystem of Python packages for data science and scientific computing, we recommend exploring the [PyData meetups](https://www.meetup.com/pro/pydata/) (150+ meetups, 100,000+ members).
 
-NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) and [Twitter](https://twitter.com/numpy_team).
+NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion).
 
 
 ## Conferences
diff --git a/content/en/contribute.md b/content/en/contribute.md
index a0968d2266..f5ea653186 100644
--- a/content/en/contribute.md
+++ b/content/en/contribute.md
@@ -92,8 +92,7 @@ issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
 ### Community coordination and outreach
 
 Through community contact we share our work more widely and learn where we're
-falling short. We're eager to get more people involved in efforts like our
-[Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code
+falling short. We're eager to get more people involved in efforts like organizing NumPy [code
 sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
 
 ### Fundraising