Fix redirected external links (#38546)

Author: Josh-Cena

CONTRIBUTING.md

@@ -218,7 +218,7 @@ This will make it easier to submit a pull request for your changes.
 
 To ensure that all MDN documents follow the same formatting, we use both [Prettier](https://www.prettier.io) and [MarkdownLint](https://github.com/DavidAnson/markdownlint) to format and lint Markdown files. This helps us enforce uniform styling across all documents with minimal reviewer intervention.
 
-If you have a [local checkout](#forking-and-cloning-the-repository) of the repository and have [installed the dependencies](#preparing-the-project), or you are using [github.dev](https://github.dev), a pre-commit hook will be installed which automatically runs while making a commit. To save some headache and improve your work flow while authoring, you may wish to [configure your editor to automatically run Prettier](https://prettier.io/docs/en/editors.html). Alternatively, you may run `yarn fix:md` in the command line to manually format all Markdown files.
+If you have a [local checkout](#forking-and-cloning-the-repository) of the repository and have [installed the dependencies](#preparing-the-project), or you are using [github.dev](https://github.dev), a pre-commit hook will be installed which automatically runs while making a commit. To save some headache and improve your work flow while authoring, you may wish to [configure your editor to automatically run Prettier](https://prettier.io/docs/editors.html). Alternatively, you may run `yarn fix:md` in the command line to manually format all Markdown files.
 
 > [!NOTE]
 > Automatically formatting changes does not work for pull requests opened using the GitHub Web UI as described in the ["Simple changes" section](#simple-changes).

files/en-us/games/techniques/3d_on_the_web/building_up_a_basic_demo_with_playcanvas/index.md

@@ -6,7 +6,7 @@ page-type: guide
 
 {{GamesSidebar}}
 
-**PlayCanvas** is a popular 3D WebGL game engine, originally created by Will Eastcott and Dave Evans. It is [open sourced on GitHub](https://github.com/playcanvas/engine), with an [editor](https://developer.playcanvas.com/en/user-manual/designer/) available online and good [documentation](https://developer.playcanvas.com/en/). The online editor is free for public projects with up to two team members, but there are also [paid plans](https://playcanvas.com/plans) if you'd like to run a commercial private project with more developers.
+**PlayCanvas** is a popular 3D WebGL game engine, originally created by Will Eastcott and Dave Evans. It is [open sourced on GitHub](https://github.com/playcanvas/engine), with an [editor](https://developer.playcanvas.com/user-manual/editor/) available online and good [documentation](https://developer.playcanvas.com/en/). The online editor is free for public projects with up to two team members, but there are also [paid plans](https://playcanvas.com/plans) if you'd like to run a commercial private project with more developers.
 
 ![PlayCanvas website.](playcanvas-cover.png)
 

files/en-us/glossary/interaction_to_next_paint/index.md

@@ -24,5 +24,5 @@ The longer the delay, the worse the user experience. The [Long Animation Frames
 - [Long animation frame timing](/en-US/docs/Web/API/Performance_API/Long_animation_frame_timing)
 - [PerformanceEventTiming](/en-US/docs/Web/API/PerformanceEventTiming)
 - [INP](https://web.dev/articles/inp) on web.dev (2023)
-- [Optimizing INP](https://web.dev/articles/optimizing-inp) on web.dev (2023)
+- [Optimize Interaction to Next Paint](https://web.dev/articles/optimize-inp) on web.dev (2023)
 - [Interaction to Next Paint is officially a Core Web Vital](https://web.dev/blog/inp-cwv-launch) on web.dev (2024)

files/en-us/learn_web_development/about/index.md

@@ -79,7 +79,7 @@ The topics presented are covered in differing levels of detail.
 There are also several areas that we explicitly don't cover in this curriculum, namely:
 
 - Exhaustive coverage of back-end languages/platforms. We do provide a brief introduction in [Node.js (Express)](/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs) and [Python (Django)](/en-US/docs/Learn_web_development/Extensions/Server-side/Django) as it is useful to every web developer to understand how HTTP and server-side technologies work. However, we don't provide exhaustive coverage across multiple platforms; that would be out of scope for MDN.
-- In-depth coverage of traditional relational databases (for example, [MySQL](https://dev.mysql.com/doc/) or [Postgres](https://www.postgresql.org/)) and other server-side datastores (for example, cloud databases such as [MongoDB](https://www.mongodb.com/) or [Google Cloud Datastore](https://cloud.google.com/datastore/)). We provide a brief introduction to such technologies in our [Server-side website programming](/en-US/docs/Learn_web_development/Extensions/Server-side) modules.
+- In-depth coverage of traditional relational databases (for example, [MySQL](https://dev.mysql.com/doc/) or [Postgres](https://www.postgresql.org/)) and other server-side datastores (for example, cloud databases such as [MongoDB](https://www.mongodb.com/) or [Google Cloud Datastore](https://cloud.google.com/products/datastore)). We provide a brief introduction to such technologies in our [Server-side website programming](/en-US/docs/Learn_web_development/Extensions/Server-side) modules.
 - Deep-dive DevOps topics such as cloud platforms for provisioning and automation (for example, [Amazon AWS](https://aws.amazon.com/), [Google Cloud Platform](https://console.cloud.google.com/), and [Microsoft Azure](https://azure.microsoft.com/)) and containerization tools (for example, [Kubernetes](https://kubernetes.io/) and [Docker](https://www.docker.com/)). We lightly touch upon some tools that are considered to be in the DevOps space — like GitHub and automated testing tools — but these have distinct crossover into the front-end developer space.
 - Graphic design beyond the basic knowledge outlined in [Design for developers](/en-US/docs/Learn_web_development/Core/Design_for_developers).
 - Skills related to roles such as product and program management (for example, organization, research, and planning).

files/en-us/learn_web_development/core/accessibility/mobile/index.md

@@ -266,7 +266,7 @@ It is also worth considering the use of HTML form input types such as the date o
 - Types `number`, `tel`, and `email` display suitable virtual keyboards for entering numbers/telephone numbers.
 - Types `time` and `date` display suitable pickers for selecting times and dates.
 
-If you want to provide a different solution for desktops, you could always serve different markup to your mobile devices using feature detection. See [input types](https://diveinto.html5doctor.com/detect.html#input-types) for raw information on detecting different input types, and also check out our [feature detection article](/en-US/docs/Learn_web_development/Extensions/Testing/Feature_detection) for much more information.
+If you want to provide a different solution for desktops, you could always serve different markup to your mobile devices using feature detection. Check out our [feature detection article](/en-US/docs/Learn_web_development/Extensions/Testing/Feature_detection) for more information.
 
 ## Summary
 

files/en-us/learn_web_development/core/accessibility/tooling/index.md

@@ -69,7 +69,7 @@ Other auditing tools that are worth checking out:
 
 - [Firefox Accessibility Inspector](https://firefox-source-docs.mozilla.org/devtools-user/accessibility_inspector/index.html)
 - [ANDI bookmarklet](https://www.ssa.gov/accessibility/andi/help/install.html)
-- [Google Lighthouse accessibility audits](https://developer.chrome.com/docs/lighthouse/accessibility/)
+- [Google Lighthouse accessibility audits](https://developer.chrome.com/docs/lighthouse/accessibility/scoring)
 
 > [!NOTE]
 > Such tools aren't good enough to solve all your accessibility problems on their own. You'll need a combination of these, knowledge and experience, user testing, etc. to get a full picture.

files/en-us/learn_web_development/core/design_for_developers/index.md

@@ -78,12 +78,10 @@ Learning outcomes:
 - [Learn UI Design Fundamentals](https://scrimba.com/learn/design?via=mdn), Scrimba <sup>Course Partner</sup>
 - [The Shape of Design](https://shapeofdesignbook.com/chapters/00-introduction/), Frank Chimero
 - [Designing for the Web](https://designingfortheweb.co.uk/), Mark Boulton
-- [Design for web](https://designforweb.org/), Prisca Schmarsow + other contributors. Highlights include:
-  - [Design trampoline: Learn design theory basics](https://designforweb.org/vis/chapter1-design-principles/designTrampoline-by-AnnaRiazhskikh/), Anna Riazhskikh
-  - [Web typography made simple](https://designforweb.org/vis/chapter2-typography/typelab-by-HannahBoom/), Hannah Boom
+- [Design for web](https://designforweb.org/), Prisca Schmarsow + other contributors
 - [Practical Typography](https://practicaltypography.com/), Matthew Butterick
 - [Web Style Guide](https://webstyleguide.com/), Patrick J. Lynch and Sarah Horton
 - [Visual design rules you can safely follow every time](https://anthonyhobday.com/sideprojects/saferules/), Anthony Hobday
-- [16 little UI design rules that make a big impact](https://www.adhamdannaway.com/blog/ui-design/16-ui-design-rules), Adham Dannaway
+- [16 little UI design rules that make a big impact](https://www.adhamdannaway.com/blog/ui-design/ui-design-tips), Adham Dannaway
 
 {{NextMenu("Learn_web_development/Core/Version_control", "Learn_web_development/Core")}}

files/en-us/learn_web_development/core/frameworks_libraries/angular_getting_started/index.md

@@ -72,7 +72,7 @@ To install Angular on your local system, you need the following:
 
   Angular requires a [active LTS or maintenance LTS](https://nodejs.org/en/about/previous-releases) version of Node.js. For information about specific version requirements, see the [Version compatibility](https://angular.dev/reference/versions) page.
 
-  For more information on installing Node.js, see [nodejs.org](https://nodejs.org/en/download/package-manager).
+  For more information on installing Node.js, see [nodejs.org](https://nodejs.org/en/download).
   If you are unsure what version of Node.js runs on your system, run `node -v` in a terminal window.
 
 - **npm package manager**

files/en-us/learn_web_development/core/frameworks_libraries/introduction/index.md

@@ -287,7 +287,7 @@ If you're looking for tools to expedite the web development process, and you kno
 
 **Content-management systems** (**CMSes**) are any tools that allow a user to create content for the web without directly writing code themselves. They're a good solution for large projects, especially projects that require input from content writers who have limited coding ability, or for programmers who want to save time. They do, however, require a significant amount of time to set up, and utilizing a CMS means that you surrender at least some measure of control over the final output of your website. For example: if your chosen CMS doesn't author accessible content by default, it's often difficult to improve this.
 
-A few popular CMS systems include [WordPress](https://wordpress.com/), [Joomla](https://www.joomla.org/), and [Drupal](https://www.drupal.org/).
+A few popular CMS systems include [WordPress](https://wordpress.com/), [Joomla](https://www.joomla.org/), and [Drupal](https://new.drupal.org/).
 
 ### Server-side rendering
 

files/en-us/learn_web_development/core/frameworks_libraries/svelte_deployment_next/index.md

@@ -209,7 +209,7 @@ You can also [import a Svelte git project](https://vercel.com/import/svelte) int
 
 For hosting static files there are several online services that allow you to automatically deploy your site whenever you push changes to a git repository. Most of them involve setting up a deployment pipeline that gets triggered on every `git push`, and takes care of building and deploying your website.
 
-To demonstrate this, we will deploy our todos app to [GitLab Pages](https://docs.gitlab.com/ee/user/project/pages/).
+To demonstrate this, we will deploy our todos app to [GitLab Pages](https://docs.gitlab.com/user/project/pages/).
 
 1. First you'll have to [register at GitLab](https://gitlab.com/users/sign_up) and then [create a new project](https://gitlab.com/projects/new). Give you new project a short, easy name like "mdn-svelte-todo". You will have a remote URL that points to your new GitLab git repository, like `git@gitlab.com:[your-user]/[your-project].git`.
 2. Before you start to upload content to your git repository, it is a good practice to add a `.gitignore` file to tell git which files to exclude from source control. In our case we will tell git to exclude files in the `node_modules` directory by creating a `.gitignore` file in the root folder of your local project, with the following content:
@@ -230,7 +230,7 @@ To demonstrate this, we will deploy our todos app to [GitLab Pages](https://docs
    ```
 
    > [!NOTE]
-   > You could use [the `git` protocol](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#_the_git_protocol) instead of `https`, which is faster and saves you from typing your username and password every time you access your origin repo. To use it you'll have to [create an SSH key pair](https://docs.gitlab.com/ee/user/ssh.html#generate-an-ssh-key-pair). Your origin URL will be like this: `[email protected]:[your-user]/mdn-svelte-todo.git`.
+   > You could use [the `git` protocol](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#_the_git_protocol) instead of `https`, which is faster and saves you from typing your username and password every time you access your origin repo. To use it you'll have to [create an SSH key pair](https://docs.gitlab.com/user/ssh/#generate-an-ssh-key-pair). Your origin URL will be like this: `[email protected]:[your-user]/mdn-svelte-todo.git`.
 
 With these instructions we initialize a local git repository, then set our remote origin (where we will push our code to) as our repo on GitLab. Next we commit all the files to the local git repo, and then push those to the remote origin on GitLab.
 

files/en-us/learn_web_development/core/frameworks_libraries/svelte_typescript/index.md

@@ -71,7 +71,7 @@ Remember to run `npm install && npm run dev` to start your app in development mo
 
 ### REPL
 
-Unfortunately, [TypeScript support is not yet available in the REPL](https://github.com/sveltejs/sites/issues/156).
+Unfortunately, [TypeScript support is not yet available in the REPL](https://github.com/sveltejs/svelte.dev/issues/853).
 
 ## TypeScript: optional static typing for JavaScript
 

files/en-us/learn_web_development/core/frameworks_libraries/vue_first_component/index.md

@@ -33,7 +33,7 @@ Now it's time to dive deeper into Vue, and create our own custom component — w
           more advanced features of Vue (like Single File Components or render
           functions), you'll need a terminal with
           <a
-            href="https://nodejs.org/en/download/package-manager"
+            href="https://nodejs.org/en/download"
             rel="noopener noreferrer"
             target="_blank"
             >Node</a

files/en-us/learn_web_development/core/scripting/what_is_javascript/index.md

@@ -119,7 +119,7 @@ They generally fall into two categories.
 
 **Third party APIs** are not built into the browser by default, and you generally have to grab their code and information from somewhere on the Web. For example:
 
-- The [Twitter API](https://developer.x.com/en/docs) allows you to do things like displaying your latest tweets on your website.
+- The [Bluesky API](https://docs.bsky.app/) allows you to do things like displaying your latest posts on your website.
 - The [Google Maps API](https://developers.google.com/maps/) and [OpenStreetMap API](https://wiki.openstreetmap.org/wiki/API) allows you to embed custom maps into your website, and other such functionality.
 
 > [!NOTE]

files/en-us/learn_web_development/core/styling_basics/tables_tasks/index.md

@@ -180,4 +180,4 @@ table {
 ## See also
 
 - [CSS styling basics](/en-US/docs/Learn_web_development/Core/Styling_basics)
-- [Web Typography: Designing Tables to be Read, Not Looked At](https://alistapart.com/article/web-typography-tables) on alistapart.com (2017)
+- [Web Typography: Designing Tables to be Read, Not Looked At](https://alistapart.com/article/web-typography-tables/) on alistapart.com (2017)

files/en-us/learn_web_development/extensions/client-side_tools/introducing_complete_toolchain/index.md

@@ -162,15 +162,15 @@ npm install --save-dev prettier
 
 Note again that we are using `--save-dev` to add it as a dev dependency, because we only use it during development.
 
-Like many tools made more recently Prettier comes with "sensible defaults". That means that you'll be able to use Prettier without having to configure anything (if you are happy with the [defaults](https://prettier.io/docs/en/configuration.html)). This lets you get on with what's important: the creative work. For demonstration, we'll add a config file. Create a file in the root of your `npm-experiment` directory called `.prettierrc.json`. Add the following contents:
+Like many tools made more recently Prettier comes with "sensible defaults". That means that you'll be able to use Prettier without having to configure anything (if you are happy with the [defaults](https://prettier.io/docs/configuration.html)). This lets you get on with what's important: the creative work. For demonstration, we'll add a config file. Create a file in the root of your `npm-experiment` directory called `.prettierrc.json`. Add the following contents:
 
 ```json
 {
   "bracketSameLine": true
 }
 ```
 
-With this setting, Prettier will print the `>` of a multi-line HTML (HTML, JSX, Vue, Angular) opening tag at the end of the last line instead of being alone on the next line. This is the format the MDN itself uses. You can find more about [configuring Prettier](https://prettier.io/docs/en/configuration.html) in its documentation.
+With this setting, Prettier will print the `>` of a multi-line HTML (HTML, JSX, Vue, Angular) opening tag at the end of the last line instead of being alone on the next line. This is the format the MDN itself uses. You can find more about [configuring Prettier](https://prettier.io/docs/configuration.html) in its documentation.
 
 By default, Prettier formats all files that you specify. However, again, we don't need to format generated files, or there may be certain legacy code that we don't want to touch. We can tell Prettier to always ignore these files by creating a `.prettierignore` file in the root of the project directory. Add the following contents to the file:
 

files/en-us/learn_web_development/extensions/forms/form_validation/index.md

@@ -699,7 +699,7 @@ To validate a form, ask yourself a few questions:
     You should offer up-front suggestions so they know what's expected, as well as clear error messages.
     If you want to dig into form validation UI requirements, here are some useful articles you should read:
 
-    - [Help users enter the right data in forms](https://web.dev/Learn_web_development/Extensions/Forms/validation/)
+    - [Help users enter the right data in forms](https://web.dev/learn/forms/form-fields)
     - [Validating input](https://www.w3.org/WAI/tutorials/forms/validation/)
     - [How to Report Errors in Forms: 10 Design Guidelines](https://www.nngroup.com/articles/errors-forms-design-guidelines/)