Update internal links and URL fragments in other docs

Author: krzysdz

src/content/blog/2025-03-31-v5-1-latest-release.md

@@ -28,7 +28,7 @@ We know that migrating between versions can be challenging, especially when it i
 
 Thanks to the incredible efforts of [Sebastian](https://github.com/bjohansebas) and [Filip](https://github.com/kjugi), we have developed a new [codemod package](https://www.npmjs.com/package/@expressjs/codemod) specifically designed to facilitate the transition from Express v4 to v5, as well as future major versions. This package automates many of the necessary code changes, minimizing manual effort and making the upgrade as smooth and efficient as possible.
 
-However, we understand that not all changes can be automated. Some breaking changes, such as the [new Path Route Matching syntax](/en/guide/migrating-5#path-syntax), require manual modifications by developers. You can read more about all of the breaking changes which came with v5 in our [original release announcement](/en/blog/2024-10-15-v5-release).
+However, we understand that not all changes can be automated. Some breaking changes, such as the [new Path Route Matching syntax](/en/guide/migrating-5#path-route-matching-syntax), require manual modifications by developers. You can read more about all of the breaking changes which came with v5 in our [original release announcement](/en/blog/2024-10-15-v5-release).
 
 For more details on the migration process and how to use the codemod package, check the [repository’s README](https://github.com/expressjs/codemod#readme) and the [migration guide](/en/guide/migrating-5).
 
@@ -115,9 +115,9 @@ starts the clock on EOL for v4 by moving it to `MAINTENANCE`. We recognize that
 only major version for most of the history of Node.js itself. Because of this, we want to remain flexible and also
 provide a bit longer support. We want to do what is best for the ecosystem, so consider these goals not commitments.
 
-\*: v4 is a special case, and we may extend MAINTENENCE support  
+\*: v4 is a special case, and we may extend MAINTENENCE support
 \*\*: v5 MAINTENENCE and EOL dates are determined by when v6 is released, these dates reflect the earliest dates if we
-were to ship v6 on 2025-10-01  
+were to ship v6 on 2025-10-01
 \*\*\* : v6 work has not officially started yet, this is simply the earliest date we can ship based on our proposed policy
 
 ---

src/content/blog/2025-06-05-vulnerability-reporting-process-overhaul.md

@@ -38,7 +38,7 @@ Security Advisories are now enabled across all Express.js repositories, allowing
 
 Expectations around ownership and response timelines have been clarified and published to reduce ambiguity and improve responsiveness.
 
-> A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team) or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md) will acknowledge your report as soon as possible.
+> A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage) or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md) will acknowledge your report as soon as possible.
 >
 > After the initial reply to your report, the security team will
 > endeavor to keep you informed of the progress towards a fix and full

src/content/blog/2026-05-18-a-new-look-for-express.mdx

@@ -77,7 +77,7 @@ The effort was led by [Sebastian Beltran](https://github.com/bjohansebas), with
 
 A huge thank you goes to the [Orama](https://orama.com) team for sponsoring [Francesca Giannino](https://github.com/g-francesca), [Angela Angelini](https://www.linkedin.com/in/angeliningl/), [Michele Riva](https://github.com/micheleriva), and [Davide Spaziani](https://www.linkedin.com/in/davidespazianitesta/), and for the design, feedback, and support they brought to every stage of the project.
 
-From the Express side, the redesign was shaped by many hands: [Ulises Gascón](https://github.com/ulisesgascon), [Rand McKinney](https://github.com/crandmck), [Jon Church](https://github.com/jonchurch), [Shubham Oulkar](https://github.com/ShubhamOulkar), the rest of the [Express Technical Committee](https://github.com/expressjs/express#technical-committee), and everyone who contributed reviews, issues, or comments along the way. The full history, including every PR that made it into the redesign, lives in [the main pull request](https://github.com/expressjs/expressjs.com/pull/2169).
+From the Express side, the redesign was shaped by many hands: [Ulises Gascón](https://github.com/ulisesgascon), [Rand McKinney](https://github.com/crandmck), [Jon Church](https://github.com/jonchurch), [Shubham Oulkar](https://github.com/ShubhamOulkar), the rest of the [Express Technical Committee](https://github.com/expressjs/express#tc-technical-committee), and everyone who contributed reviews, issues, or comments along the way. The full history, including every PR that made it into the redesign, lives in [the main pull request](https://github.com/expressjs/expressjs.com/pull/2169).
 
 More than a year of work went into this launch. In open source, progress is rarely fast: decisions take discussion, design takes iteration, and reviews take time. But step by step, a community can build something it's proud of, and this is one of those steps.
 

src/content/docs/en/4x/guide/behind-proxies.mdx

@@ -86,16 +86,17 @@ Enabling `trust proxy` will have the following impact:
 
 <ul>
   <li markdown="1">
-    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    The value of [req.hostname](../../api/request/#reqhostname) is derived from the value set in the
     `X-Forwarded-Host` header, which can be set by the client or by the proxy.
   </li>
   <li markdown="1">
     `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
-    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+    `http` or even an invalid name. This value is reflected by
+    [req.protocol](../../api/request/#reqprotocol).
   </li>
   <li markdown="1">
-    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
-    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+    The [req.ip](/en/api#req.ip) and [req.ips](../../api/request/#reqips) values are populated based
+    on the socket address and `X-Forwarded-For` header, starting at the first untrusted address.
   </li>
 </ul>
 

src/content/docs/en/4x/guide/debugging.mdx

@@ -18,7 +18,7 @@ On Windows, use the corresponding command.
 > $env:DEBUG = "express:*"; node index.js
 ```
 
-Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+Running this command on the default app generated by the [express generator](../../starter/generator) prints the following output:
 
 ```bash
 $ DEBUG=express:* node ./bin/www

src/content/docs/en/4x/guide/error-handling.mdx

@@ -190,7 +190,7 @@ function errorHandler(err, req, res, next) {
 Note that the default error handler can get triggered if you call `next()` with an error
 in your code more than once, even if custom error handling middleware is in place.
 
-Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+Other error handling middleware can be found at [Express middleware](../../../resources/middleware).
 
 ## Writing error handlers
 

src/content/docs/en/4x/guide/overriding-express-api.md

@@ -14,7 +14,7 @@ Altering the global prototypes will affect all loaded Express apps in the same p
 
 You can override the signature and behavior of existing methods with your own, by assigning a custom function.
 
-Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+Following is an example of overriding the behavior of [res.sendStatus](../../api/response/#ressendstatusstatuscode).
 
 ```js
 app.response.sendStatus = function (statusCode, type, message) {

src/content/docs/en/4x/guide/routing.mdx

@@ -6,12 +6,12 @@ description: Learn how to define and use routes in Express.js applications, incl
 import Alert from '@components/primitives/Alert/Alert.astro';
 
 _Routing_ refers to how an application's endpoints (URIs) respond to client requests.
-For an introduction to routing, see [Basic routing](/en/4x/starter/basic-routing).
+For an introduction to routing, see [Basic routing](../../starter/basic-routing).
 
 You define routing using methods of the Express `app` object that correspond to HTTP methods;
 for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/en/4x/api/application#appmethodpath-callback--callback-). You can also use [app.all()](/en/4x/api/application#appallpath-callback--callback-) to handle all HTTP methods and [app.use()](/en/4x/api/application#appusepath-callback--callback) to
-specify middleware as the callback function (See [Using middleware](/en/4x/guide/using-middleware) for details).
+see [app.METHOD](../../api/application#appmethodpath-callback--callback-). You can also use [app.all()](../../api/application#appallpath-callback--callback-) to handle all HTTP methods and [app.use()](../../api/application#appusepath-callback--callback) to
+specify middleware as the callback function (See [Using middleware](../using-middleware) for details).
 
 These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
 
@@ -50,7 +50,7 @@ app.post('/', (req, res) => {
 ```
 
 Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/en/4x/api/application#appmethodpath-callback--callback-).
+For a full list, see [app.METHOD](../../api/application#appmethodpath-callback--callback-).
 
 There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
 
@@ -212,12 +212,12 @@ characters with an additional backslash, for example `\\d+`.
 </Alert>
 
 <Alert type="warning">
-The <a href="https://github.com/expressjs/express/issues/2495">`*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`.
+The [`*`](https://github.com/expressjs/express/issues/2495) character in regular expressions is not interpreted in the usual way. As a workaround, use `{0,}` instead of `*`.
 </Alert>
 
 ## Route handlers
 
-You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+You can provide multiple callback functions that behave like [middleware](../using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
 
 ```js
 app.get('/user/:id', (req, res, next) => {
@@ -312,22 +312,22 @@ app.get(
 
 The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
 
-| Method                                                                       | Description                                                                           |
-| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
-| [res.download()](/en/4x/api/response#resdownloadpath--filename--options--fn) | Prompt a file to be downloaded.                                                       |
-| [res.end()](/en/4x/api/response#resenddata-encoding-callback)                | End the response process.                                                             |
-| [res.json()](/en/4x/api/response#resjsonbody)                                | Send a JSON response.                                                                 |
-| [res.jsonp()](/en/4x/api/response#resjsonpbody)                              | Send a JSON response with JSONP support.                                              |
-| [res.redirect()](/en/4x/api/response#resredirectstatus-path)                 | Redirect a request.                                                                   |
-| [res.render()](/en/4x/api/response#resrenderview--locals--callback)          | Render a view template.                                                               |
-| [res.send()](/en/4x/api/response#ressendbody)                                | Send a response of various types.                                                     |
-| [res.sendFile()](/en/4x/api/response#ressendfilepath--options--fn)           | Send a file as an octet stream.                                                       |
-| [res.sendStatus()](/en/4x/api/response#ressendstatusstatuscode)              | Set the response status code and send its string representation as the response body. |
+| Method                                                                      | Description                                                                           |
+| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](../../api/response#resdownloadpath--filename--options--fn) | Prompt a file to be downloaded.                                                       |
+| [res.end()](../../api/response#resenddata-encoding-callback)                | End the response process.                                                             |
+| [res.json()](../../api/response#resjsonbody)                                | Send a JSON response.                                                                 |
+| [res.jsonp()](../../api/response#resjsonpbody)                              | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](../../api/response#resredirectstatus-path)                 | Redirect a request.                                                                   |
+| [res.render()](../../api/response#resrenderview--locals--callback)          | Render a view template.                                                               |
+| [res.send()](../../api/response#ressendbody)                                | Send a response of various types.                                                     |
+| [res.sendFile()](../../api/response#ressendfilepath--options--fn)           | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](../../api/response#ressendstatusstatuscode)              | Set the response status code and send its string representation as the response body. |
 
 ## app.route()
 
 You can create chainable route handlers for a route path by using `app.route()`.
-Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/4x/api/router).
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](../../api/router).
 
 Here is an example of chained route handlers that are defined by using `app.route()`.
 
@@ -388,7 +388,7 @@ app.use('/birds', birds);
 
 The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
 
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/4x/api/application#appusepath-callback--callback).
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](../../api/application#appusepath-callback--callback).
 
 ```js
 const router = express.Router({ mergeParams: true });