diff --git a/docs/_link_checker_sc/ignore_errors.json b/docs/_link_checker_sc/ignore_errors.json
index 64705a503d..1dac6b56b0 100644
--- a/docs/_link_checker_sc/ignore_errors.json
+++ b/docs/_link_checker_sc/ignore_errors.json
@@ -1010,5 +1010,142 @@
       "text": "PX4 v1.13 Docs"
     },
     "hideReason": "intended"
+  },
+  {
+    "link": {
+      "url": "https://logs.px4.io/",
+      "text": ""
+    },
+    "hideReason": "405 Method Not Allowed - works in browser"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/development-tools/stsw-stm32080.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.molex.com/en-us/products/part-detail/5024430670", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/development-tools/stlink-v3minie.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/development-tools/stsw-link004.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/mems-and-sensors/iis2mdc.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/positioning/teseo-liv4f.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/development-tools/st-link-v2.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32f0-series.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32h743ii.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32f745vg.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32f765ii.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers/stm32f405rg.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32h750vb.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://review.px4.io/plot_app?log=6a1a279c-1df8-4736-9f55-70ec16656d1e", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.skypull.technology/", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.st.com/en/microcontrollers-microprocessors/stm32-32-bit-arm-cortex-mcus.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.te.com/usa-en/product-CAT-BLPS0003.html", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Flight_Dynamics_Model", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Howto:Install_Flightgear_from_a_PPA", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Command_line_options", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Suggested_airports", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Howto:Multiplayer", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://wiki.flightgear.org/Property_tree", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.nxp.com/", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
+  },
+  {
+    "link": { "url": "https://www.hovergames.com/", "text": "" },
+    "hideReason": "timeout - bot block",
+    "expiry": "2026-08-26"
   }
-]
+]
\ No newline at end of file
diff --git a/docs/en/advanced_features/satcom_roadblock.md b/docs/en/advanced_features/satcom_roadblock.md
index 7a6a21a1e4..14da742b57 100644
--- a/docs/en/advanced_features/satcom_roadblock.md
+++ b/docs/en/advanced_features/satcom_roadblock.md
@@ -9,7 +9,7 @@ Given good signal quality, users can expect a latency between 10 to 15 seconds.
 
 The following components are needed for the satellite communication link:
 
-- A [RockBlock 9603 Iridium Satellite Modem](https://www.iridium.com/products/ground-control-rockblock-9603/) module connected to a Pixhawk flashed with the PX4 Autopilot.
+- A [RockBlock 9603 Iridium Satellite Modem](https://www.iridium.com/products/rockblock-9603) module connected to a Pixhawk flashed with the PX4 Autopilot.
 - A message relay server running Ubuntu Linux.
 - A ground station computer running _QGroundControl_ on Ubuntu Linux
 
@@ -55,15 +55,15 @@ The default baud rate of the module is 19200. However, the PX4 _iridiumsbd_ driv
 
 1. Connect to the module with using a 19200/8-N-1 setting and check if the communication is working using the command: `AT`.
    The response should be: `OK`.
-1. Change the baud rate:
+2. Change the baud rate:
 
-   ```
+   ```sh
    AT+IPR=9
    ```
 
-1. Reconnect to the model now with a 115200/8-N-1 setting and save the configuration using:
+3. Reconnect to the model now with a 115200/8-N-1 setting and save the configuration using:
 
-   ```
+   ```sh
    AT&W0
    ```
 
@@ -77,7 +77,7 @@ There is no need to set the baud rate for the port, as this is configured by the
 ::: info
 If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware):
 
-```
+```txt
 drivers/telemetry/iridiumsbd
 ```
 
@@ -103,38 +103,38 @@ The relay server should be run on either Ubuntu 16.04 or 14.04 OS.
    - `5672` for the _RabbitMQ_ message broker (can be changed in the _rabbitmq_ settings)
    - `45679` for the HTTP POST interface (can be changed in the **relay.cfg** file)
 
-1. Install the required python modules:
+2. Install the required python modules:
 
    ```sh
    sudo pip install pika tornado future
    ```
 
-1. Install the `rabbitmq` message broker:
+3. Install the `rabbitmq` message broker:
 
    ```sh
    sudo apt install rabbitmq-server
    ```
 
-1. Configure the broker's credentials (change PWD to your preferred password):
+4. Configure the broker's credentials (change PWD to your preferred password):
 
    ```sh
    sudo rabbitmqctl add_user iridiumsbd PWD
    sudo rabbitmqctl set_permissions iridiumsbd ".*" ".*" ".*"
    ```
 
-1. Clone the [SatComInfrastructure](https://github.com/acfloria/SatComInfrastructure) repository:
+5. Clone the [SatComInfrastructure](https://github.com/acfloria/SatComInfrastructure) repository:
 
    ```sh
    git clone https://github.com/acfloria/SatComInfrastructure.git
    ```
 
-1. Go to the location of the _SatComInfrastructure_ repo and configure the broker's queues:
+6. Go to the location of the _SatComInfrastructure_ repo and configure the broker's queues:
 
    ```sh
    ./setup_rabbit.py localhost iridiumsbd PWD
    ```
 
-1. Verify the setup:
+7. Verify the setup:
 
    ```sh
    sudo rabbitmqctl list_queues
@@ -142,8 +142,8 @@ The relay server should be run on either Ubuntu 16.04 or 14.04 OS.
 
    This should give you a list of 4 queues: `MO`, `MO_LOG`, `MT`, `MT_LOG`
 
-1. Edit the `relay.cfg` configuration file to reflect your settings.
-1. Start the relay script in the detached mode:
+8. Edit the `relay.cfg` configuration file to reflect your settings.
+9. Start the relay script in the detached mode:
 
    ```sh
    screen -dm bash -c 'cd SatcomInfrastructure/; ./relay.py
@@ -216,15 +216,15 @@ If in the terminal where the `udp2rabbit.py` script is running within a couple o
 
    ![Connect the High Latency link](../../assets/satcom/linkconnect.png)
 
-1. Open a terminal on the ground station computer and change to the location of the _SatComInfrastructure_ repository.
+2. Open a terminal on the ground station computer and change to the location of the _SatComInfrastructure_ repository.
    Then start the **udp2rabbit.py** script:
 
    ```sh
    ./udp2rabbit.py
    ```
 
-1. Power up the vehicle.
-1. Wait until the first `HIGH_LATENCY2` message is received on QGC.
+3. Power up the vehicle.
+4. Wait until the first `HIGH_LATENCY2` message is received on QGC.
    This can be checked either using the _MAVLink Inspector_ widget or on the toolbar with the _LinkIndicator_.
    If more than one link is connected to the active vehicle the _LinkIndicator_ shows all of them by clicking on the name of the shown link:
 
@@ -232,7 +232,7 @@ If in the terminal where the `udp2rabbit.py` script is running within a couple o
 
    The link indicator always shows the name of the priority link.
 
-1. The satellite communication system is now ready to use.
+5. The satellite communication system is now ready to use.
    The priority link, which is the link over which commands are send, is determined the following ways:
    - If no link is commanded by the user a regular radio telemetry link is preferred over the high latency link.
    - The autopilot and QGC will fall back from the regular radio telemetry to the high latency link if the vehicle is armed and the radio telemetry link is lost (no MAVLink messages received for a certain time).
diff --git a/docs/en/assembly/quick_start_pixhawk5x.md b/docs/en/assembly/quick_start_pixhawk5x.md
index 10db57bbf5..3516206416 100644
--- a/docs/en/assembly/quick_start_pixhawk5x.md
+++ b/docs/en/assembly/quick_start_pixhawk5x.md
@@ -52,7 +52,7 @@ You can press the safety switch again to enable safety and disarm the vehicle (t
 ## Power
 
 Connect the output of the _PM02D Power Module_ (PM board) that comes with the Standard Set to one of the **POWER** port of _Pixhawk 5X_ using the 6-wire cable.
-The PM02D and Power ports on the Pixhawk 5X uses the 6 circuit [2.00mm Pitch CLIK-Mate Wire-to-Board PCB Receptacle](https://www.molex.com/en-us/products/part-detail/5024430670) & [Housing](https://www.molex.com/molex/products/part-detail/crimp_housings/5024390600).
+The PM02D and Power ports on the Pixhawk 5X uses the 6 circuit [2.00mm Pitch CLIK-Mate Wire-to-Board PCB Receptacle](https://www.molex.com/en-us/products/part-detail/5024430670) & [Housing](https://www.molex.com/en-us/products/part-detail/5024390600).
 
 The PM02D Power Module supports **2~6S** battery, the board input should be connected to your LiPo battery. Note that the PM board does not supply power to the + and - pins of **FMU PWM OUT** and **I/O PWM OUT**.
 
diff --git a/docs/en/assembly/quick_start_pixhawk6x.md b/docs/en/assembly/quick_start_pixhawk6x.md
index b7f35adb96..ed8f6ccc01 100644
--- a/docs/en/assembly/quick_start_pixhawk6x.md
+++ b/docs/en/assembly/quick_start_pixhawk6x.md
@@ -65,7 +65,7 @@ You can press the safety switch again to enable safety and disarm the vehicle (t
 ## Power
 
 Connect the output of the _PM02D Power Module_ (PM board) that comes with the Standard Set to one of the **POWER** port of _Pixhawk 6X_ using the 6-wire cable.
-The PM02D and Power ports on the Pixhawk 6X uses the 6 circuit [2.00mm Pitch CLIK-Mate Wire-to-Board PCB Receptacle](https://www.molex.com/en-us/products/part-detail/5024430670) & [Housing](https://www.molex.com/molex/products/part-detail/crimp_housings/5024390600).
+The PM02D and Power ports on the Pixhawk 6X uses the 6 circuit [2.00mm Pitch CLIK-Mate Wire-to-Board PCB Receptacle](https://www.molex.com/en-us/products/part-detail/5024430670) & [Housing](https://www.molex.com/en-us/products/part-detail/5024390600).
 
 The PM02D Power Module supports **2~6S** battery, the board input should be connected to your LiPo battery. Note that the PM board does not supply power to the + and - pins of **FMU PWM OUT** and **I/O PWM OUT**.
 
diff --git a/docs/en/camera/camera_intel_realsense_t265_vio.md b/docs/en/camera/camera_intel_realsense_t265_vio.md
index 1fdb99e9ab..795ba5c2b4 100644
--- a/docs/en/camera/camera_intel_realsense_t265_vio.md
+++ b/docs/en/camera/camera_intel_realsense_t265_vio.md
@@ -18,17 +18,20 @@ No longer available.
 
 At a high level:
 
-- The [`realsense-ros` wrapper](https://github.com/IntelRealSense/realsense-ros) provided by Intel should be used to extract the raw data from the camera.
+- The [`realsense-ros` wrapper](https://github.com/realsenseai/realsense-ros) provided by Intel should be used to extract the raw data from the camera.
 - The camera should be mounted with lenses facing down (default).
   Be sure to specify the camera orientation by publishing the static transform between the `base_link` and `camera_pose_frame` in a ROS launch file, for example:
+
   ```xml
   <node pkg="tf" type="static_transform_publisher" name="tf_baseLink_cameraPose"
       args="0 0 0 0 1.5708 0 base_link camera_pose_frame 1000"/>
   ```
+
   This is a static transform that links the camera ROS frame `camera_pose_frame` to the MAVROS drone frame `base_link`.
   - the first three `args` specify _translation_ x,y,z in metres from the center of the flight controller to the camera.
     For example, if the camera is 10cm in front of the controller and 4cm up, the first three numbers would be : [0.1, 0, 0.04,...]
   - the next three `args` specify rotation in radians (yaw, pitch, roll).
     So `[... 0, 1.5708, 0]` means pitch down by 90° (facing the ground). Facing straight forward would be [... 0 0 0].
+
 - The camera is sensitive to high-frequency vibrations!
   It should be soft-mounted with, for example, vibration isolation foam.
diff --git a/docs/en/companion_computer/companion_computer_peripherals.md b/docs/en/companion_computer/companion_computer_peripherals.md
index 481603109a..d08e4fecfd 100644
--- a/docs/en/companion_computer/companion_computer_peripherals.md
+++ b/docs/en/companion_computer/companion_computer_peripherals.md
@@ -54,8 +54,8 @@ They are in no way guaranteed to be plug and play with your companion computer.
 
 Popular stereo cameras include:
 
-- [Intel® RealSense™ Depth Camera D435](https://realsenseai.com/stereo-depth-cameras/stereo-depth-camera-d435/)
-- [Intel® RealSense™ Depth Camera D415](https://realsenseai.com/stereo-depth-cameras/stereo-depth-camera-d415/)
+- [Intel® RealSense™ Depth Camera D435](https://www.realsenseai.com/products/stereo-depth-camera-d435/)
+- [Intel® RealSense™ Depth Camera D415](https://www.realsenseai.com/products/stereo-depth-camera-d415/)
 - [DUO MLX](https://duo3d.com/product/duo-minilx-lv1)
 
 ### VIO Cameras/Sensors
diff --git a/docs/en/complete_vehicles_mc/px4_vision_kit.md b/docs/en/complete_vehicles_mc/px4_vision_kit.md
index e20ea0da32..f7267a0888 100644
--- a/docs/en/complete_vehicles_mc/px4_vision_kit.md
+++ b/docs/en/complete_vehicles_mc/px4_vision_kit.md
@@ -67,7 +67,7 @@ Difference between the PX4 Vision V1 and V1.5 can be found [here](https://docs.h
 
 ![PV4 Vision v1.5](../../assets/hardware/px4_vision_devkit/px4_vision_v1.5_whats_inside.jpg)
 
-What's inside the PX4 Vision V1 can be found here in the [PX4 v1.13 Docs here](https://docs.px4.io/v1.13/en/complete_vehicles/px4_vision_kit.html#what-is-inside).
+What's inside the PX4 Vision V1 can be found here in the [PX4 v1.13 Docs here](https://docs.px4.io/v1.13/en/complete_vehicles/px4_vision_kit#what-is-inside).
 
 The PX4 Vision DevKit contains following components:
 
@@ -381,7 +381,7 @@ The carrier board pinouts and other information are in the [downloads section](h
 ## Other Development Resources
 
 - [_UP Core_ Wiki](https://github.com/up-board/up-community/wiki/Ubuntu) - _Up Core_ companion computer technical information
-- [Occipital Developer Forum](https://structure.io/developers/) - _Structure Core_ camera information
+- [Occipital Developer Forum](https://structure.io/structure-sdk) - _Structure Core_ camera information
 - [Pixhawk 4 Overview](../flight_controller/pixhawk4.md)
 - [Pixhawk 6C Overview](../flight_controller/pixhawk6c.md)
 
diff --git a/docs/en/computer_vision/path_planning_interface.md b/docs/en/computer_vision/path_planning_interface.md
index 57e0d4f8c6..19a56738e6 100644
--- a/docs/en/computer_vision/path_planning_interface.md
+++ b/docs/en/computer_vision/path_planning_interface.md
@@ -18,4 +18,4 @@ This interface allows PX4 to stream a proposed path to a companion computer, and
 This enables features such obstacle avoidance in missions and safer landing to be provided by a planner on a companion computer.
 
 This actual code is still present in code at time of writing (PX4 v1.15).
-Information about the API and associated features can be found in the [PX4 v1.14 docs](https://docs.px4.io/v1.14/en/computer_vision/path_planning_interface.html).
+Information about the API and associated features can be found in the [PX4 v1.14 docs](https://docs.px4.io/v1.14/en/computer_vision/path_planning_interface).
diff --git a/docs/en/concept/control_allocation.md b/docs/en/concept/control_allocation.md
index d6e60189f2..1467a705c3 100644
--- a/docs/en/concept/control_allocation.md
+++ b/docs/en/concept/control_allocation.md
@@ -2,7 +2,7 @@
 
 ::: info
 Control allocation replaces the legacy mixing approach used in PX4 v1.13 and earlier.
-For PX4 v1.13 documentation see: [Mixing & Actuators](https://docs.px4.io/v1.13/en/concept/mixing.html), [Geometry Files](https://docs.px4.io/v1.13/en/concept/geometry_files.html) and [Adding a New Airframe Configuration](https://docs.px4.io/v1.13/en/dev_airframes/adding_a_new_frame.html).
+For PX4 v1.13 documentation see: [Mixing & Actuators](https://docs.px4.io/v1.13/en/concept/mixing), [Geometry Files](https://docs.px4.io/v1.13/en/concept/geometry_files) and [Adding a New Airframe Configuration](https://docs.px4.io/v1.13/en/dev_airframes/adding_a_new_frame).
 :::
 
 PX4 takes desired torque and thrust commands from the core controllers and translates them to actuator commands which control motors or servos.
diff --git a/docs/en/contribute/dev_call.md b/docs/en/contribute/dev_call.md
index 54c4dfff08..fe0ecf558c 100644
--- a/docs/en/contribute/dev_call.md
+++ b/docs/en/contribute/dev_call.md
@@ -7,7 +7,7 @@ const { site } = useData();
 
 <div v-if="site.title !== 'PX4 Guide (main)'">
   <div class="custom-block danger">
-    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/contribute/dev_call.html">See the latest version</a>.</p>
+    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/contribute/dev_call">See the latest version</a>.</p>
   </div>
 </div>
 
@@ -36,4 +36,4 @@ Please add your topics for discussion to the agenda before the meeting begins, b
 ## Schedule
 
 - TIME: Wednesday 17h00 CET ([subscribe to calendar](https://dronecode.org/calendar/))
-- **Join the call**: [https://discord.gg/BDYmr6FA6Q](https://discord.gg/BDYmr6FA6Q)
+- **Join the call**: [https://discord.com/invite/BDYmr6FA6Q](https://discord.com/invite/BDYmr6FA6Q)
diff --git a/docs/en/contribute/docs.md b/docs/en/contribute/docs.md
index b0e03e247c..acdb2d1382 100644
--- a/docs/en/contribute/docs.md
+++ b/docs/en/contribute/docs.md
@@ -54,7 +54,7 @@ If you already have a clone of the [PX4-Autopilot](https://github.com/PX4/PX4-Au
 To get the library(s) sources onto your local computer you will need to use the git toolchain.
 The instructions below explain how to get git and use it on your local computer.
 
-1. Download git for your computer from [https://git-scm.com/downloads](https://git-scm.com/downloads)
+1. Download git for your computer from [https://git-scm.com/downloads/](https://git-scm.com/downloads/)
 1. [Sign up](https://github.com/signup) for Github if you haven't already
 1. Create a copy (Fork) of the [PX4-Autopilot repo](https://github.com/PX4/PX4-Autopilot) on Github ([instructions here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)).
 1. Clone (copy) your forked repository to your local computer:
@@ -79,7 +79,7 @@ The instructions below explain how to get git and use it on your local computer.
 1. Add a _remote_ called "upstream" to point to the "official" PX4 version of the library:
 
    ```sh
-   git remote add upstream https://github.com/PX4/PX4-Autopilot.git
+   git remote add upstream https://github.com/PX4/PX4-Autopilot
    ```
 
    :::tip
diff --git a/docs/en/contribute/git_examples.md b/docs/en/contribute/git_examples.md
index 87c60b27fd..d7bc91ad4d 100644
--- a/docs/en/contribute/git_examples.md
+++ b/docs/en/contribute/git_examples.md
@@ -20,7 +20,7 @@ Adding a feature to PX4 follows a defined workflow. In order to share your contr
   ```sh
   cd PX4-Autopilot
   git submodule update --init --recursive
-  git remote add upstream https://github.com/PX4/PX4-Autopilot.git
+  git remote add upstream https://github.com/PX4/PX4-Autopilot
   ```
 
 - You should have now two remote repositories: One repository is called `upstream` that points to PX4/PX4-Autopilot, and one repository `origin` that points to your forked copy of the PX4 repository.
@@ -55,7 +55,7 @@ Adding a feature to PX4 follows a defined workflow. In order to share your contr
 
   For a good commit message, please refer to the [Source Code Management](../contribute/code.md#commits-and-commit-messages) section.
 
-- Some time might have passed and the [upstream main](https://github.com/PX4/PX4-Autopilot.git) has changed.
+- Some time might have passed and the [upstream main](https://github.com/PX4/PX4-Autopilot) has changed.
   PX4 prefers a linear commit history and uses [git rebase](https://git-scm.com/book/en/v2/Git-Branching-Rebasing).
   To include the newest changes from upstream in your local branch, switch to your main branch
 
@@ -134,7 +134,7 @@ To get the source code for a _specific older release_ (tag):
 1. Clone the PX4-Autopilot repo and navigate into _PX4-Autopilot_ directory:
 
    ```sh
-   git clone https://github.com/PX4/PX4-Autopilot.git
+   git clone https://github.com/PX4/PX4-Autopilot
    cd PX4-Autopilot
    ```
 
@@ -173,7 +173,7 @@ To get a release branch:
 - Clone the PX4-Autopilot repo and navigate into _PX4-Autopilot_ directory:
 
   ```sh
-  git clone https://github.com/PX4/PX4-Autopilot.git
+  git clone https://github.com/PX4/PX4-Autopilot
   cd PX4-Autopilot
   ```
 
diff --git a/docs/en/contribute/support.md b/docs/en/contribute/support.md
index 59cd6541ba..71642e7aee 100644
--- a/docs/en/contribute/support.md
+++ b/docs/en/contribute/support.md
@@ -7,7 +7,7 @@ const { site } = useData();
 
 <div v-if="site.title !== 'PX4 Guide (main)'">
   <div class="custom-block danger">
-    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/contribute/support.html">See the latest version</a>.</p>
+    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/contribute/support">See the latest version</a>.</p>
   </div>
 </div>
 
@@ -18,7 +18,7 @@ This section shows how you can get help from the core dev team and the wider com
 The core development team and community are active on the following channels:
 
 - [PX4 Discuss Forum](https://discuss.px4.io/) - Post here first!
-- [PX4 Discord](https://discord.gg/dronecode) - Post here if you don't get a response in discuss within a few days (include a link to your forum topic).
+- [PX4 Discord](https://discord.com/invite/dronecode) - Post here if you don't get a response in discuss within a few days (include a link to your forum topic).
 
 :::tip
 The Discuss Forum is much preferred because it is indexed by search engines and serves as a common knowledge base.
diff --git a/docs/en/dev_log/log_encryption.md b/docs/en/dev_log/log_encryption.md
index 23280698e0..e57bbba841 100644
--- a/docs/en/dev_log/log_encryption.md
+++ b/docs/en/dev_log/log_encryption.md
@@ -15,7 +15,7 @@ To use it you will need to build firmware with this feature enabled and then upl
 Log encryption was has been improved in PX4 v1.16 to generate a single encrypted log file that contains both encrypted log data, and an encrypted symmetric key that you can use to decrypt it (provided you can decrypt the symmetric key).
 
 In earlier versions the encrypted symmetric key was stored in a separate file.
-For more information see the [Log Encryption (PX4 v1.15)](https://docs.px4.io/v1.15/en/dev_log/log_encryption.html).
+For more information see the [Log Encryption (PX4 v1.15)](https://docs.px4.io/v1.15/en/dev_log/log_encryption).
 :::
 
 ## How ULog Encryption Works
diff --git a/docs/en/dev_setup/dev_env_windows_vm.md b/docs/en/dev_setup/dev_env_windows_vm.md
index 43704c78d2..2b9f7b1c2d 100644
--- a/docs/en/dev_setup/dev_env_windows_vm.md
+++ b/docs/en/dev_setup/dev_env_windows_vm.md
@@ -29,7 +29,7 @@ There is also an incomplete section for VirtualBox at the end (we'd welcome expa
 
 VMWare performance is acceptable for basic usage (building Firmware) but not for running ROS or Gazebo Classic.
 
-1. Download [VMWare Player Freeware](https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html)
+1. Download [VMWare Player Freeware](https://www.vmware.com/info/workstation-player/evaluation)
 1. Install it on your Windows system
 1. Download the desired version of [Ubuntu Desktop ISO Image](https://ubuntu.com/download/desktop).
    (see [Linux Instructions Page](../dev_setup/dev_env_linux.md) for recommended Ubuntu version).
diff --git a/docs/en/dev_setup/qtcreator.md b/docs/en/dev_setup/qtcreator.md
index dd18bc946d..2769fc93fa 100644
--- a/docs/en/dev_setup/qtcreator.md
+++ b/docs/en/dev_setup/qtcreator.md
@@ -8,7 +8,7 @@ Qt Creator has been replaced by [VSCode](../dev_setup/vscode.md) as the official
 See [Toolchain Installation](../dev_setup/dev_env.md) for information about the environments and tools supported by the core development team.
 :::
 
-[Qt Creator](https://www.qt.io/download-open-source) is a popular cross-platform open-source IDE that can be used to compile and debug PX4.
+[Qt Creator](https://www.qt.io/development/download-open-source) is a popular cross-platform open-source IDE that can be used to compile and debug PX4.
 
 ## Qt Creator Functionality
 
diff --git a/docs/en/flight_controller/autopilot_discontinued.md b/docs/en/flight_controller/autopilot_discontinued.md
index 2ae824c9a2..60257d68dd 100644
--- a/docs/en/flight_controller/autopilot_discontinued.md
+++ b/docs/en/flight_controller/autopilot_discontinued.md
@@ -26,6 +26,6 @@ They are listed because you may be using them in an existing drone, and because
 
 ## Complete Vehicles
 
-- [BetaFPV Beta75X 2S Brushless Whoop](https://docs.px4.io/v1.14/en/complete_vehicles/betafpv_beta75x.html#betafpv-beta75x-2s-brushless-whoop) (circa PX4 v1.14)
-- [Intel® Aero RTF Drone](https://docs.px4.io/v1.12/en/complete_vehicles/intel_aero.html) (circa PX4 v1.12)
-- [Qualcomm Snapdragon Flight](https://docs.px4.io/v1.11/en/flight_controller/snapdragon_flight.html) (circa PX4 v1.11)
+- [BetaFPV Beta75X 2S Brushless Whoop](https://docs.px4.io/v1.14/en/complete_vehicles/betafpv_beta75x#betafpv-beta75x-2s-brushless-whoop) (circa PX4 v1.14)
+- [Intel® Aero RTF Drone](https://docs.px4.io/v1.12/en/complete_vehicles/intel_aero) (circa PX4 v1.12)
+- [Qualcomm Snapdragon Flight](https://docs.px4.io/v1.11/en/flight_controller/snapdragon_flight) (circa PX4 v1.11)
diff --git a/docs/en/flight_controller/dropix.md b/docs/en/flight_controller/dropix.md
index e400005541..8faa347f83 100644
--- a/docs/en/flight_controller/dropix.md
+++ b/docs/en/flight_controller/dropix.md
@@ -4,4 +4,4 @@
 
 The Drotek<sup>&reg;</sup> _DroPix autopilot_ is no longer available on the Drotek website, and is assumed to be discontinued.
 
-See [PX4 v1.13 Documentation > DroPix Flight Controller](https://docs.px4.io/v1.13/en/flight_controller/dropix.html) for documentation.
+See [PX4 v1.13 Documentation > DroPix Flight Controller](https://docs.px4.io/v1.13/en/flight_controller/dropix) for documentation.
diff --git a/docs/en/flight_controller/modalai_fc_v1.md b/docs/en/flight_controller/modalai_fc_v1.md
index a311cc1723..1a0027718a 100644
--- a/docs/en/flight_controller/modalai_fc_v1.md
+++ b/docs/en/flight_controller/modalai_fc_v1.md
@@ -11,12 +11,12 @@ PX4 does not manufacture this (or any) autopilot.
 Contact the [manufacturer](https://forum.modalai.com/) for hardware support or compliance issues.
 :::
 
-The ModalAI _Flight Core v1_ ([Datasheet](https://docs.modalai.com/flight-core-datasheet)) is a flight controller for PX4, made in the USA.
+The ModalAI _Flight Core v1_ ([Datasheet](https://docs.modalai.com/flight-core-datasheet/)) is a flight controller for PX4, made in the USA.
 The Flight Core can be paired with ModalAI VOXL for obstacle avoidance and GPS-denied navigation, or used independently as a standalone flight controller.
 
 ![FlightCoreV1](../../assets/flight_controller/modalai/fc_v1/main.jpg)
 
-Flight Core is identical to the PX4 Flight Controller portion of [VOXL Flight](https://www.modalai.com/voxl-flight) ([Datasheet](https://docs.modalai.com/voxl-flight-datasheet/)) which integrates the VOXL Companion Computer and Flight Core into a single PCB.
+Flight Core is identical to the PX4 Flight Controller portion of [VOXL Flight](https://www.modalai.com/pages/eol) ([Datasheet](https://docs.modalai.com/voxl-flight-datasheet/)) which integrates the VOXL Companion Computer and Flight Core into a single PCB.
 
 ::: info
 This flight controller is [manufacturer supported](../flight_controller/autopilot_manufacturer_supported.md).
@@ -93,7 +93,7 @@ The diagram below shows the recommended orientation, which corresponds to `ROTAT
 
 ### Connectors
 
-Detailed information about the pinouts can be found [here](https://docs.modalai.com/flight-core-datasheet-connectors).
+Detailed information about the pinouts can be found [here](https://docs.modalai.com/flight-core-datasheet-connectors/).
 
 ![FlightCoreV1Top](../../assets/flight_controller/modalai/fc_v1/top.png)
 
diff --git a/docs/en/flight_controller/modalai_voxl_2.md b/docs/en/flight_controller/modalai_voxl_2.md
index 63d7bc7213..03e8836da9 100644
--- a/docs/en/flight_controller/modalai_voxl_2.md
+++ b/docs/en/flight_controller/modalai_voxl_2.md
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
 Contact the [manufacturer](https://forum.modalai.com/) for hardware support or compliance issues.
 :::
 
-The ModalAI [VOXL 2](https://modalai.com/voxl-2) ([Datasheet](https://docs.modalai.com/voxl2-datasheets/)) is ModalAI’s next-gen autonomous computing platform built around the Qualcomm QRB5165 processor. VOXL 2 boasts 8 cores, integrated PX4, seven camera concurrency, advanced onboard AI up to 15+ TOPS, and 5G connectivity. At 16 grams, VOXL 2 is the future of fully autonomous and connected drones!
+The ModalAI [VOXL 2](https://www.modalai.com/products/voxl-2) ([Datasheet](https://docs.modalai.com/voxl2-datasheets/)) is ModalAI's next-gen autonomous computing platform built around the Qualcomm QRB5165 processor. VOXL 2 boasts 8 cores, integrated PX4, seven camera concurrency, advanced onboard AI up to 15+ TOPS, and 5G connectivity. At 16 grams, VOXL 2 is the future of fully autonomous and connected drones!
 
 ![VOXL-2](../../assets/flight_controller/modalai/voxl_2/voxl-2-hero.jpg)
 
diff --git a/docs/en/flight_controller/mro_control_zero_f7.md b/docs/en/flight_controller/mro_control_zero_f7.md
index 97a97004b5..5848e7338f 100644
--- a/docs/en/flight_controller/mro_control_zero_f7.md
+++ b/docs/en/flight_controller/mro_control_zero_f7.md
@@ -30,7 +30,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
   - [Bosch BMI088](https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi088/) 3-axis accelerometer/gyroscope (internally vibration dampened)
   - [Invensense ICM-20602](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-20602/) 3-axis accelerometer/gyroscope
   - [Invensense ICM-20948](https://invensense.tdk.com/products/motion-tracking/9-axis/icm-20948/) 3-axis accelerometer/gyroscope/magnetometer
-  - [Infineon DPS310 barometer](https://www.infineon.com/assets/row/public/documents/24/49/infineon-dps310-datasheet-en.pdf) - [Discontinued](https://www.infineon.com/part/DPS310) (So smooth and NO more light sensitivity)
+  - Infineon DPS310 barometer - [Discontinued](https://www.infineon.com/products/sensor/pressure-sensors/pressure-sensors-for-iot) (So smooth and NO more light sensitivity)
 
 - Interfaces:
   - 6x UART (serial ports total), 3x with HW flow control, 1x FRSky Telemetry (D or X types), 1x Console and 1x GPS+I2C
diff --git a/docs/en/flight_controller/ocpoc_zynq.md b/docs/en/flight_controller/ocpoc_zynq.md
index 8c0be56b77..42393ce0d4 100644
--- a/docs/en/flight_controller/ocpoc_zynq.md
+++ b/docs/en/flight_controller/ocpoc_zynq.md
@@ -6,7 +6,7 @@
 This flight controller has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available.
 
 PX4 v1.11 is the last release that has (experimental) support for this platform.
-See the [PX4v1.11 docs](http://docs.px4.io/v1.11/en/flight_controller/ocpoc_zynq.html#aerotenna-ocpoc-zynq-mini-flight-controller) for more information.
+See the [PX4v1.11 docs](https://docs.px4.io/v1.11/en/flight_controller/ocpoc_zynq#aerotenna-ocpoc-zynq-mini-flight-controller) for more information.
 :::
 
 ![ocpoc-zynq-mini](../../assets/hardware/hardware-ocpoc-zynq-mini.jpg)
diff --git a/docs/en/flight_controller/pixhawk6x-rt.md b/docs/en/flight_controller/pixhawk6x-rt.md
index 1fd9a52979..bc9e868ad8 100644
--- a/docs/en/flight_controller/pixhawk6x-rt.md
+++ b/docs/en/flight_controller/pixhawk6x-rt.md
@@ -122,7 +122,7 @@ The Pixhawk®​ 6X-RT is perfect for developers at corporate research labs, sta
 
 ## Where to Buy {#store}
 
-Order from [Holybro](https://holybro.com/products/fmuv6x-rt-developer-edition).
+Order from [Holybro](https://holybro.com/products/pixhawk-6x-rt).
 
 ## Assembly/Setup
 
diff --git a/docs/en/frames_multicopter/dji_f450_cuav_5nano.md b/docs/en/frames_multicopter/dji_f450_cuav_5nano.md
index 5ebbd550a9..769351f2dc 100644
--- a/docs/en/frames_multicopter/dji_f450_cuav_5nano.md
+++ b/docs/en/frames_multicopter/dji_f450_cuav_5nano.md
@@ -15,7 +15,7 @@ Key information
 The components needed for this build are:
 
 - Flight controller: [CUAV V5 nano](https://store.cuav.net/shop/v5-nano/):
-  - GPS: [CUAV NEO V2 GPS](https://store.cuav.net/index.php?id_product=97&id_product_attribute=0&rewrite=cuav-new-ublox-neo-m8n-gps-module-with-shell-stand-holder-for-flight-controller-gps-compass-for-pixhack-v5-plus-rc-parts-px4&controller=product&id_lang=1)
+  - GPS: [CUAV NEO V2 GPS](https://store.cuav.net/?id_product=97&id_product_attribute=0&rewrite=cuav-new-ublox-neo-m8n-gps-module-with-shell-stand-holder-for-flight-controller-gps-compass-for-pixhack-v5-plus-rc-parts-px4&controller=product&id_lang=1)
   - Power Module
 - Frame: [DJI F450](https://www.amazon.com/Flame-Wheel-Basic-Quadcopter-Drone/dp/B00HNMVQHY)
 - Propellers: [DJI Phantom Built-in Nut Upgrade Propellers 9.4x5](https://www.masterairscrew.com/products/dji-phantom-built-in-nut-upgrade-propellers-in-black-mr-9-4x5-prop-set-x4-phantom)
diff --git a/docs/en/frames_multicopter/omnicopter.md b/docs/en/frames_multicopter/omnicopter.md
index e8732e113d..517aec2440 100644
--- a/docs/en/frames_multicopter/omnicopter.md
+++ b/docs/en/frames_multicopter/omnicopter.md
@@ -19,7 +19,7 @@ The components needed for this build are:
     You can select your own flight controller of choice, it just needs to support 8 DShot outputs.
     :::
   - GPS: [ZED-F9P](https://gnss.store/zed-f9p-gnss-modules/105-elt0092.html)
-  - [GPS helix antenna](https://gnss.store/gnss-rtk-multiband-antennas/28-elt0014.html)
+  - [GPS helix antenna](https://gnss.store/products/elt0014)
     ::: info
     Any other GPS may work as well, however a helix antenna is expected to perform better for inverted flights.
     :::
@@ -32,8 +32,8 @@ The components needed for this build are:
   - Battery: we used a 6S 3300mAh LiPo. Make sure to check the dimensions so it fits the frame.
   - Battery strap
 - Frame:
-  - Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/Vierkant-Rohre/CFK-Vierkantrohr-8x8-7x7mm.html)
-  - Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/CFK-Rohre-pultrudiert-pullwinding/Carbon-Microtubes-100cm-x-20-3mm.html)
+  - Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/Vierkant-Rohre/CFK-Vierkantrohr-8x8-7x7mm.html)
+  - Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/CFK-Rohre-pultrudiert-pullwinding/Carbon-Microtubes-100cm-x-20-3mm.html)
   - Required lengths:
     - square tube: 8 pieces with length of 248mm
     - rods: 12x328mm, 6x465mm
diff --git a/docs/en/frames_plane/reptile_dragon_2.md b/docs/en/frames_plane/reptile_dragon_2.md
index fff7047ce3..be2aa27274 100644
--- a/docs/en/frames_plane/reptile_dragon_2.md
+++ b/docs/en/frames_plane/reptile_dragon_2.md
@@ -49,12 +49,12 @@ Key build features
 - [Holybro M9N GPS module](https://holybro.com/products/m9n-gps)
 - Holybro PWM breakout board
 - MS4525DO differential pressure module and pitot tube
-- [Caddx Vista FPV air unit](https://caddxfpv.com/collections/vista-kit)
+- [Caddx Vista FPV air unit](https://www.caddxfpv.com/collections/vista-kit)
 - [Emax ES08MA ii](https://emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo)
 - [DJI FPV Goggles](https://www.dji.com/fpv)
 - [ExpressLRS Matek Diversity RX](https://www.mateksys.com/?portfolio=elrs-r24)
 - [5V BEC](https://www.readymaderc.com/products/details/rmrc-3a-power-regulator-5-to-6-volt-ubec)
-- [6s2p 18650 LiIon flight battery](https://www.upgradeenergytech.com/product-page/6s-22-2v-5600mah-30c-dark-lithium-liion-drone-battery) (select XT60 connector)
+- [6s2p 18650 LiIon flight battery](https://www.upgradeenergytech.com/products/red-6s1p-5000mah-molicel-p50b) (select XT60 connector)
 - [Custom designed 3D printed parts](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/fw/reptile_dragon_2/rd2_3d_printed_parts.zip)
   - ARK6X carrier mount
   - Holybro Pixhawk 5x carrier mount
diff --git a/docs/en/frames_plane/turbo_timber_evolution.md b/docs/en/frames_plane/turbo_timber_evolution.md
index e39f8dbbd1..325aada1f9 100644
--- a/docs/en/frames_plane/turbo_timber_evolution.md
+++ b/docs/en/frames_plane/turbo_timber_evolution.md
@@ -44,7 +44,7 @@ Key Build Features:
 - [SIK telemetry radio](../telemetry/sik_radio.md)
 
 - MS4525DO differential pressure module and pitot tube
-- [Caddx Vista FPV air unit](https://caddxfpv.com/collections/vista-kit)
+- [Caddx Vista FPV air unit](https://www.caddxfpv.com/collections/vista-kit)
 - [DJI FPV Goggles](https://www.dji.com/fpv)
 - [ExpressLRS Matek Diversity RX](https://www.mateksys.com/?portfolio=elrs-r24)
 - [Custom designed 3D printed parts](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/fw/turbo_timber_evolution/3d_printed_parts.zip)
@@ -62,7 +62,7 @@ Servos and linkages have already been installed, and the only real remaining wor
 For this portion of the assembly, simply follow the manual.
 
 ::: info
-[Some reports](https://www.rcgroups.com/forums/showthread.php?3904021-NEW-E-flite-Turbo-Timber-Evolution-1-5m-%C2%96-Smartest-Most-Capable-Durable-Timber-Yet/page50) have indicated that the stock ESC bundled with the airplane has an issue with overheating.
+[Some reports](https://www.rcgroups.com/forums/showthread.php?3904021-NEW-E-flite-Turbo-Timber-Evolution-1-5m/page50) have indicated that the stock ESC bundled with the airplane has an issue with overheating.
 
 As this build will be especially heavy, and therefore likely demand higher average power from the ESC, the stock 60A ESC was replaced with an 80A Turnigy PLUSH-32 during testing.
 The stock motor was also replaced with a [higher power motor](https://hobbyking.com/en_us/turnigy-aerodrive-sk3-3548-840kv-brushless-outrunner-motor.html).
diff --git a/docs/en/frames_sub/bluerov2.md b/docs/en/frames_sub/bluerov2.md
index 5056eea439..8402df3473 100644
--- a/docs/en/frames_sub/bluerov2.md
+++ b/docs/en/frames_sub/bluerov2.md
@@ -2,7 +2,7 @@
 
 <Badge type="tip" text="PX4 v1.12" />
 
-The [BlueROV2](https://bluerobotics.com/store/rov/bluerov2-upgrade-kits/brov2-heavy-retrofit-r1-rp/BlueROV2) is an
+The [BlueROV2](https://bluerobotics.com/store/rov/bluerov2/) is an
 affordable high-performance underwater vehicle that is perfect for inspections, research, and adventuring.
 
 PX4 provides [experimental support](index.md) for an 8-thrust vectored configuration, known as the _BlueROV2 Heavy
@@ -12,7 +12,7 @@ Configuration_.
 
 ## Where to Buy
 
-[BlueROV2](https://bluerobotics.com/store/rov/bluerov2/) + [BlueROV2 Heavy Configuration Retrofit Kit](https://bluerobotics.com/store/rov/bluerov2-upgrade-kits/brov2-heavy-retrofit-r1-rp/)
+[BlueROV2](https://bluerobotics.com/store/rov/bluerov2/) + [BlueROV2 Heavy Configuration Retrofit Kit](https://bluerobotics.com/store/rov/bluerov2-upgrade-kits/brov2-heavy-retrofit/)
 
 ### Motor Mapping/Wiring
 
diff --git a/docs/en/frames_vtol/tailsitter.md b/docs/en/frames_vtol/tailsitter.md
index cddc2bfb1e..0671f915d5 100644
--- a/docs/en/frames_vtol/tailsitter.md
+++ b/docs/en/frames_vtol/tailsitter.md
@@ -90,7 +90,7 @@ This section contains videos that are specific to Tailsitter VTOL (videos that a
 
 <div class="grid_wrapper three_column">
   <div class="grid_item">
-    <div class="grid_item_heading"><big><a href="https://wingtra.com/mapping-drone-wingtraone/">WingtraOne</a></big></div>
+    <div class="grid_item_heading"><big><a href="https://wingtra.com/mapping-drone-fast-accurate-surveying/">WingtraOne</a></big></div>
     <div class="grid_text">
     <img src="../../assets/airframes/vtol/wingtraone/hero.jpg" title="Wingtra: WingtraOne VTOL Duo Tailsitter" alt="wingtraone" />
     </div>
diff --git a/docs/en/frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md b/docs/en/frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md
index c3880cbf69..6856c0bba1 100644
--- a/docs/en/frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md
+++ b/docs/en/frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md
@@ -4,7 +4,7 @@ The Caipiroshka VTOL is a slightly modified _TBS Caipirinha_.
 
 ::: info
 The _TBS Caipirinha_ has been superseded and is no longer available.
-These instructions _should_ work with the updated vehicle: [TBS Caipirinha 2](https://team-blacksheep.com/products/prod:tbs_caipi2_pnp).
+These instructions _should_ work with the updated vehicle: [TBS Caipirinha 2](https://www.team-blacksheep.com/products/prod:tbs_caipi2_pnp).
 A number of other components have been updated in the parts list too.
 :::
 
@@ -12,7 +12,7 @@ A number of other components have been updated in the parts list too.
 
 ## Parts List
 
-- TBS Caipirinha Wing (no longer available - try [TBS Caipirinha 2](https://team-blacksheep.com/products/prod:tbs_caipi2_pnp))
+- TBS Caipirinha Wing (no longer available - try [TBS Caipirinha 2](https://www.team-blacksheep.com/products/prod:tbs_caipi2_pnp))
 - Left and right 3D-printed motor mount (<a href="https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/vtol/caipiroshka/motor_mounts.zip" target="_blank">design files</a>)
 - CW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-CWCCW-Propeller-For-Quadcopters-1-Pair-p-950874.html))
 - CCW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-CWCCW-Propeller-For-Quadcopters-1-Pair-p-950874.html))
diff --git a/docs/en/gps_compass/rtk_gps_cuav_c-rtk-9ps.md b/docs/en/gps_compass/rtk_gps_cuav_c-rtk-9ps.md
index cc41632a6c..c73553ed94 100644
--- a/docs/en/gps_compass/rtk_gps_cuav_c-rtk-9ps.md
+++ b/docs/en/gps_compass/rtk_gps_cuav_c-rtk-9ps.md
@@ -12,7 +12,7 @@ This is ideal for survey drones, agricultural drones and other application scena
 
 ## Where to Buy
 
-[cuav Store](https://store.cuav.net/shop/c-rtk-9ps/)
+[cuav Store](https://store.cuav.net/index.php?route=product/product&path=61&product_id=187)
 
 ## Specification
 
diff --git a/docs/en/gps_compass/rtk_gps_cuav_c-rtk2.md b/docs/en/gps_compass/rtk_gps_cuav_c-rtk2.md
index fcfeba3d6d..9a75f479d0 100644
--- a/docs/en/gps_compass/rtk_gps_cuav_c-rtk2.md
+++ b/docs/en/gps_compass/rtk_gps_cuav_c-rtk2.md
@@ -18,7 +18,7 @@ In addition to surveying/mapping, it is suitable for many other use-cases, inclu
 
 ## Where to Buy
 
-- [CUAV Store](https://store.cuav.net/shop/c-rtk-2/)
+- [CUAV Store](https://store.cuav.net/index.php?route=product/product&product_id=159)
 - [CUAV aliexpress](https://pt.aliexpress.com/item/1005003754165772.html?spm=a2g0o.store_pc_groupList.8148356.13.2f893550i0NE4o)
 
 # Quick Summary
diff --git a/docs/en/gps_compass/rtk_gps_drotek_xl.md b/docs/en/gps_compass/rtk_gps_drotek_xl.md
index 91e1d80245..867ef328d4 100644
--- a/docs/en/gps_compass/rtk_gps_drotek_xl.md
+++ b/docs/en/gps_compass/rtk_gps_drotek_xl.md
@@ -2,7 +2,7 @@
 
 ::: info
 This module appears to have been discontinued, and is no longer on the Drotek site (September 2023).
-The last documentation was in [PX4 v1.13 here](https://docs.px4.io/v1.13/en/gps_compass/rtk_gps_drotek_xl.html)
+The last documentation was in [PX4 v1.13 here](https://docs.px4.io/v1.13/en/gps_compass/rtk_gps_drotek_xl)
 :::
 
 <!-- delete ../../assets/hardware/gps/rtk_base_drotek_xl_rtk_gps.jpg if still present -->
diff --git a/docs/en/gps_compass/rtk_gps_hex_hereplus.md b/docs/en/gps_compass/rtk_gps_hex_hereplus.md
index b96de2a954..c4b924b9fe 100644
--- a/docs/en/gps_compass/rtk_gps_hex_hereplus.md
+++ b/docs/en/gps_compass/rtk_gps_hex_hereplus.md
@@ -5,7 +5,7 @@
 ::: info
 This GPS is no longer available for purchase but is still compatible with PX4.
 
-Usage documentation can be found in [PX4v1.11 docs](https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus.html)
+Usage documentation can be found in [PX4v1.11 docs](https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus)
 :::
 
 The **Here+ RTK GPS receiver** is a small, light and energy efficient [RTK GPS module](../gps_compass/rtk_gps.md), based on the u-blox M8P. Using RTK, PX4 can get its position with centimetre-level accuracy, which is much more accurate than can be provided by a normal GPS.
diff --git a/docs/en/gps_compass/rtk_gps_holybro_h-rtk-f9p.md b/docs/en/gps_compass/rtk_gps_holybro_h-rtk-f9p.md
index 80c6df2f41..cc1350d2cf 100644
--- a/docs/en/gps_compass/rtk_gps_holybro_h-rtk-f9p.md
+++ b/docs/en/gps_compass/rtk_gps_holybro_h-rtk-f9p.md
@@ -19,7 +19,7 @@ Using RTK allows PX4 to get its position with centimetre-level accuracy, which i
 ## Where to Buy
 
 - [H-RTK F9P (Holybro Website)](https://holybro.com/products/h-rtk-f9p-gnss-series)
-- [H-RTK Accessories (Holybro Website)](https://holybro.com/collections/h-rtk-gps)
+- [H-RTK Accessories (Holybro Website)](https://holybro.com/collections/gps)
 
 ## Configuration
 
@@ -50,6 +50,6 @@ The cables/connectors may need to be modified in order to connect to other fligh
 
 ## GPS Accessories
 
-[H-RTK Mount (Holybro Website)](https://holybro.com/products/vertical-mount-for-h-rtk-helical)
+[H-RTK Mount (Holybro Website)](https://holybro.com/collections/gps-accessories/products/vertical-mount-for-h-rtk-helical)
 
 ![h-rtk](../../assets/hardware/gps/rtk_holybro_h-rtk_mount_3.png)
diff --git a/docs/en/gps_compass/rtk_gps_holybro_h-rtk-m8p.md b/docs/en/gps_compass/rtk_gps_holybro_h-rtk-m8p.md
index 59f0441912..2d09d57079 100644
--- a/docs/en/gps_compass/rtk_gps_holybro_h-rtk-m8p.md
+++ b/docs/en/gps_compass/rtk_gps_holybro_h-rtk-m8p.md
@@ -16,7 +16,7 @@ Using RTK allows PX4 to get its position with centimeter-level accuracy, which i
 
 ## Where to Buy
 
-- [H-RTK M8P (GPS RTK Mounts)](https://holybro.com/products/vertical-mount-for-h-rtk-helical)
+- [H-RTK M8P (GPS RTK Mounts)](https://holybro.com/collections/gps-accessories/products/vertical-mount-for-h-rtk-helical)
 
 ## Configuration
 
diff --git a/docs/en/index.md b/docs/en/index.md
index f361486948..4f465f1fcc 100644
--- a/docs/en/index.md
+++ b/docs/en/index.md
@@ -5,7 +5,7 @@ const { site } = useData();
 
 # PX4 Autopilot User Guide
 
-[![Releases](https://img.shields.io/badge/release-main-blue.svg)](https://github.com/PX4/PX4-Autopilot/releases) [![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](https://discuss.px4.io//) [![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.gg/dronecode)
+[![Releases](https://img.shields.io/badge/release-main-blue.svg)](https://github.com/PX4/PX4-Autopilot/releases) [![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](https://discuss.px4.io//) [![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.com/invite/dronecode)
 
 PX4 is an open-source autopilot for drones and autonomous vehicles. It runs on multirotors, fixed-wing, VTOL, helicopters, rovers, and more. This guide covers everything from assembly and configuration to flight operations and development.
 
@@ -49,7 +49,7 @@ Read [Operations](config/operations.md) to understand safety features and failsa
 
 ## Support
 
-Get help on the [discussion forums](https://discuss.px4.io/) or [Discord](https://discord.gg/dronecode). See the [Support](contribute/support.md) page for diagnosing problems, reporting bugs, and joining the [weekly dev call](contribute/dev_call.md).
+Get help on the [discussion forums](https://discuss.px4.io/) or [Discord](https://discord.com/invite/dronecode). See the [Support](contribute/support.md) page for diagnosing problems, reporting bugs, and joining the [weekly dev call](contribute/dev_call.md).
 
 ## Contributing
 
@@ -93,9 +93,9 @@ The following icons used in this library are licensed separately (as shown below
 
 ## Governance
 
-The PX4 Autopilot project is hosted by the [Dronecode Foundation](https://www.dronecode.org/), a [Linux Foundation](https://www.linuxfoundation.org/) Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship. No single company owns the name or controls the roadmap. The source code is licensed under the [BSD 3-Clause](https://opensource.org/license/BSD-3-Clause) license, so you are free to use, modify, and distribute it in your own projects.
+The PX4 Autopilot project is hosted by the [Dronecode Foundation](https://dronecode.org/), a [Linux Foundation](https://www.linuxfoundation.org/) Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship. No single company owns the name or controls the roadmap. The source code is licensed under the [BSD 3-Clause](https://opensource.org/license/BSD-3-Clause) license, so you are free to use, modify, and distribute it in your own projects.
 
-<a href="https://www.dronecode.org/" style="padding:20px"><img src="../assets/site/dronecode_logo.svg" alt="Dronecode Logo" width="140px"/></a>
+<a href="https://dronecode.org/" style="padding:20px"><img src="../assets/site/dronecode_logo.svg" alt="Dronecode Logo" width="140px"/></a>
 <a href="https://www.linuxfoundation.org/projects" style="padding:20px;"><img src="../assets/site/logo_linux_foundation.png" alt="Linux Foundation Logo" width="80px" /></a>
 
 <div style="padding:10px">&nbsp;</div>
diff --git a/docs/en/middleware/micrortps.md b/docs/en/middleware/micrortps.md
index 47d08fd85e..2756225261 100644
--- a/docs/en/middleware/micrortps.md
+++ b/docs/en/middleware/micrortps.md
@@ -3,4 +3,4 @@
 <Badge type="info" text="Discontinued" />
 
 [uXRCE-DDS (PX4-ROS 2/DDS Bridge)](../middleware/uxrce_dds.md) has replaced the _Fast-RTPS Bridge_.
-If you're working in PX4 v1.13 or earlier see: [Fast-RTPS Bridge](https://docs.px4.io/v1.13/en/middleware/micrortps.html#rtps-dds-interface-px4-fast-rtps-dds-bridge)
+If you're working in PX4 v1.13 or earlier see: [Fast-RTPS Bridge](https://docs.px4.io/v1.13/en/middleware/micrortps#rtps-dds-interface-px4-fast-rtps-dds-bridge)
diff --git a/docs/en/middleware/uxrce_dds.md b/docs/en/middleware/uxrce_dds.md
index 806fe0f479..917f0d538a 100644
--- a/docs/en/middleware/uxrce_dds.md
+++ b/docs/en/middleware/uxrce_dds.md
@@ -3,7 +3,7 @@
 <Badge type="tip" text="PX4 v1.14" />
 
 ::: info
-uXRCE-DDS replaces the [Fast-RTPS Bridge](https://docs.px4.io/v1.13/en/middleware/micrortps.html#rtps-dds-interface-px4-fast-rtps-dds-bridge) used in PX4 v1.13.
+uXRCE-DDS replaces the [Fast-RTPS Bridge](https://docs.px4.io/v1.13/en/middleware/micrortps#rtps-dds-interface-px4-fast-rtps-dds-bridge) used in PX4 v1.13.
 If you were using the Fast-RTPS Bridge, please follow the [migration guidelines](#fast-rtps-to-uxrce-dds-migration-guidelines).
 :::
 
@@ -584,7 +584,7 @@ For a list of services, details and examples see the [service documentation](../
 ## Fast-RTPS to uXRCE-DDS Migration Guidelines
 
 These guidelines explain how to migrate from using PX4 v1.13 [Fast-RTPS](../middleware/micrortps.md) middleware to PX4 v1.14 `uXRCE-DDS` middleware.
-These are useful if you have [ROS 2 applications written for PX4 v1.13](https://docs.px4.io/v1.13/en/ros/ros2_comm.html), or you have used Fast-RTPS to interface your applications to PX4 [directly](https://docs.px4.io/v1.13/en/middleware/micrortps.html#agent-in-an-offboard-fast-dds-interface-ros-independent).
+These are useful if you have [ROS 2 applications written for PX4 v1.13](https://docs.px4.io/v1.13/en/ros/ros2_comm), or you have used Fast-RTPS to interface your applications to PX4 [directly](https://docs.px4.io/v1.13/en/middleware/micrortps#agent-in-an-offboard-fast-dds-interface-ros-independent).
 
 ::: info
 This section contains migration-specific information.
@@ -593,7 +593,7 @@ You should also read the rest of this page to properly understand uXRCE-DDS.
 
 #### Dependencies do not need to be removed
 
-uXRCE-DDS does not need the dependencies that were required for Fast-RTPS, such as those installed by following the topic [Fast DDS Installation](https://docs.px4.io/v1.13/en/dev_setup/fast-dds-installation.html).
+uXRCE-DDS does not need the dependencies that were required for Fast-RTPS, such as those installed by following the topic [Fast DDS Installation](https://docs.px4.io/v1.13/en/dev_setup/fast-dds-installation).
 You can keep them if you want, without affecting your uXRCE-DDS applications.
 
 If you do choose to remove the dependencies, take care not to remove anything that is used by applications (for example, Java).
@@ -646,7 +646,7 @@ There are many ways to install it on your PC / companion computer - for more inf
 
 #### Application-Specific Changes
 
-If you where not using ROS 2 alongside the agent ([Fast DDS Interface ROS-Independent](https://docs.px4.io/v1.13/en/middleware/micrortps.html#agent-in-an-offboard-fast-dds-interface-ros-independent)), then you need to migrate to [eProsima Fast DDS](https://fast-dds.docs.eprosima.com/en/latest/index.html).
+If you where not using ROS 2 alongside the agent ([Fast DDS Interface ROS-Independent](https://docs.px4.io/v1.13/en/middleware/micrortps#agent-in-an-offboard-fast-dds-interface-ros-independent)), then you need to migrate to [eProsima Fast DDS](https://fast-dds.docs.eprosima.com/en/latest/index.html).
 
 ROS 2 applications still need to compile alongside the PX4 messages, which you do by adding the [px4_msgs](https://github.com/PX4/px4_msgs) package to your workspace.
 You can remove the [px4_ros_com](https://github.com/PX4/px4_ros_com) package as it is no longer needed, other than for example code.
diff --git a/docs/en/releases/1.12.md b/docs/en/releases/1.12.md
index 0c1f8dcb35..209d36411f 100644
--- a/docs/en/releases/1.12.md
+++ b/docs/en/releases/1.12.md
@@ -124,7 +124,7 @@ These are removed:
 
 ### NuttX
 
-Nuttx was upgraded from [8.2+ to NuttX 10.10.0+](https://github.com/apache/incubator-nuttx/compare/nuttx-8.2..nuttx-10.0.1) (@ [904a602c74dc08a100b5c2bd490807de19e73e10](https://github.com/apache/incubator-nuttx/commit/904a602c74dc08a100b5c2bd490807de19e73e10))
+Nuttx was upgraded from [8.2+ to NuttX 10.10.0+](https://github.com/apache/nuttx/compare/nuttx-8.2..nuttx-10.0.1) (@ [904a602c74dc08a100b5c2bd490807de19e73e10](https://github.com/apache/nuttx/commit/904a602c74dc08a100b5c2bd490807de19e73e10))
 
 - **SDCARD performance:** Results in better performance on H7 Targets
   - [**BACKPORT**] stm32:SDIO:Use 250 Ms Data path timeout, regardless of Card Clock frequency
diff --git a/docs/en/releases/1.14.md b/docs/en/releases/1.14.md
index 71f9522c22..ad5c81ff56 100644
--- a/docs/en/releases/1.14.md
+++ b/docs/en/releases/1.14.md
@@ -51,10 +51,10 @@ The new [Failsafe State Machine Simulation](../config/safety_simulation.md) allo
 
 ### New Gazebo
 
-Given [the recent changes](https://discourse.ros.org/t/a-new-era-for-gazebo-cross-post/25012) by the Open Robotics simulation team, we are introducing name changes for our gazebo simulations, mirroring Open Robotics naming scheme, starting with v1.14:
+Given [the recent changes](https://discourse.openrobotics.org/t/a-new-era-for-gazebo-cross-post/25012) by the Open Robotics simulation team, we are introducing name changes for our gazebo simulations, mirroring Open Robotics naming scheme, starting with v1.14:
 
-- [Ignition Gazebo](https://docs.px4.io/v1.13/en/simulation/ignition_gazebo.html) to [Gazebo](../sim_gazebo_gz/index.md)
-- [Gazebo](https://docs.px4.io/v1.13/en/simulation/gazebo.html) to [Gazebo Classic](../sim_gazebo_classic/index.md).
+- [Ignition Gazebo](https://docs.px4.io/v1.13/en/simulation/ignition_gazebo) to [Gazebo](../sim_gazebo_gz/index.md)
+- [Gazebo](https://docs.px4.io/v1.13/en/simulation/gazebo) to [Gazebo Classic](../sim_gazebo_classic/index.md).
 
 Most importantly this affects the PX4 build target names as well:
 
@@ -63,7 +63,7 @@ Most importantly this affects the PX4 build target names as well:
 
 ### Improved ROS 2 Interface via uXRCE-DDS
 
-We updated the ROS 2 interface, replacing [Fast-RTPS](https://docs.px4.io/v1.13/en/middleware/micrortps.html) with [uXRCE-DDS](../ros2/user_guide.md), resulting in an improved experience across the board.
+We updated the ROS 2 interface, replacing [Fast-RTPS](https://docs.px4.io/v1.13/en/middleware/micrortps) with [uXRCE-DDS](../ros2/user_guide.md), resulting in an improved experience across the board.
 The change also avoids the need for `_rtps` build targets, enabling the interface on even more targets by default.
 
 ## Upgrade Guide
diff --git a/docs/en/releases/1.17.md b/docs/en/releases/1.17.md
index 67728cca98..2115e92400 100644
--- a/docs/en/releases/1.17.md
+++ b/docs/en/releases/1.17.md
@@ -9,7 +9,7 @@ const { site } = useData();
 
 <div v-if="site.title !== 'PX4 Guide (main)'">
   <div class="custom-block danger">
-    <p class="custom-block-title">This page is on a release branch, and hence probably out of date. <a href="https://docs.px4.io/main/en/releases/main.html">See the latest version</a>.</p>
+    <p class="custom-block-title">This page is on a release branch, and hence probably out of date. <a href="https://docs.px4.io/main/en/releases/main">See the latest version</a>.</p>
   </div>
 </div>
 
@@ -57,7 +57,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide).
 
 -->
 
-- <Badge type="warning" text="Experimental" /> [MC Neural Network Module](../advanced/neural_networkss.md)
+- <Badge type="warning" text="Experimental" /> [MC Neural Network Module](../advanced/neural_networks.md)
 
 ### Estimation
 
diff --git a/docs/en/releases/main.md b/docs/en/releases/main.md
index ebb63ce36a..8e06078324 100644
--- a/docs/en/releases/main.md
+++ b/docs/en/releases/main.md
@@ -9,7 +9,7 @@ const { site } = useData();
 
 <div v-if="site.title !== 'PX4 Guide (main)'">
   <div class="custom-block danger">
-    <p class="custom-block-title">This page is on a release branch, and hence probably out of date. <a href="https://docs.px4.io/main/en/releases/main.html">See the latest version</a>.</p>
+    <p class="custom-block-title">This page is on a release branch, and hence probably out of date. <a href="https://docs.px4.io/main/en/releases/main">See the latest version</a>.</p>
   </div>
 </div>
 
diff --git a/docs/en/releases/release_process.md b/docs/en/releases/release_process.md
index 73745a0cd3..beda62e000 100644
--- a/docs/en/releases/release_process.md
+++ b/docs/en/releases/release_process.md
@@ -195,7 +195,7 @@ The release vote takes place during the [Weekly Community Q&A Call](../contribut
 - Present the release status and test results
 - **Vote 1:** Core maintainers vote on whether to publish the release
 - **Vote 2:** Decide the name/number of the next release version
-- The call happens Wednesdays at 17:00 CET on [Discord](https://discord.gg/BDYmr6FA6Q)
+- The call happens Wednesdays at 17:00 CET on [Discord](https://discord.com/invite/BDYmr6FA6Q)
 
 ### 8. Create and Push Release Tag
 
@@ -254,7 +254,7 @@ Review and finalize the release notes that have been developed throughout the re
 Announce the release through official channels:
 
 - [PX4 Discuss Forum](https://discuss.px4.io/)
-- [PX4 Discord](https://discord.gg/dronecode)
+- [PX4 Discord](https://discord.com/invite/dronecode)
 - Social media (Twitter/X, LinkedIn)
 - Dronecode newsletter
 
diff --git a/docs/en/robotics/index.md b/docs/en/robotics/index.md
index 049df149a1..04f0e1a113 100644
--- a/docs/en/robotics/index.md
+++ b/docs/en/robotics/index.md
@@ -66,7 +66,7 @@ Upgrade to ROS 2 for existing projects as soon as possible.
 
 DroneKit-Python is a MAVLink API written in Python.
 It is not optimised for use with PX4, and has not be maintained for some years.
-Legacy docs for using PX4 and DroneKit can be found here: [PX4 v1.12 > DroneKit](https://docs.px4.io/v1.12/en/robotics/dronekit.html).
+Legacy docs for using PX4 and DroneKit can be found here: [PX4 v1.12 > DroneKit](https://docs.px4.io/v1.12/en/robotics/dronekit).
 
 ::: tip
 [MAVSDK](https://mavsdk.mavlink.io/) is the recommended MAVLink API for use with PX4.
diff --git a/docs/en/ros2/user_guide.md b/docs/en/ros2/user_guide.md
index 332c9b00dd..a06c6d05c5 100644
--- a/docs/en/ros2/user_guide.md
+++ b/docs/en/ros2/user_guide.md
@@ -9,7 +9,7 @@ From PX4 v1.14, ROS 2 uses [uXRCE-DDS](../middleware/uxrce_dds.md) middleware, r
 
 The [migration guide](../middleware/uxrce_dds.md#fast-rtps-to-uxrce-dds-migration-guidelines) explains what you need to do in order to migrate ROS 2 apps from PX4 v1.13 to PX4 v1.14.
 
-If you're still working on PX4 v1.13, please follow the instructions in the [PX4 v1.13 Docs](https://docs.px4.io/v1.13/en/ros/ros2_comm.html).
+If you're still working on PX4 v1.13, please follow the instructions in the [PX4 v1.13 Docs](https://docs.px4.io/v1.13/en/ros/ros2_comm).
 
 <!-- remove this when there are PX4 v1.14 docs for some months -->
 
diff --git a/docs/en/sensor/px4flow.md b/docs/en/sensor/px4flow.md
index d0d5104758..83edc7f785 100644
--- a/docs/en/sensor/px4flow.md
+++ b/docs/en/sensor/px4flow.md
@@ -5,4 +5,4 @@
 PX4 does not support the PX4Flow [optical flow](../sensor/optical_flow.md) sensor from PX4 v1.13 (it doesn't work with current firmware).
 PX4 may work with older PX4Flow firmware.
 
-Documentation has been removed (if needed, see [Legacy Docs for PX4Flow in v1.13](https://docs.px4.io/v1.13/en/sensor/px4flow.html)).
+Documentation has been removed (if needed, see [Legacy Docs for PX4Flow in v1.13](https://docs.px4.io/v1.13/en/sensor/px4flow)).
diff --git a/docs/en/sensor/vectornav.md b/docs/en/sensor/vectornav.md
index cbe8f7b53a..9e1dae0f2d 100644
--- a/docs/en/sensor/vectornav.md
+++ b/docs/en/sensor/vectornav.md
@@ -42,7 +42,7 @@ This can be changed to any rigid rotation using the VectorNav Reference Frame Ro
 
 If using a GNSS-enabled product, the GNSS antenna must be mounted rigidly with respect to the inertial sensor and with an unobstructed sky view. If using a dual-GNSS-enabled product (VN-3X0), the secondary antenna must be mounted rigidly with respect to the primary antenna and the inertial sensor with an unobstructed sky view.
 
-For more mounting requirements and recommendations, see the relevant [Quick Start Guide](https://www.vectornav.com/resources/quick-start-guides).
+For more mounting requirements and recommendations, see the relevant [Quick Start Guide](https://www.vectornav.com/resources/technical-documentation/quick-start-guides).
 
 ## Firmware Configuration
 
@@ -131,5 +131,5 @@ Published topics can be viewed using the `listener` command.
 
 ## Hardware Specifications
 
-- [Product Briefs](https://www.vectornav.com/resources/product-briefs)
-- [Datasheets](https://www.vectornav.com/resources/datasheets)
+- [Product Briefs](https://www.vectornav.com/resources/product-information/product-briefs)
+- [Datasheets](https://www.vectornav.com/resources/technical-documentation/datasheets)
diff --git a/docs/en/test_and_ci/test_flights.md b/docs/en/test_and_ci/test_flights.md
index 91a7681f97..a120578703 100644
--- a/docs/en/test_and_ci/test_flights.md
+++ b/docs/en/test_and_ci/test_flights.md
@@ -7,7 +7,7 @@ const { site } = useData();
 
 <div v-if="site.title !== 'PX4 Guide (main)'">
   <div class="custom-block danger">
-    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/test_and_ci/test_flights.html">See the latest version</a>.</p>
+    <p class="custom-block-title">This page may be out out of date. <a href="https://docs.px4.io/main/en/test_and_ci/test_flights">See the latest version</a>.</p>
   </div>
 </div>