docs: replace legacy twitter.com links on policy/terms pages

changelog.mdx

@@ -1461,7 +1461,7 @@ Rules with emojis are now available in the enterprise Search APIs
 
 <Update label="Apr 6, 2017" description="X API: Standard v1.1" >
 ### Wider availability of Direct Message APIs
-Access to several new Direct Message APIs are now more widely available. Read more about this update [on our blog](https://blog.twitter.com/developer/en_us/topics/tools/2017/new-apis-to-power-the-future-of-customer-engagement-in-direct-me.html).  
+Access to several new Direct Message APIs are now more widely available. Read more about this update [on our blog](https://blog.x.com/developer/en_us/topics/tools/2017/new-apis-to-power-the-future-of-customer-engagement-in-direct-me).  
 </Update>
 
 <Update label="Mar 9, 2017" description="X API: Standard v1.1" >

developer-terms/agreement.mdx

@@ -40,7 +40,7 @@ In this Agreement, the following definitions apply:
 3. Modify X Content only to format it for display on your Services; and
 4. Use and display X Marks to attribute X Applications as the source of the X Content, as set forth in this Agreement.
 
-**B. License to X.** You hereby grant X a non-exclusive, royalty free, non-transferable, and non-sublicensable revocable license to access, index, and cache by any means, including web spiders and/or crawlers, any webpage or applications on which you display X Content using [**embedded Posts**](https://developer.x.com/docs/twitter-for-websites/embedded-tweets/overview) or [**embedded timelines**](https://developer.x.com/docs/twitter-for-websites/timelines/overview).
+**B. License to X.** You hereby grant X a non-exclusive, royalty free, non-transferable, and non-sublicensable revocable license to access, index, and cache by any means, including web spiders and/or crawlers, any webpage or applications on which you display X Content using [**embedded Posts**](/x-for-websites/embedded-posts/overview) or [**embedded timelines**](/x-for-websites/timelines/overview).
 
 **C. Incorporated Terms.** Your access to and use of the Licensed Material is also subject to, and you shall comply with, the following additional terms and policies (collectively, “**Incorporated Developer Terms**”):
 

developer-terms/policy.mdx

@@ -36,10 +36,10 @@ Have you taken care to review X’s policies and set up your API access the righ
 
 [**Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules.**](https://help.x.com/rules-and-policies/x-automation) In particular, you should:
 
-- Always get explicit consent before sending people [automated replies or Direct Messages](https://twittercommunity.com/t/policy-clarification-automated-replies-and-mentions/94444)
+- Always get explicit consent before sending people [automated replies or Direct Messages](https://devcommunity.x.com/t/policy-clarification-automated-replies-and-mentions/94444)
 - Immediately respect requests to opt-out of being contacted by you
-- Never perform bulk, aggressive, or spammy actions, including [bulk following](https://twittercommunity.com/t/policy-clarification-aggressive-following-and-inorganic-following-behavior/92769)
-- Never post identical or substantially similar content across [multiple accounts](https://blog.twitter.com/developer/en_us/topics/tips/2018/automation-and-the-use-of-multiple-accounts.html)
+- Never perform bulk, aggressive, or spammy actions, including [bulk following](https://devcommunity.x.com/t/policy-clarification-aggressive-following-and-inorganic-following-behavior/92769)
+- Never post identical or substantially similar content across [multiple accounts](https://blog.x.com/developer/en_us/topics/tips/2018/automation-and-the-use-of-multiple-accounts)
 
 **If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it.** You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio.
 
@@ -58,7 +58,7 @@ Have you taken care to review X’s policies and set up your API access the righ
 
 ## Public display of Posts
 
-**You must maintain the integrity of all X Content that you display publicly or to people who use your service.** If you don’t use [X for Websites](https://developer.x.com/docs/twitter-for-websites/overview) to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law.
+**You must maintain the integrity of all X Content that you display publicly or to people who use your service.** If you don’t use [X for Websites](https://help.x.com/en/x-for-websites-ads-info-and-privacy) to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law.
 
 **There are specific rules you must follow if you display X Content offline.** Follow the [guidelines](https://developer.x.com/developer-terms/display-requirements) for using Posts in broadcast if you display Posts offline.
 
@@ -70,7 +70,7 @@ Have you taken care to review X’s policies and set up your API access the righ
 - **X for Websites widgets**
   - You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s [cookie use](https://help.x.com/rules-and-policies/x-cookies), where providing such information and obtaining such consent is required by law
 - **Services targeted to children under 13**
-  - Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described [here](https://developer.x.com/docs/twitter-for-websites/privacy)
+  - Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described [here](https://x.com/en/privacy)
 
 ## Content redistribution
 

developer-terms/restricted-use-cases.mdx

@@ -12,9 +12,9 @@ The use of X's APIs and developer products to create spam, or engage in spammy b
 
 If your application will be used to perform write actions on the X service, including posting Posts, following accounts, or sending Direct Messages, you should carefully review the [Automation Rules](https://support.x.com/articles/76915) to ensure your service complies with our guidelines. In particular, you should:
 
-- Always get a user’s explicit consent before sending them [automated replies or messages](https://twittercommunity.com/t/policy-clarification-automated-replies-and-mentions/94444)
+- Always get a user’s explicit consent before sending them [automated replies or messages](https://devcommunity.x.com/t/policy-clarification-automated-replies-and-mentions/94444)
 - Immediately respect user requests to opt-out of being contacted by you
-- Never perform bulk, aggressive, or spammy actions, including [bulk following](https://twittercommunity.com/t/policy-clarification-aggressive-following-and-inorganic-following-behavior/92769)
+- Never perform bulk, aggressive, or spammy actions, including [bulk following](https://devcommunity.x.com/t/policy-clarification-aggressive-following-and-inorganic-following-behavior/92769)
 - Never post identical or substantially similar content across [multiple accounts](https://blog.x.com/developer/en_us/topics/tips/2018/automation-and-the-use-of-multiple-accounts.html)
 
 ## Sensitive information
@@ -64,7 +64,7 @@ To the extent you are permitted to distribute X content to a third party, note t
 
 ## Multiple applications
 
-You are not permitted to register multiple applications for a single use case, or substantially similar or overlapping use cases. Learn more about these policies [here](https://twittercommunity.com/t/policy-clarification-multiple-applications-for-the-same-use-case/92080).
+You are not permitted to register multiple applications for a single use case, or substantially similar or overlapping use cases. Learn more about these policies [here](https://devcommunity.x.com/t/policy-clarification-multiple-applications-for-the-same-use-case/92080).
 
 In this context, we define “use case” as a consistent set of analyses, displays, or actions performed via an application. Providing the same service or application to different end users counts as a single use case: however, "white label" versions of a tool or service are not included. If you plan to "white label" versions of your application, you must notify and receive separate approval from us. These rules apply both to applications you register, and to applications registered by the end users of your tool or service; requiring your end users to register applications for the purpose of using your tool or service could result in enforcement actions against you, your applications, your customers, and/or the end users of your tool or service.