docs: update Twitter references to X (formerly Twitter)

[shivamk-29]

Why:

Closes: N/A

Twitter has rebranded to X. Updating these references to "X (formerly Twitter)" ensures that the user-facing documentation remains current, accurate, and easy to understand for global users.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Updated 4 documentation markdown files to replace outdated text references of "Twitter" with "X (formerly Twitter)". Additionally, updated a legacy example profile URL from https://twitter.com/github to https://x.com/github in the profile personalization guide to prevent documentation link rot.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

---

🌱 First-Time Contributor Note:

I wanted to share that I actually noticed this outdated reference while going through the process of changing my own GitHub username! The documentation advised updating other social profiles like LinkedIn and Twitter, which made me realize the text was out of date. Since this is my very first open-source commit, I utilized AI to help me safely navigate the Git workflow, filter out underlying system/API files, and ensure I was only touching documentation prose. Excited to submit my first contribution here!

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
account-and-profile/concepts/username-changes.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17
account-and-profile/tutorials/personalize-your-profile.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17
organizations/managing-organization-settings/renaming-an-organization.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@shivamk-29 Checking to see how much we feel the need to update this and make sure it's consistent across the docs.

[Sharra-writes]

@shivamk-29 No one cares enough to ensure it's completely consistent everywhere, so yeah, we'll take this.

[Copilot]

Pull request overview

Updates user-facing references after Twitter’s rebranding.

Changes:

• Renames Twitter references to “X (formerly Twitter).”
• Updates the example profile URL to https://x.com/github.

Show a summary per file

File	Description
content/site-policy/privacy-policies/github-general-privacy-statement.md	Updates the third-party service name.
content/organizations/managing-organization-settings/renaming-an-organization.md	Updates the social profile example.
content/account-and-profile/tutorials/personalize-your-profile.md	Updates the account name and profile URL.
content/account-and-profile/concepts/username-changes.md	Updates the social profile example.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Medium

[Sharra-writes]

@shivamk-29 Okay, actually, I didn't realize one of those changes was to a site policy article. We can't change those, they aren't owned by the docs team and have to be reviewed by our legal department before any changes can be made. I tried changing it back, but the PR already requires a review from them, so I'm going to have to close it. If you want to open a new one where you don't change anything in site policy, I will happily accept that.

[jessephus]

I can approve it with the Privacy Policy update pulled out.