Fix all possible HTTP to HTTPS docs links (#25153)

2026-03-24 02:24:09 +08:00 · 2025-07-03 18:09:58 +10:00
parent 375f421c61
commit 2c31e2bad5
84 changed files with 276 additions and 359 deletions
--- a/docs/en/SUMMARY.md
+++ b/docs/en/SUMMARY.md
@@ -162,7 +162,6 @@
      - [ARK Electronics ARKV6X](flight_controller/ark_v6x.md)
      - [ARK FPV Flight Controller](flight_controller/ark_fpv.md)
      - [ARK Pi6X Flow Flight Controller](flight_controller/ark_pi6x.md)
-      - [CUAV X7](flight_controller/cuav_x7.md)
      - [CUAV Nora](flight_controller/cuav_nora.md)
      - [CUAV V5+ (FMUv5)](flight_controller/cuav_v5_plus.md)
        - [Wiring Quickstart](assembly/quick_start_cuav_v5_plus.md)
@@ -183,8 +182,7 @@
      - [ModalAI Flight Core v1](flight_controller/modalai_fc_v1.md)
      - [ModalAI VOXL Flight](flight_controller/modalai_voxl_flight.md)
      - [ModalAI VOXL 2](flight_controller/modalai_voxl_2.md)
-      - [mRobotics-X2.1 (FMUv2)](flight_controller/mro_x2.1.md)
-      - [mRo Control Zero F7)](flight_controller/mro_control_zero_f7.md)
+      - [mRo Control Zero F7](flight_controller/mro_control_zero_f7.md)
      - [Sky-Drones AIRLink](flight_controller/airlink.md)
      - [SPRacing SPRacingH7EXTREME](flight_controller/spracingh7extreme.md)
      - [ThePeach FCC-K1](flight_controller/thepeach_k1.md)
@@ -201,11 +199,13 @@
      - [BetaFPV Beta75X 2S Brushless Whoop](complete_vehicles_mc/betafpv_beta75x.md)
      - [Bitcraze Crazyflie 2.0 ](complete_vehicles_mc/crazyflie2.md)
      - [Aerotenna OcPoC-Zynq Mini](flight_controller/ocpoc_zynq.md)
+      - [CUAV X7](flight_controller/cuav_x7.md)
      - [CUAV v5](flight_controller/cuav_v5.md)
      - [CUAV Pixhack v3 (FMUv3)](flight_controller/pixhack_v3.md)
      - [Holybro Kakute F7](flight_controller/kakutef7.md)
      - [Holybro Pixfalcon](flight_controller/pixfalcon.md)
      - [Holybro pix32 (FMUv2)](flight_controller/holybro_pix32.md)
+      - [mRo X2.1 (FMUv2)](flight_controller/mro_x2.1.md)
      - [mRo AUAV-X2](flight_controller/auav_x2.md)
      - [NXP RDDRONE-FMUK66 FMU](flight_controller/nxp_rddrone_fmuk66.md)
      - [3DR Pixhawk 1](flight_controller/pixhawk.md)
--- a/docs/en/advanced/realsense_intel_driver.md
+++ b/docs/en/advanced/realsense_intel_driver.md
@@ -41,7 +41,7 @@ The tutorial is ordered in the following way: In a first part it is shown how to

 ## Installing ROS Indigo

- Follow instructions given at [ROS indigo installation guide](http://wiki.ros.org/indigo/Installation/Ubuntu):
+- Follow instructions given at [ROS indigo installation guide](https://wiki.ros.org/indigo/Installation/Ubuntu):
  - Install Desktop-Full version.
  - Execute steps described in the sections "Initialize rosdep" and "Environment setup".

@@ -54,7 +54,6 @@ The tutorial is ordered in the following way: In a first part it is shown how to
  ```

 - Download and install the driver:
-
  - Clone [RealSense_ROS repository](https://github.com/bestmodule/RealSense_ROS):

    ```sh
@@ -62,7 +61,6 @@ The tutorial is ordered in the following way: In a first part it is shown how to
    ```

 - Follow instructions given in [here](https://github.com/bestmodule/RealSense_ROS/tree/master/r200_install).
-
  - Press the enter button when the questions whether to install the following installation packages show up:

    ```sh
@@ -86,11 +84,9 @@ The tutorial is ordered in the following way: In a first part it is shown how to
 - After the installation has completed, reboot the Virtual Machine.

 - Test camera driver:
-
  - Connect the Intel RealSense camera head with the computer with a USB3 cable that is plugged into a USB3 receptacle on the computer.
  - Click on Devices->USB-> Intel Corp Intel RealSense 3D Camera R200 in the menu bar of the Virtual Box, in order to forward the camera USB connection to the Virtual Machine.
  - Execute the file [unpacked folder]/Bin/DSReadCameraInfo:
-
    - If the following error message appears, unplug the camera (physically unplug USB cable from the computer). Plug it in again + Click on Devices->USB-> Intel Corp Intel RealSense 3D Camera R200 in the menu bar of the Virtual Box again and execute again the file [unpacked folder]/Bin/DSReadCameraInfo.

      ```sh
--- a/docs/en/advanced/system_tunes.md
+++ b/docs/en/advanced/system_tunes.md
@@ -25,7 +25,7 @@ On Windows, one option is to use _Melody Master_ within _Dosbox_.

 The steps for using the software are:

-1. Download [DosBox](http://www.dosbox.com/) and install the app
+1. Download [DosBox](https://www.dosbox.com/) and install the app
 1. Download [Melody Master](ftp://archives.thebbs.org/ansi_utilities/melody21.zip) and unzip into a new directory
 1. Open the _Dosbox_ console
 1. Mount the melody master directory in Dosbox as shown below:
--- a/docs/en/advanced_config/bootloader_update.md
+++ b/docs/en/advanced_config/bootloader_update.md
@@ -109,7 +109,7 @@ The following steps explain how you can "manually" update the bootloader using a
   Bootloaders from [PX4/PX4-Bootloader](https://github.com/PX4/PX4-Bootloader) are named with the pattern `*_bl.elf`.
   :::

-4. The _gdb terminal_ appears and it should display the following output:
+4. The _gdb terminal_ appears and it should display (something like) the following output:

   ```sh
   GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
@@ -121,9 +121,9 @@ The following steps explain how you can "manually" update the bootloader using a
   This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
   Type "show configuration" for configuration details.
   For bug reporting instructions, please see:
-   <http://www.gnu.org/software/gdb/bugs/>.
+   <https://www.sourceware.org/gdb/bugs/>.
   Find the GDB manual and other documentation resources online at:
-   <http://www.gnu.org/software/gdb/documentation/>.
+   <https://www.sourceware.org/gdb/documentation/>.
   For help, type "help".
   Type "apropos word" to search for commands related to "word"...
   Reading symbols from px4fmuv5_bl.elf...done.
--- a/docs/en/assembly/vibration_isolation.md
+++ b/docs/en/assembly/vibration_isolation.md
@@ -31,5 +31,5 @@ A few of simple steps that may reduce vibrations are:

 Some references that you may find useful are:

- [An Introduction to Shock & Vibration Response Spectra, Tom Irvine](http://www.vibrationdata.com/tutorials2/srs_intr.pdf) (free paper)
+- [An Introduction to Shock & Vibration Response Spectra, Tom Irvine](https://www.vibrationdata.com/tutorials2/srs_intr.pdf) (free paper)
 - [Structural Dynamics and Vibration in Practice - An Engineering Handbook, Douglas Thorby](https://books.google.ch/books?id=PwzDuWDc8AgC&printsec=frontcover) (preview).
--- a/docs/en/complete_vehicles_mc/index.md
+++ b/docs/en/complete_vehicles_mc/index.md
@@ -19,12 +19,12 @@ They may come either fully assembled or in parts.

 This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed.

- [Teal One](https://tealdrones.com/teal-one/)
 - [ModalAI Starling](../complete_vehicles_mc/modalai_starling.md)
 - [ModalAI Sentinel](https://www.modalai.com/sentinel)
 - [MindRacer 210](../complete_vehicles_mc/mindracer210.md)
 - [NanoMind 110](../complete_vehicles_mc/nanomind110.md)
 - [Amovlab F410](../complete_vehicles_mc/amov_F410_drone.md)
+- [Teal One](https://px4.io/project/teal-one/) ([superseded](https://tealdrones.com/solutions/teal-2/))

 ## PX4 Compatible

--- a/docs/en/complete_vehicles_mc/px4_vision_kit.md
+++ b/docs/en/complete_vehicles_mc/px4_vision_kit.md
@@ -8,7 +8,6 @@ The kit contains a near-ready-to-fly carbon-fibre quadcopter equipped with a _Pi

 The guide explains the minimal additional setup required to get the vehicle ready to fly (installing an RC system and battery). It also covers the first flight, and how to get started with modifying the computer vision code.

-
 :::warning
 PX4 no longer supports the avoidance software described in this document:

@@ -16,7 +15,7 @@ PX4 no longer supports the avoidance software described in this document:
 - [Path Planning Interface](../computer_vision/path_planning_interface.md), along with obstacle avoidance in missions, and safe landing.

 A USB stick is included in the kit with an example of an obstacle avoidance feature implementation based on this software.
-This example is intended as a reference only and serves to demonstrate the capabilities of the platform. 
+This example is intended as a reference only and serves to demonstrate the capabilities of the platform.
 :::

 ::: tip
@@ -73,7 +72,6 @@ What's inside the PX4 Vision V1 can be found here in the [PX4 v1.13 Docs here](h
 The PX4 Vision DevKit contains following components:

 - Core Components:
-
  - 1x Pixhawk 4 or Pixhawk 6C (for v1.5) flight controller
  - 1x PMW3901 optical flow sensor
  - 1x TOF Infrared distance sensor (PSK‐CM8JL65‐CC5)
@@ -94,7 +92,6 @@ The PX4 Vision DevKit contains following components:
    - WiFi 802.11 b/g/n @ 2.4 GHz (attached to external antenna #1). Allows computer to access home WiFi network for Internet access/updates.

 - Mechanical Specification:
-
  - Frame: Full 5mm 3k carbon fiber twill
  - Motors: T-MOTOR KV1750
  - ESC: BEHEli-S 20A ESC
@@ -105,7 +102,6 @@ The PX4 Vision DevKit contains following components:
  - Telemetry: ESP8266 connected to flight controller (attached to external antenna #2). Enables wireless connection to the ground station.

 - A USB2.0 stick with pre-flashed software that bundles:
-
  - Ubuntu 18.04 LTS
  - ROS Melodic
  - Occipital Structure Core ROS driver
@@ -133,7 +129,6 @@ In addition, users will need ground station hardware/software:
 ## First-time Setup

 1. Attach a [compatible RC receiver](../getting_started/rc_transmitter_receiver.md#connecting-receivers) to the vehicle (not supplied with kit):
-
   - Remove/unscrew the top plate (where the battery goes) using an H2.0 hex key tool.
   - [Connect the receiver to the flight controller](../assembly/quick_start_pixhawk4.md#radio-control).
   - Re-attach the top plate.
@@ -155,7 +150,6 @@ In addition, users will need ground station hardware/software:
   Ensure propellers are removed before connecting the battery.
   :::
 1. Connect the ground station to the vehicle WiFi network (after a few seconds) using the following default credentials:
-
   - **SSID:** pixhawk4
   - **Password:** pixhawk4

@@ -171,7 +165,6 @@ In addition, users will need ground station hardware/software:
   The vehicle should arrive pre-calibrated (e.g. with firmware, airframe, battery, and sensors all setup).
   You will however need to calibrate the radio system (that you just connected) and it is often worth re-doing the compass calibration.
   :::
-
   - [Calibrate the Radio System](../config/radio.md)
   - [Calibrate the Compass](../config/compass.md)

@@ -182,7 +175,6 @@ In addition, users will need ground station hardware/software:
   :::

   We recommend RC controller switches are define for:
-
   - [Position Mode](../flight_modes_mc/position.md) - a safe manual flight mode that can be used to test collision prevention.
   - [Mission Mode](../flight_modes_mc/mission.md) - run missions and test obstacle avoidance.
   - [Return Mode](../flight_modes_mc/return.md) - return vehicle safely to its launch point and land.
@@ -190,7 +182,6 @@ In addition, users will need ground station hardware/software:
 1. Attach the propellers with the rotations as shown:

   ![Motor Order Diagram](../../assets/hardware/px4_vision_devkit/motor_order_diagram.png)
-
   - The propellers directions can be determined from the labels: _6045_ (normal, counter-clockwise) and _6045_**R** (reversed, clockwise).

     ![Propeller identification](../../assets/hardware/px4_vision_devkit/propeller_directions.jpg)
@@ -212,7 +203,6 @@ When the vehicle setup described above is complete:
   :::

 1. Check that the avoidance system has started properly:
-
   - The _QGroundControl_ notification log displays the message: **Avoidance system connected**.

     ![QGC Log showing avoidance system has started](../../assets/hardware/px4_vision_devkit/qgc_console_vision_system_started.jpg)
@@ -309,7 +299,6 @@ To login to the companion computer:
 1. Connect a keyboard and mouse to the _UP Core_ via port `USB2`:

   ![UP Core: USB2](../../assets/hardware/px4_vision_devkit/upcore_port_usb2.png)
-
   - Use the USB-JST cable from the kit to get a USB A connector

     ![USB to JST cable](../../assets/hardware/px4_vision_devkit/usb_jst_cable.jpg)
@@ -323,7 +312,6 @@ To login to the companion computer:
   The Ubuntu login screen should then appear on the monitor.

 1. Login to the _UP Core_ using the credentials:
-
   - **Username:** px4vision
   - **Password:** px4vision

@@ -375,7 +363,7 @@ To integrate a different planner, this needs to be disabled.
   ```

 The ROS workspace is placed in `~/catkin_ws`.
-For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](http://wiki.ros.org/catkin/Tutorials).
+For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](https://wiki.ros.org/catkin/Tutorials).

 ### Developing PX4 Firmware

@@ -385,7 +373,6 @@ You can modify PX4 itself, and [install it as custom firmware](../config/firmwar
 - Select the _PX4 Vision DevKit_ airframe after loading new firmware:
  ![Airframe Selection - PX4 Vision DevKit](../../assets/hardware/px4_vision_devkit/qgc_airframe_px4_vision_devkit_platform.jpg)

-
 ## PX4 Vision Carrier Board Pinouts

 Information for the PX4 Vision 1.15 can be found at [https://docs.holybro.com](https://docs.holybro.com/drone-development-kit/px4-vision-dev-kit-v1.5).
--- a/docs/en/computer_vision/visual_inertial_odometry.md
+++ b/docs/en/computer_vision/visual_inertial_odometry.md
@@ -42,9 +42,7 @@ To setup ROS and PX4:

 - [Verify that VIO is set up correctly](#verify_estimate) before your first flight!

-<a id="vio_ros_node"></a>
-
-### ROS VIO node
+### ROS VIO node {#vio_ros_node}

 In this suggested setup, a ROS node is required to

@@ -54,17 +52,16 @@ In this suggested setup, a ROS node is required to

 The implementation of the ROS node will be specific to the camera used and will need to be developed to use the interface and drivers appropriate for the camera.

-The odometry messages should be of the type [`nav_msgs/Odometry`](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html) and published to the topic `/mavros/odometry/out`.
+The odometry messages should be of the type [`nav_msgs/Odometry`](https://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html) and published to the topic `/mavros/odometry/out`.

-System status messages of the type [`mavros_msgs/CompanionProcessStatus`](https://github.com/mavlink/mavros/blob/master/mavros_msgs/msg/CompanionProcessStatus.msg) should be published to the topic `/mavros/companion_process/status`. These should identify the component as `MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY` (197) and indicate the `state` of the system. Recommended status values are:
+System status messages of the type [`mavros_msgs/CompanionProcessStatus`](https://github.com/mavlink/mavros/blob/master/mavros_msgs/msg/CompanionProcessStatus.msg) should be published to the topic `/mavros/companion_process/status`.
+These should identify the component as `MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY` (197) and indicate the `state` of the system. Recommended status values are:

 - `MAV_STATE_ACTIVE` when the VIO system is functioning as expected,
 - `MAV_STATE_CRITICAL` when the VIO system is functioning, but with low confidence, and
 - `MAV_STATE_FLIGHT_TERMINATION` when the system has failed or the estimate confidence is unacceptably low.

-<a id="ekf2_tuning"></a>
-
-### PX4 Tuning
+### PX4 Tuning {#ekf2_tuning}

 The following parameters must be set to use external position information with EKF2.

@@ -79,9 +76,7 @@ These can be set in _QGroundControl_ > **Vehicle Setup > Parameters > EKF2** (re

 For more detailed/additional information, see: [Using PX4's Navigation Filter (EKF2) > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system).

-<a id="tuning-EKF2_EV_DELAY"></a>
-
-#### Tuning EKF2_EV_DELAY
+#### Tuning EKF2_EV_DELAY {#tuning-EKF2_EV_DELAY}

 [EKF2_EV_DELAY](../advanced_config/parameter_reference.md#EKF2_EV_DELAY) is the _Vision Position Estimator delay relative to IMU measurements_.
 In other words, it is the difference between the vision system timestamp and the "actual" capture time that would have been recorded by the IMU clock (the "base clock" for EKF2).
@@ -100,9 +95,7 @@ A plot of external data vs. onboard estimate (as above) can be generated using [

 The value can further be tuned by varying the parameter to find the value that yields the lowest EKF innovations during dynamic maneuvers.

-<a id="verify_estimate"></a>
-
-## Check/Verify VIO Estimate
+## Check/Verify VIO Estimate {#verify_estimate}

 ::: info
 The [MAV_ODOM_LP](../advanced_config/parameter_reference.md#MAV_ODOM_LP) parameter mentioned below was removed in PX4 v1.14.
@@ -147,11 +140,9 @@ First, make sure MAVROS is able to connect successfully to the flight controller
 If it is connecting properly common problems/solutions are:

 - **Problem:** I get drift / flyaways when the drone flies, but not when I carry it around with the props off.
-
  - If using the [T265](../peripherals/camera_t265_vio.md) try soft-mounting it (this camera is very sensitive to high-frequency vibrations).

 - **Problem:** I get toilet-bowling when VIO is enabled.
-
  - Make sure the orientation of the camera matches the transform in the launch file.
    Use the _QGroundControl_ [MAVLink Inspector](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_inspector.html) to verify that the velocities in the `ODOMETRY` message coming from MAVROS are aligned to the FRD coordinate system.

--- a/docs/en/concept/control_allocation.md
+++ b/docs/en/concept/control_allocation.md
@@ -42,7 +42,7 @@ Notes:
  - publishes the servo trims separately so they can be added as an offset when [testing actuators](../config/actuators.md#actuator-testing) (using the test sliders).
 - the output drivers:
  - handle the hardware initialization and update
-  - use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module/).
+  - use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module).
    The driver defines a parameter prefix, e.g. `PWM_MAIN` that the library then uses for configuration.
    Its main task is to select from the input topics and assign the right data to the outputs based on the user set `<param_prefix>_FUNCx` parameter values.
    For example if `PWM_MAIN_FUNC3` is set to **Motor 2**, the 3rd output is set to the 2nd motor from `actuator_motors`.
--- a/docs/en/concept/system_startup.md
+++ b/docs/en/concept/system_startup.md
@@ -31,7 +31,7 @@ For that to work, a few things are required:
  For that the `bin` directory with the symbolic links is added to the `PATH` variable right before executing the startup scripts.
 - The shell starts each module as a new (client) process.
  Each client process needs to communicate with the main instance of px4 (the server), where the actual modules are running as threads.
-  This is done through a [UNIX socket](http://man7.org/linux/man-pages/man7/unix.7.html).
+  This is done through a [UNIX socket](https://man7.org/linux/man-pages/man7/unix.7.html).
  The server listens on a socket, to which clients can connect and send a command.
  The server then sends the output and return code back to the client.
 - The startup scripts call the module directly, e.g. `commander start`, rather than using the `px4-` prefix.
--- a/docs/en/config/joystick.md
+++ b/docs/en/config/joystick.md
@@ -12,7 +12,7 @@ Joysticks are also commonly used to allow developers to fly the vehicle in simul
 :::

 ::: info
-_QGroundControl_ uses the cross-platform [SDL2](http://www.libsdl.org/index.php) library to convert joystick movements to MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages, which are then sent to PX4 over the telemetry channel.
+_QGroundControl_ uses the cross-platform [SDL2](https://www.libsdl.org/index.php) library to convert joystick movements to MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages, which are then sent to PX4 over the telemetry channel.
 In consequence, a joystick-based controller system requires a reliable high bandwidth telemetry channel to ensure that the vehicle is responsive to joystick movements.
 :::

--- a/docs/en/contribute/code.md
+++ b/docs/en/contribute/code.md
@@ -112,7 +112,7 @@ Currently we have two types of source-based documentation:
  - Do not add documentation that can trivially be inferred from C++ entity names.
  - ALWAYS specify units of variables, constants, and input/return parameters where they are defined.
  - Commonly you may want to add information about corner cases and error handling.
-  - [Doxgyen](http://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
+  - [Doxgyen](https://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
    A good example of usage is [src/modules/events/send_event.h](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/events/send_event.h).

 Please avoid "magic numbers", for example, where does this number in the conditional come from? What about the multiplier on yaw stick input?
--- a/docs/en/debug/eclipse_jlink.md
+++ b/docs/en/debug/eclipse_jlink.md
@@ -46,7 +46,6 @@ For more information, see: [https://gnu-mcu-eclipse.github.io/debug/jlink/instal
   Set it as shown in the screenshot below.
   ![Eclipse: Segger J-Link Path](../../assets/debug/eclipse_segger_jlink_path.png)
 1. Update packs:
-
   - Click the small icon on the top right called _Open Perspective_ and open the _Packs_ perspective.
     ![Eclipse: Workspace](../../assets/debug/eclipse_workspace_perspective.png)
   - Click the **update all** button.
@@ -61,7 +60,6 @@ For more information, see: [https://gnu-mcu-eclipse.github.io/debug/jlink/instal
   - The STM32Fxx devices are found in the Keil folder, install by right-clicking and then selecting **install** on the according device for F4 and F7.

 1. Setup debug configuration for target:
-
   - Right click project and open the _Settings_ (menu: **C/C++ Build > Settings**)
   - Choose the _Devices_ Tab, _Devices_ section (Not _Boards_).
   - Find the FMU chip you wish to debug.
@@ -73,7 +71,6 @@ For more information, see: [https://gnu-mcu-eclipse.github.io/debug/jlink/instal
 1. Then select _GDB SEGGER J-Link Debugging_ and then the **New config** button on the top left.
   ![Eclipse: GDB Segger Debug config](../../assets/debug/eclipse_settings_debug_config_gdb_segger.png)
 1. Setup build config:
-
   - Give it a name and set the _C/C++ Application_ to the corresponding **.elf** file.
   - Choose _Disable Auto build_

@@ -96,7 +93,6 @@ This is quite useful since PX4 tends to run many different tasks.
 To enable this feature for use in Eclipse:

 1. You first need to enable `CONFIG_DEBUG_TCBINFO` in the NuttX configuration for your build (to expose the TCB offsets).
-
   - Open a terminal in the root of your PX4-Autopilot source code
   - In the terminal, open `menuconfig` using the appropriate make target for the build.
     This will be something like:
@@ -136,7 +132,7 @@ Adding missing SVD files for the _Peripheral View_:

   ![Eclipse: MCU Packages](../../assets/debug/eclipse_mcu_packages.png)

-2. Download missing packages from: http://www.keil.com/dd2/Pack/
+2. Download missing packages from: https://www.keil.arm.com/devices/
 3. Open downloaded pack with a decompression tool, and extract the **.SVD** files from: **/CMSIS/SVD**.
 4. Select desired **.SVD** file in: **Debug Options > GDB SEGGER JLink Debugging > SVD Path**

--- a/docs/en/debug/profiling.md
+++ b/docs/en/debug/profiling.md
@@ -9,7 +9,7 @@ PMSP is a shell script that operates by interrupting execution of the firmware p
 Sampled stack traces are appended into a text file.
 Once sampling is finished (which normally takes about an hour or more), the collected stack traces are _folded_.
 The result of _folding_ is another text file that contains the same stack traces, except that all similar stack traces (i.e. those that were obtained at the same point in the program) are joined together, and the number of their occurrences is recorded.
-The folded stacks are then fed into the visualization script, for which purpose we employ [FlameGraph - an open source stack trace visualizer](http://www.brendangregg.com/flamegraphs.html).
+The folded stacks are then fed into the visualization script, for which purpose we employ [FlameGraph - an open source stack trace visualizer](https://www.brendangregg.com/flamegraphs.html).

 ## Basic Usage

--- a/docs/en/debug/system_console.md
+++ b/docs/en/debug/system_console.md
@@ -72,7 +72,7 @@ screen /dev/ttyXXX BAUDRATE 8N1

 ### Windows: PuTTY

-Download [PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) and start it.
+Download [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) and start it.

 Then select 'serial connection' and set the port parameters to:

--- a/docs/en/dev_log/logging.md
+++ b/docs/en/dev_log/logging.md
@@ -28,7 +28,7 @@ logger help

 ## Configuration

-The logging system is configured by default to collect sensible logs for [flight reporting](../getting_started/flight_reporting.md) with [Flight Review](http://logs.px4.io).
+The logging system is configured by default to collect sensible logs for [flight reporting](../getting_started/flight_reporting.md) with [Flight Review](https://logs.px4.io/).

 Logging may further be configured using the [SD Logging](../advanced_config/parameter_reference.md#sd-logging) parameters.
 The parameters you are most likely to change are listed below.
@@ -185,7 +185,6 @@ There are different clients that support ulog streaming:
  Also make sure `txerr` stays at 0.
  If this goes up, either the NuttX sending buffer is too small, the physical link is saturated or the hardware is too slow to handle the data.

-
 ## See Also

 - [Encrypted logging](../dev_log/log_encryption.md)
--- a/docs/en/dronecan/cuav_can_pmu.md
+++ b/docs/en/dronecan/cuav_can_pmu.md
@@ -71,4 +71,4 @@ Set the following parameters in _QGroundControl_ [Vehicle Setup > Parameters](..

 [CAN PMU Manual](http://manual.cuav.net/power-module/CAN-PMU.pdf)

-[CAN PMU Power detection module > Enable CAN PMU > PX4 firmware](http://doc.cuav.net/power-module/can-pmu/en/) (CUAV docs)
+[CAN PMU Power detection module > Enable CAN PMU > PX4 firmware](https://doc.cuav.net/power-module/can-pmu/en/) (CUAV docs)
--- a/docs/en/dronecan/development.md
+++ b/docs/en/dronecan/development.md
@@ -8,6 +8,6 @@ Additional documentation on how to use Babel/other SLCAN adapters, the DroneCAN

 ## Debugging with Zubax Babel

-A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://zubax.com/products/babel) in combination with the [GUI tool](http://dronecan.github.io/GUI_Tool/Overview/).
+A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://zubax.com/products/babel) in combination with the [GUI tool](https://dronecan.github.io/GUI_Tool/Overview/).

 They can also be used independently from Pixhawk hardware in order to test a node or manually control DroneCAN enabled ESCs.
--- a/docs/en/flight_controller/auav_x2.md
+++ b/docs/en/flight_controller/auav_x2.md
@@ -11,13 +11,13 @@ PX4 does not manufacture this (or any) autopilot.
 Contact the [manufacturer](https://store.mrobotics.io/) for hardware support or compliance issues.
 :::

-The [AUAV<sup>&reg;</sup>](http://www.auav.com/) _AUAV-X2 autopilot_ is based on the [Pixhawk<sup>&reg;</sup>-project](https://pixhawk.org/) **FMUv2** open hardware design. It runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.
+The AUAV-X2 autopilot is based on the [Pixhawk<sup>&reg;</sup>-project](https://pixhawk.org/) **FMUv2** open hardware design. It runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.

 ![AUAVX2_case2](../../assets/flight_controller/auav_x2/auavx2_case2.jpg)

 ## Quick Summary

- Main System-on-Chip: [STM32F427](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: STM32F427VIT6 ARM microcontroller - Revision 3
  - IO: STM32F100C8T6 ARM microcontroller
 - Sensors:
@@ -58,7 +58,7 @@ mRobotics is the distributor for the AUAV Products from August 2017.
 ## Key Links

 - [User Manual](http://arsovtech.com/wp-content/uploads/2015/08/AUAV-X2-user-manual-EN.pdf)
- [DIY Drones Post](http://diydrones.com/profiles/blogs/introducing-the-auav-x2-1-flight-controller)
+- [DIY Drones Post](https://diydrones.com/profiles/blogs/introducing-the-auav-x2-1-flight-controller)

 ## Wiring Guide

--- a/docs/en/flight_controller/autopilot_discontinued.md
+++ b/docs/en/flight_controller/autopilot_discontinued.md
@@ -8,6 +8,7 @@ They are listed because you may be using them in an existing drone, and because

 - [Drotek DroPix](../flight_controller/dropix.md) (FMUv2)
 - [Omnibus F4 SD](../flight_controller/omnibus_f4_sd.md)
+- [CUAV X7](../flight_controller/cuav_x7.md)
 - [CUAV v5](../flight_controller/cuav_v5.md) (Pixhawk FMUv5)
 - [CUAV Pixhack v3](../flight_controller/pixhack_v3.md) (FMUv3)
 - [Aerotenna OcPoC-Zynq Mini](../flight_controller/ocpoc_zynq.md)
@@ -16,6 +17,7 @@ They are listed because you may be using them in an existing drone, and because
 - [Holybro Pixhawk Mini](../flight_controller/pixhawk_mini.md) (FMUv3)
 - [Holybro Pixfalcon](../flight_controller/pixfalcon.md) (Pixhawk FMUv2)
 - [Holybro Pix32](../flight_controller/holybro_pix32.md) (FMUv2)
+- [mRobotics-X2.1](../flight_controller/mro_x2.1.md) (FMUv2)
 - [mRo AUAV-X2](../flight_controller/auav_x2.md) (Pixhawk FMUv2)
 - [NXP FMUK66](../flight_controller/nxp_rddrone_fmuk66.md) (Discontinued)
 - [3DR Pixhawk 1](../flight_controller/pixhawk.md) (Pixhawk FMUv2)
--- a/docs/en/flight_controller/autopilot_manufacturer_supported.md
+++ b/docs/en/flight_controller/autopilot_manufacturer_supported.md
@@ -17,7 +17,6 @@ The boards in this category are:
 - [ARK Electronics ARKV6X](../flight_controller/ark_v6x.md) (and [ARK Electronics Pixhawk Autopilot Bus Carrier](../flight_controller/ark_pab.md))
 - [ARK FPV Flight Controller](../flight_controller/ark_fpv.md)
 - [ARK Pi6X Flow Flight Controller](../flight_controller/ark_pi6x.md)
- [CUAV X7](../flight_controller/cuav_x7.md)
 - [CUAV Nora](../flight_controller/cuav_nora.md)（CUAV X7 variant)
 - [CUAV V5+](../flight_controller/cuav_v5_plus.md) (FMUv5)
 - [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) (FMUv5)
@@ -33,7 +32,6 @@ The boards in this category are:
 - [ModalAI Flight Core v1](../flight_controller/modalai_fc_v1.md)
 - [ModalAI VOXL Flight](../flight_controller/modalai_voxl_flight.md)
 - [ModalAI VOXL 2](../flight_controller/modalai_voxl_2.md)
- [mRobotics-X2.1](../flight_controller/mro_x2.1.md) (FMUv2)
 - [mRo Control Zero](../flight_controller/mro_control_zero_f7.md)
 - [Sky-Drones AIRLink](../flight_controller/airlink.md)
 - [SPRacing SPRacingH7EXTREME](../flight_controller/spracingh7extreme.md)
--- a/docs/en/flight_controller/beaglebone_blue.md
+++ b/docs/en/flight_controller/beaglebone_blue.md
@@ -122,7 +122,7 @@ echo "PermitRootLogin yes" >>  /etc/ssh/sshd_config && systemctl restart sshd

         Download and unpack [gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz](https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder.

-         Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](http://www.linaro.org/downloads/).
+         Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/).

         ```sh
         wget https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz
--- a/docs/en/flight_controller/cuav_nora.md
+++ b/docs/en/flight_controller/cuav_nora.md
@@ -39,7 +39,6 @@ They should be used by preference as they contain the most complete and up to da

 - Main FMU Processor: STM32H743
 - On-board sensors:
-
  - Accelerometer/Gyroscope: ICM-20689
  - Accelerometer/Gyroscope: ICM-20649
  - Accelerometer/Gyroscope: BMI088
@@ -169,5 +168,5 @@ The complete set of supported configurations can be seen in the [Airframes Refer
 ## Further info

 - [Quick start](https://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-nora.html)
- [CUAV docs](http://doc.cuav.net)
+- [CUAV docs](https://doc.cuav.net/)
 - [nora schematic](https://github.com/cuav/hardware/tree/master/X7_Autopilot)
--- a/docs/en/flight_controller/cuav_v5.md
+++ b/docs/en/flight_controller/cuav_v5.md
@@ -1,6 +1,6 @@
 # CUAV v5 (Discontinued)

-<Badge type="info" text="Discontinued" />
+<Badge type="info" text="Discontinued" /> <!-- 202507 / PX4v1.16 -->

 :::warning
 This flight controller has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available.
@@ -25,7 +25,6 @@ It is intended primarily for academic and commercial developers.
 - IO Processor: STM32F100
  - 32 Bit Arm® Cortex®-M3, 24MHz, 8KB SRAM
 - On-board sensors:
-
  - Accelerometer/Gyroscope: ICM-20689
  - Accelerometer/Gyroscope: BMI055
  - Magnetometer: IST8310
@@ -142,5 +141,4 @@ The complete set of supported configurations can be seen in the [Airframes Refer
 ## Further info

 - [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165).
- [CUAV v5 docs](http://doc.cuav.net/flight-controller/v5-autopilot/en/v5.html)
 - [CUAV Github](https://github.com/cuav)
--- a/docs/en/flight_controller/cuav_x7.md
+++ b/docs/en/flight_controller/cuav_x7.md
@@ -1,4 +1,11 @@
-# CUAV X7 Flight Controller
+# CUAV X7 Flight Controller (Discontinued)
+
+<Badge type="info" text="Discontinued" /> <!-- 202507 / PX4v1.16 -->
+
+:::warning
+This flight controller has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available.
+It has been superseded by the [CUAV X7+](https://doc.cuav.net/controller/x7/en/).
+:::

 :::warning
 PX4 does not manufacture this (or any) autopilot.
@@ -40,7 +47,6 @@ They should be used by preference as they contain the most complete and up to da

 - Main FMU Processor: STM32H743
 - On-board sensors:
-
  - Accelerometer/Gyroscope: ICM-20689
  - Accelerometer/Gyroscope: ICM-20649
  - Accelerometer/Gyroscope: BMI088
@@ -81,7 +87,7 @@ When it runs PX4 firmware, only 8 pwm works, the remaining 6 pwm are still being

 ## Connections (Wiring)

-[CUAV X7 Wiring Quickstart](http://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-x7.html)
+[CUAV X7 Wiring Quickstart](https://doc.cuav.net/controller/x7/en/quick-start/quick-start-x7-plus.html)

 ## Size and Pinouts

@@ -173,5 +179,5 @@ The complete set of supported configurations can be seen in the [Airframes Refer
 ## Further info

 - [Quick start](http://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-x7.html)
- [CUAV docs](http://doc.cuav.net)
+- [CUAV docs](https://doc.cuav.net/)
 - [x7 schematic](https://github.com/cuav/hardware/tree/master/X7_Autopilot)
--- a/docs/en/flight_controller/cubepilot_cube_orange.md
+++ b/docs/en/flight_controller/cubepilot_cube_orange.md
@@ -53,7 +53,7 @@ The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopi
  - 400 MHz
  - 1 MB RAM
  - 2 MB Flash \(fully accessible\)
- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor http://www.proficnc.com/all-products/191-pixhawk2-suite.html -->
+- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor -->
  - STM32F103 (32bit _ARM Cortex-M3_)
  - 24 MHz
  - 8 KB SRAM
--- a/docs/en/flight_controller/cubepilot_cube_orangeplus.md
+++ b/docs/en/flight_controller/cubepilot_cube_orangeplus.md
@@ -54,7 +54,7 @@ The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopi
  - 400 MHz
  - 1 MB RAM
  - 2 MB Flash \(fully accessible\)
- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor http://www.proficnc.com/all-products/191-pixhawk2-suite.html -->
+- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor -->
  - STM32F103 (32bit _ARM Cortex-M3_)
  - 24 MHz
  - 8 KB SRAM
--- a/docs/en/flight_controller/cubepilot_cube_yellow.md
+++ b/docs/en/flight_controller/cubepilot_cube_yellow.md
@@ -49,7 +49,7 @@ The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopi
  - 400 MHz
  - 512 KB MB RAM
  - 2 MB Flash
- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor http://www.proficnc.com/all-products/191-pixhawk2-suite.html -->
+- **Failsafe co-processor:** <!-- inconsistent info on failsafe processor: 32 bit STM32F103 failsafe co-processor -->
  - STM32F100 (32bit _ARM Cortex-M3_)
  - 24 MHz
  - 8 KB SRAM
--- a/docs/en/flight_controller/holybro_pix32.md
+++ b/docs/en/flight_controller/holybro_pix32.md
@@ -26,7 +26,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo

 ## Key Features

- Main System-on-Chip: [STM32F427](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: 32-bit STM32F427 Cortex<sup>&reg;</sup> M4 core with FPU
  - RAM: 168 MHz/256 KB
  - Flash: 2 MB
--- a/docs/en/flight_controller/mro_x2.1.md
+++ b/docs/en/flight_controller/mro_x2.1.md
@@ -1,4 +1,10 @@
-# mRo-X2.1 Autopilot
+# mRo-X2.1 Autopilot (Discontinued)
+
+<Badge type="info" text="Discontinued" /> <!-- 202507 / PX4v1.16 -->
+
+:::warning
+This flight controller has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available.
+:::

 :::warning
 PX4 does not manufacture this (or any) autopilot.
@@ -16,7 +22,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo

 ## Quick Summary

- Main System-on-Chip: [STM32F427](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: STM32F427VIT6 ARM<sup>&reg;</sup> microcontroller - Revision 3
  - IO: STM32F100C8T6 ARM<sup>&reg;</sup> microcontroller
 - Sensors:
@@ -29,8 +35,10 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
  - Mounting Points: 30.5mm x 30.5mm 3.2mm diameter
  - Weight: 10.9g

-The diagram below provides a side-by-side comparison with a Pixhawk 1. The mRo features almost identical hardware and connectivity but
-has a much smaller footprint. Major differences are updated sensors and Rev 3 FMU.
+The diagram below provides a side-by-side comparison with a Pixhawk 1.
+The mRo features almost identical hardware and connectivity but
+has a much smaller footprint.
+Major differences are updated sensors and Rev 3 FMU.

 ![Mro Pixhawk 1 vs X2.1 comparison](../../assets/flight_controller/mro/px1_x21.jpg)

--- a/docs/en/flight_controller/omnibus_f4_sd.md
+++ b/docs/en/flight_controller/omnibus_f4_sd.md
@@ -187,9 +187,9 @@ If you use CRSF Telemetry you will need to build custom PX4 firmware.
 By contrast, FrSky telemetry can use prebuilt firmware.
 :::

-For Omnibus we recommend the [TBS Crossfire Nano RX](http://team-blacksheep.com/products/prod:crossfire_nano_rx), since it is specifically designed for small Quads.
+For Omnibus we recommend the [TBS Crossfire Nano RX](https://www.team-blacksheep.com/products/prod:crossfire_nano_rx), since it is specifically designed for small Quads.

-On the handheld controller (e.g. Taranis) you will also need a [Transmitter Module](http://team-blacksheep.com/shop/cat:rc_transmitters#product_listing).
+On the handheld controller (e.g. Taranis) you will also need a [Transmitter Module](https://www.team-blacksheep.com/shop/cat:tbs-crossfire-radio-transmitter#product_listing).
 This can be plugged into the back of the RC controller.

 ::: info
@@ -213,13 +213,9 @@ Instructions for this are provided in the [TBS Crossfire Manual](https://www.tea
 You will need to build custom firmware to use CRSF.
 For more information see [CRSF Telemetry](../telemetry/crsf_telemetry.md#px4-configuration).

-## Schematics
+<!-- no longer available 202507 -->

-The schematics are provided by [Airbot](https://myairbot.com/): [OmnibusF4-Pro-Sch.pdf](http://bit.ly/obf4pro).
-
-<a id="bootloader"></a>
-
-## PX4 Bootloader Update
+## PX4 Bootloader Update {#bootloader}

 The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
 Before PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
--- a/docs/en/flight_controller/pixfalcon.md
+++ b/docs/en/flight_controller/pixfalcon.md
@@ -17,7 +17,7 @@ The Pixfalcon autopilot (designed by [Holybro<sup>&reg;</sup>](https://holybro.c

 ## Quick Summary

- Main System-on-Chip: [STM32F427](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: 180 MHz ARM<sup>&reg;</sup> Cortex<sup>&reg;</sup> M4 with single-precision FPU
  - RAM: 256 KB SRAM (L1)
 - Failsafe System-on-Chip: STM32F100
--- a/docs/en/flight_controller/pixhawk-2.md
+++ b/docs/en/flight_controller/pixhawk-2.md
@@ -51,7 +51,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md

 ## Where to Buy

-[Cube Black](http://www.proficnc.com/61-system-kits) (ProfiCNC)
+[Cube Black](https://www.cubepilot.com/#/reseller/list) (Reseller list)

 ## Assembly

--- a/docs/en/flight_controller/pixhawk.md
+++ b/docs/en/flight_controller/pixhawk.md
@@ -19,7 +19,7 @@ Assembly/setup instructions for use with PX4 are provided here: [Pixhawk Wiring

 ## Key Features

- Main System-on-Chip: [STM32F427](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: 180 MHz ARM<sup>&reg;</sup> Cortex<sup>&reg;</sup> M4 with single-precision FPU
  - RAM: 256 KB SRAM (L1)
 - Failsafe System-on-Chip: STM32F100
@@ -323,10 +323,10 @@ make px4_fmu-v2_default

 ## Parts / Housings

- **ARM MINI JTAG (J6)**: 1.27 mm 10pos header (SHROUDED), for Black Magic Probe: FCI 20021521-00010D4LF ([Distrelec](https://www.distrelec.ch/en/minitek-127-straight-male-pcb-header-surface-mount-rows-10-contacts-27mm-pitch-amphenol-fci-20021521-00010d4lf/p/14352308), [Digi-Key](https://www.digikey.com/en/products/detail/20021521-00010T1LF/609-4054-ND/2414951),) or Samtec FTSH-105-01-F-DV-K (untested) or Harwin M50-3600542 ([Digikey](https://www.digikey.com/en/products/detail/harwin-inc/M50-3600542/2264370) or [Mouser](http://ch.mouser.com/ProductDetail/Harwin/M50-3600542/?qs=%2fha2pyFadujTt%2fIEz8xdzrYzHAVUnbxh8Ki%252bwWYPNeEa09PYvTkIOQ%3d%3d))
+- **ARM MINI JTAG (J6)**: 1.27 mm 10pos header (SHROUDED), for Black Magic Probe: FCI 20021521-00010D4LF ([Distrelec](https://www.distrelec.ch/en/minitek-127-straight-male-pcb-header-surface-mount-rows-10-contacts-27mm-pitch-amphenol-fci-20021521-00010d4lf/p/14352308), [Digi-Key](https://www.digikey.com/en/products/detail/20021521-00010T1LF/609-4054-ND/2414951),) or Samtec FTSH-105-01-F-DV-K (untested) or Harwin M50-3600542 ([Digikey](https://www.digikey.com/en/products/detail/harwin-inc/M50-3600542/2264370))
  - JTAG Adapter Option #1: [BlackMagic Probe](https://1bitsquared.com/products/black-magic-probe). Note, may come without cables (check with manufacturer).
-    If so, you will need the **Samtec FFSD-05-D-06.00-01-N** cable ([Samtec sample service](https://www.samtec.com/products/ffsd-05-d-06.00-01-n) or [Digi-Key Link: SAM8218-ND](http://www.digikey.com/product-search/en?x=0&y=0&lang=en&site=us&KeyWords=FFSD-05-D-06.00-01-N)) or [Tag Connect Ribbon](http://www.tag-connect.com/CORTEXRIBBON10) and a Mini-USB cable.
-  - JTAG Adapter Option #2: [Digi-Key Link: ST-LINK/V2](https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND) / [ST USER MANUAL](http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/USER_MANUAL/DM00026748.pdf), needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
+    If so, you will need the **Samtec FFSD-05-D-06.00-01-N** cable ([Samtec sample service](https://www.samtec.com/products/ffsd-05-d-06.00-01-n) or [Digi-Key Link: SAM8218-ND](https://www.digikey.com/en/products/detail/samtec-inc/ffsd-05-d-06-00-01-n/1106577)) or [Tag Connect Ribbon](https://www.tag-connect.com/product/10-pin-cortex-ribbon-cable-4-length-with-50-mil-connectors) and a Mini-USB cable.
+  - JTAG Adapter Option #2: [Digi-Key Link: ST-LINK/V2](https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND) / [ST USER MANUAL](https://www.st.com/resource/en/user_manual/dm00026748.pdf), needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
  - JTAG Adapter Option #3: [Olimex ARM-TINY](https://www.olimex.com/wiki/ARM-USB-TINY) or any other OpenOCD-compatible ARM Cortex JTAG adapter, needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
 - **USARTs**: Hirose DF13 6 pos ([Digi-Key Link: DF13A-6P-1.25H(20)](https://www.digikey.com/products/en?keywords=H3371-ND))
  - Mates: Hirose DF13 6 pos housing ([Digi-Key Link: Hirose DF13-6S-1.25C](https://www.digikey.com/products/en?keywords=H2182-ND))
--- a/docs/en/flight_controller/pixhawk6c_mini.md
+++ b/docs/en/flight_controller/pixhawk6c_mini.md
@@ -112,7 +112,7 @@ Please refer to the [Pixhawk 4 Mini Wiring Quick Start](../assembly/quick_start_
 | UART7  | /dev/ttyS5 | TELEM1                    | TELEM1           |
 | UART8  | /dev/ttyS6 | GPS2                      | GPS2             |

-<!-- See http://docs.px4.io/main/en/hardware/serial_port_mapping.html#serial-port-mapping -->
+<!-- See https://docs.px4.io/main/en/hardware/serial_port_mapping.html#serial-port-mapping -->

 ## Dimensions

--- a/docs/en/flight_controller/pixracer.md
+++ b/docs/en/flight_controller/pixracer.md
@@ -16,7 +16,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md

 ## Key Features

- Main System-on-Chip: [STM32F427VIT6 rev.3](http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1789)
+- Main System-on-Chip: [STM32F427VIT6 rev.3](https://www.st.com/en/microcontrollers-microprocessors/stm32f427-437.html)
  - CPU: 180 MHz ARM Cortex<sup>&reg;</sup> M4 with single-precision FPU
  - RAM: 256 KB SRAM (L1)
 - Standard FPV form factor: 36x36 mm with standard 30.5 mm hole pattern
@@ -41,7 +41,8 @@ Accessories include:

 ## Kit

-The Pixracer is designed to use a separate avionics power supply. This is necessary to avoid current surges from motors or ESCs to flow back to the flight controller and disturb its delicate sensors.
+The Pixracer is designed to use a separate avionics power supply.
+This is necessary to avoid current surges from motors or ESCs to flow back to the flight controller and disturb its delicate sensors.

 - Power module (with voltage and current sensing)
 - I2C splitter (supporting AUAV, Hobbyking and 3DR<sup>&reg;</sup> peripherals)
@@ -53,7 +54,7 @@ One of the main features of the board is its ability to use Wifi for flashing ne
 This frees it of the need of any desktop system.

 - [ESP8266 Wifi](../telemetry/esp8266_wifi_module.md)
- [Custom ESP8266 MAVLink firmware](https://github.com/dogmaphobic/mavesp8266)
+- [Custom ESP8266 MAVLink firmware](https://github.com/BeyondRobotix/mavesp8266)

 ::: info
 Firmware upgrade is not yet enabled over WiFi (it is supported by the default bootloader but not yet enabled).
--- a/docs/en/flight_controller/raccoonlab_fmu6x.md
+++ b/docs/en/flight_controller/raccoonlab_fmu6x.md
@@ -159,4 +159,4 @@ The complete set of supported configurations can be seen in the [Airframes Refer
 - [Pixhawk Autopilot FMUv6X Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-012%20Pixhawk%20Autopilot%20v6X%20Standard.pdf)
 - [Pixhawk Autopilot Bus Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-010%20Pixhawk%20Autopilot%20Bus%20Standard.pdf)
 - [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf)
- [RaccoonLab docs](http://docs.raccoonlab.co)
+- [RaccoonLab docs](https://docs.raccoonlab.co/)
--- a/docs/en/flight_controller/thepeach_k1.md
+++ b/docs/en/flight_controller/thepeach_k1.md
@@ -14,21 +14,17 @@ It is based on the **Pixhawk-project FMUv3** open hardware design and runs **PX4
 ## Specifications

 - Main Processor: STM32F427VIT6
-
  - 32bit ARM Cortex-M4, 168 MHz 256 KB RAM 2 MB Flash memory

 - IO Processor: STM32F100C8T6
-
  - ARM Cortex-M3, 32bit ARM Cortex-M3, 24 MHz, 8KB SRAM

 - On-board sensors
-
  - Accel/Gyro: ICM-20602
  - Accel/Gyro/Mag: MPU-9250
  - Barometer: MS5611

 - Interfaces
-
  - 8+5 PWM output (8 from IO, 5 from FMU)
  - Spektrum DSM / DSM2 / DSM-X Satellite compatible input
  - Futaba S.BUS compatible input and output
@@ -98,4 +94,4 @@ make thepeach_k1_default

 ## Where to buy

-Order from [ThePeach](http://thepeach.shop/)
+Order from [ThePeach](https://thepeach.shop/)
--- a/docs/en/flight_controller/thepeach_r1.md
+++ b/docs/en/flight_controller/thepeach_r1.md
@@ -14,21 +14,17 @@ It is based on the **Pixhawk-project FMUv3** open hardware design and runs **PX4
 ## Specifications

 - Main Processor: STM32F427VIT6
-
  - 32bit ARM Cortex-M4, 168 MHz 256 KB RAM 2 MB Flash memory

 - IO Processor: STM32F100C8T6
-
  - ARM Cortex-M3, 32bit ARM Cortex-M3, 24 MHz, 8KB SRAM

 - On-board sensors
-
  - Accel/Gyro: ICM-20602
  - Accel/Gyro/Mag: MPU-9250
  - Barometer: MS5611

 - Interfaces
-
  - 8+6 PWM output (8 from IO, 6 from FMU)
  - Spektrum DSM / DSM2 / DSM-X Satellite compatible input
  - Futaba S.BUS compatible input and output
@@ -42,7 +38,6 @@ It is based on the **Pixhawk-project FMUv3** open hardware design and runs **PX4
  - Analog inputs for voltage / Current of 1 battery

 - Interfaces For Raspberry Pi CM3+
-
  - VBUS
  - DDR2 Connector: Raspberry Pi CM3+
  - 1x UART
@@ -103,4 +98,4 @@ make thepeach_r1_default

 ## Where to buy

-Order from [ThePeach](http://thepeach.shop/)
+Order from [ThePeach](https://thepeach.shop/)
--- a/docs/en/flight_modes/offboard.md
+++ b/docs/en/flight_modes/offboard.md
@@ -85,9 +85,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding
 ### Copter

 - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg)
-
  - The following input combinations are supported:
-
    - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers.
    - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers.
    - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`)
@@ -95,18 +93,14 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding
  - All values are interpreted in NED (Nord, East, Down) coordinate system and the units are \[m\], \[m/s\] and \[m/s^2\] for position, velocity and acceleration, respectively.

 - [px4_msgs::msg::VehicleAttitudeSetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleAttitudeSetpoint.msg)
-
  - The following input combination is supported:
-
    - quaternion `q_d` + thrust setpoint `thrust_body`.
      Non-`NaN` values of `yaw_sp_move_rate` are used as feedforward terms expressed in Earth frame and in \[rad/s\].

  - The quaternion represents the rotation between the drone body FRD (front, right, down) frame and the NED frame. The thrust is in the drone body FRD frame and expressed in normalized \[-1, 1\] values.

 - [px4_msgs::msg::VehicleRatesSetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleRatesSetpoint.msg)
-
  - The following input combination is supported:
-
    - `roll`, `pitch`, `yaw` and `thrust_body`.

  - All the values are in the drone body FRD frame. The rates are in \[rad/s\] while thrust_body is normalized in \[-1, 1\].
@@ -116,7 +110,6 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding
 The following offboard control modes bypass all internal PX4 control loops and should be used with great care.

 - [px4_msgs::msg::VehicleThrustSetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleThrustSetpoint.msg) + [px4_msgs::msg::VehicleTorqueSetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleTorqueSetpoint.msg)
-
  - The following input combination is supported:
    - `xyz` for thrust and `xyz` for torque.
  - All the values are in the drone body FRD frame and normalized in \[-1, 1\].
@@ -134,9 +127,7 @@ The following MAVLink messages and their particular fields and field values are
 ### Copter/VTOL

 - [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED)
-
  - The following input combinations are supported: <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
-
    - Position setpoint (only `x`, `y`, `z`)
    - Velocity setpoint (only `vx`, `vy`, `vz`)
    - Acceleration setpoint (only `afx`, `afy`, `afz`)
@@ -146,9 +137,7 @@ The following MAVLink messages and their particular fields and field values are
  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_LOCAL_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_NED) and [MAV_FRAME_BODY_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_BODY_NED).

 - [SET_POSITION_TARGET_GLOBAL_INT](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_GLOBAL_INT)
-
  - The following input combinations are supported: <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
-
    - Position setpoint (only `lat_int`, `lon_int`, `alt`)
    - Velocity setpoint (only `vx`, `vy`, `vz`)
    - _Thrust_ setpoint (only `afx`, `afy`, `afz`)
@@ -169,18 +158,14 @@ The following MAVLink messages and their particular fields and field values are
 ### Fixed-wing

 - [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED)
-
  - The following input combinations are supported (via `type_mask`): <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
-
    - Position setpoint (`x`, `y`, `z` only; velocity and acceleration setpoints are ignored).
-
      - Specify the _type_ of the setpoint in `type_mask` (if these bits are not set the vehicle will fly in a flower-like pattern):
        ::: info
        Some of the _setpoint type_ values below are not part of the MAVLink standard for the `type_mask` field.
        :::

        The values are:
-
        - 292: Gliding setpoint.
          This configures TECS to prioritize airspeed over altitude in order to make the vehicle glide when there is no thrust (i.e. pitch is controlled to regulate airspeed).
          It is equivalent to setting `type_mask` as `POSITION_TARGET_TYPEMASK_Z_IGNORE`, `POSITION_TARGET_TYPEMASK_VZ_IGNORE`, `POSITION_TARGET_TYPEMASK_AZ_IGNORE`.
@@ -192,11 +177,8 @@ The following MAVLink messages and their particular fields and field values are
  - PX4 supports the coordinate frames (`coordinate_frame` field): [MAV_FRAME_LOCAL_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_NED) and [MAV_FRAME_BODY_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_BODY_NED).

 - [SET_POSITION_TARGET_GLOBAL_INT](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_GLOBAL_INT)
-
  - The following input combinations are supported (via `type_mask`): <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
-
    - Position setpoint (only `lat_int`, `lon_int`, `alt`)
-
      - Specify the _type_ of the setpoint in `type_mask` (if these bits are not set the vehicle will fly in a flower-like pattern):

        ::: info
@@ -204,7 +186,6 @@ The following MAVLink messages and their particular fields and field values are
        :::

        The values are:
-
        - 4096: Takeoff setpoint.
        - 8192: Land setpoint.
        - 12288: Loiter setpoint (fly a circle centred on setpoint).
@@ -220,11 +201,8 @@ The following MAVLink messages and their particular fields and field values are
 ### Rover

 - [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED)
-
  - The following input combinations are supported (in `type_mask`): <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
-
    - Position setpoint (only `x`, `y`, `z`)
-
      - Specify the _type_ of the setpoint in `type_mask`:

        ::: info
@@ -232,7 +210,6 @@ The following MAVLink messages and their particular fields and field values are
        ::

        The values are:
-
        - 12288: Loiter setpoint (vehicle stops when close enough to setpoint).

    - Velocity setpoint (only `vx`, `vy`, `vz`)
@@ -240,12 +217,10 @@ The following MAVLink messages and their particular fields and field values are
  - PX4 supports the coordinate frames (`coordinate_frame` field): [MAV_FRAME_LOCAL_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_NED) and [MAV_FRAME_BODY_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_BODY_NED).

 - [SET_POSITION_TARGET_GLOBAL_INT](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_GLOBAL_INT)
-
  - The following input combinations are supported (in `type_mask`): <!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/FlightTasks/tasks/Offboard/FlightTaskOffboard.cpp#L166-L170 -->
    - Position setpoint (only `lat_int`, `lon_int`, `alt`)
  - Specify the _type_ of the setpoint in `type_mask` (not part of the MAVLink standard).
    The values are:
-
    - Following bits not set then normal behaviour.
    - 12288: Loiter setpoint (vehicle stops when close enough to setpoint).

@@ -272,7 +247,7 @@ _Offboard mode_ is affected by the following parameters:

 ## Developer Resources

-Typically developers do not directly work at the MAVLink layer, but instead use a robotics API like [MAVSDK](https://mavsdk.mavlink.io/) or [ROS](http://www.ros.org/) (these provide a developer friendly API, and take care of managing and maintaining connections, sending messages and monitoring responses - the minutiae of working with _Offboard mode_ and MAVLink).
+Typically developers do not directly work at the MAVLink layer, but instead use a robotics API like [MAVSDK](https://mavsdk.mavlink.io/) or [ROS](https://www.ros.org/) (these provide a developer friendly API, and take care of managing and maintaining connections, sending messages and monitoring responses - the minutiae of working with _Offboard mode_ and MAVLink).

 The following resources may be useful for a developer audience:

--- a/docs/en/frames_plane/reptile_dragon_2.md
+++ b/docs/en/frames_plane/reptile_dragon_2.md
@@ -52,7 +52,7 @@ Key build features
 - [Caddx Vista FPV air unit](https://caddxfpv.com/products/caddx-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](http://www.mateksys.com/?portfolio=elrs-r24)
+- [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)
 - [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)
--- a/docs/en/frames_plane/turbo_timber_evolution.md
+++ b/docs/en/frames_plane/turbo_timber_evolution.md
@@ -46,7 +46,7 @@ Key Build Features:
 - MS4525DO differential pressure module and pitot tube
 - [Caddx Vista FPV air unit](https://caddxfpv.com/products/caddx-vista-kit)
 - [DJI FPV Goggles](https://www.dji.com/fpv)
- [ExpressLRS Matek Diversity RX](http://www.mateksys.com/?portfolio=elrs-r24)
+- [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)
  - Pixhawk 4 Mini mount and top GPS mount
  - FPV pod and camera mount
--- a/docs/en/frames_rover/rover_position_control.md
+++ b/docs/en/frames_rover/rover_position_control.md
@@ -110,8 +110,8 @@ The idea was to develop a platform that allows for easy control of wheeled UGVs
 - [Pixhawk Mini (Discontinued)](../flight_controller/pixhawk_mini.md)
  - 3DR 10S Power Module
  - 3DR 433MHz Telemetry Module (EU)
- [Spektrum Dxe Controller](http://www.spektrumrc.com/Products/Default.aspx?ProdId=SPM1000) or other PX4-compatible remotes
- [Spektrum Quad Race Serial Receiver w/Diversity](http://www.spektrumrc.com/Products/Default.aspx?ProdID=SPM4648)
+- [Spektrum Dxe Controller](https://www.spektrumrc.com/product/dxe-dsmx-transmitter-with-ar610/SPM1000.html) or other PX4-compatible remotes
+- [Spektrum Quad Race Serial Receiver w/Diversity](https://www.spektrumrc.com/product/dsmx-quad-race-serial-receiver-with-diversity/SPM4648.html)
 - [PX4Flow](../sensor/px4flow.md) (Deprecated)

 ### Assembly
--- a/docs/en/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md
+++ b/docs/en/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md
@@ -47,7 +47,7 @@ The approximate maximum size of the FC is: 50x110x22mm
 - [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor?pr_prod_strat=use_description&pr_rec_id=236dfda00&pr_rec_pid=7150470561981&pr_ref_pid=7150472462525&pr_seq=uniform)
 - [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) (Optional)
 - [Lidar Seeed Studio PSK-CM8JL65-CC5 (cheaper alternative)](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) (Optional)
- [5V BEC](http://www.mateksys.com/?portfolio=bec12s-pro)
+- [5V BEC](https://www.mateksys.com/?portfolio=bec12s-pro)
 - [Radio (RC) System](../getting_started/rc_transmitter_receiver.md) of your preference
 - [Servo cable extension cable male 30cm 10 pcs](https://www.getfpv.com/male-to-male-servo-extension-cable-twisted-22awg-jr-style-5-pcs.html)
 - [USB-C extension cable](https://www.digitec.ch/en/s1/product/powerguard-usb-c-usb-c-025-m-usb-cables-22529949?dbq=1&gclid=Cj0KCQjw2cWgBhDYARIsALggUhrh-z-7DSU0wKfLBVa8filkXLQaxUpi7pC0ffQyRzLng8Ph01h2R1gaAp0mEALw_wcB&gclsrc=aw.ds)
--- a/docs/en/getting_started/flight_reporting.md
+++ b/docs/en/getting_started/flight_reporting.md
@@ -21,7 +21,7 @@ You can also host a [private Flight Review server](../dev_log/log_encryption.md#

 ## Analyzing the Logs

-Upload the log file to the online [Flight Review](http://logs.px4.io) tool.
+Upload the log file to the online [Flight Review](https://logs.px4.io/) tool.
 After upload you'll be emailed a link to the analysis page for the log.

 [Log Analysis using Flight Review](../log/flight_review.md) explains how to interpret the plots, and can help you to verify/reject the causes of common problems: excessive vibration, poor PID tuning, saturated controllers, imbalanced vehicles, GPS noise, etc.
@@ -38,17 +38,17 @@ For more information see [Settings > MAVLink Settings > MAVLink 2 Logging (PX4 o

 ## Sharing the Log Files for Review by PX4 Developers

-The [Flight Review](http://logs.px4.io) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../index.md#reporting-bugs-issues).
+The [Flight Review](https://logs.px4.io/) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../index.md#reporting-bugs-issues).

 ## Log Configuration

-The logging system is configured by default to collect sensible logs for use with [Flight Review](http://logs.px4.io).
+The logging system is configured by default to collect sensible logs for use with [Flight Review](https://logs.px4.io/).

 Logging may further be configured using the [SD Logging](../advanced_config/parameter_reference.md#sd-logging) parameters or with a file on the SD card.
 Details on configuration can be found in the [logging configuration documentation](../dev_log/logging.md#configuration).

 ## Key Links

- [Flight Review](http://logs.px4.io)
+- [Flight Review](https://logs.px4.io/)
 - [Log Analysis using Flight Review](../log/flight_review.md)
 - [Flight Log Analysis](../dev_log/flight_log_analysis.md)
--- a/docs/en/getting_started/px4_basic_concepts.md
+++ b/docs/en/getting_started/px4_basic_concepts.md
@@ -62,9 +62,9 @@ Some of PX4's key features are:
 - Supports many different vehicle frames/types, including: [multicopters](../frames_multicopter/index.md), [fixed-wing aircraft](../frames_plane/index.md) (planes), [VTOLs](../frames_vtol/index.md) (hybrid multicopter/fixed-wing), [ground vehicles](../frames_rover/index.md), and [underwater vehicles](../frames_sub/index.md).
 - Great choice of drone components for [flight controller](#flight-controller), [sensors](#sensors), [payloads](#payloads), and other peripherals.
 - Flexible and powerful [flight modes](#flight-modes) and [safety features](#safety-settings-failsafe).
- Robust and deep integration with [companion computers](#offboard-companion-computer) and [robotics APIs](../robotics/index.md) such as [ROS 2](../ros2/user_guide.md) and [MAVSDK](http://mavsdk.mavlink.io).
+- Robust and deep integration with [companion computers](#offboard-companion-computer) and [robotics APIs](../robotics/index.md) such as [ROS 2](../ros2/user_guide.md) and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html).

-PX4 is a core part of a broader drone platform that includes the [QGroundControl](#qgc) ground station, [Pixhawk hardware](https://pixhawk.org/), and [MAVSDK](http://mavsdk.mavlink.io) for integration with companion computers, cameras and other hardware using the MAVLink protocol.
+PX4 is a core part of a broader drone platform that includes the [QGroundControl](#qgc) ground station, [Pixhawk hardware](https://pixhawk.org/), and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html) for integration with companion computers, cameras and other hardware using the MAVLink protocol.
 PX4 is supported by the [Dronecode Project](https://www.dronecode.org/).

 ## Ground Control Stations
--- a/docs/en/gps_compass/gps_hex_here2.md
+++ b/docs/en/gps_compass/gps_hex_here2.md
@@ -4,7 +4,7 @@
 This has been superseded by the [Cube Here 3](https://www.cubepilot.com/#/here/here3)
 :::

-The [Here2 GPS receiver](http://www.proficnc.com/all-products/152-gps-module.html) is an update to the Here GPS module from HEX.
+The _Here2 GPS receiver_ is an update to the Here GPS module from HEX.

 Main features include:

@@ -18,8 +18,7 @@ Main features include:

 ## Where to Buy

- [ProfiCNC](http://www.proficnc.com/all-products/152-gps-module.html) (Australia)
- [Other resellers](http://www.proficnc.com/stores)
+- [Resellers](https://www.cubepilot.com/#/reseller/list)

 ## Configuration

@@ -33,7 +32,7 @@ Setup and use on PX4 is largely plug and play.

 ## Wiring and Connections

-The Here2 GPS comes with an 8 pin connector that can be inserted directly into the [Pixhawk 2](http://www.hex.aero/wp-content/uploads/2016/07/DRS_Pixhawk-2-17th-march-2016.pdf) GPS UART port.
+The Here2 GPS comes with an 8 pin connector that can be inserted directly into the Pixhawk 2 `GPS` UART port.

 The Pixhawk 3 Pro and Pixracer have a 6 pin GPS port connector.
 For these controllers you can modify the GPS cable (as shown below) to remove pin 6 and 7.
--- a/docs/en/gps_compass/rtk_gps_trimble_mb_two.md
+++ b/docs/en/gps_compass/rtk_gps_trimble_mb_two.md
@@ -18,7 +18,7 @@ The following firmware options need to be selected when buying the device:
 ## Antennas and Cable

 The Trimble MB-Two requires two dual-frequency (L1/L2) antennas.
-A good example is the [Maxtenna M1227HCT-A2-SMA](http://www.maxtena.com/products/helicore/m1227hct-a2-sma/)
+A good example is the [Maxtenna M1227HCT-A2-SMA](https://www.maxtena.com/products/helicore/m1227hct-a2-sma/)
 (which can be bought, for instance, from [Farnell](https://uk.farnell.com/maxtena/m1227hct-a2-sma/antenna-1-217-1-25-1-565-1-61ghz/dp/2484959)).

 The antenna connector type on the device is MMCX.
--- a/docs/en/hardware/board_support_guide.md
+++ b/docs/en/hardware/board_support_guide.md
@@ -20,7 +20,6 @@ The general requirements for all supported boards are:
   Board needs to pass acceptance criteria to ensure quality of parts and assembly.
 1. A clear and easy way to contact customer support for customers.
   One or more of the following is accepted:
-
   - PX4 Discord server presence
   - Support email
   - Phone number
@@ -29,7 +28,6 @@ The general requirements for all supported boards are:
 1. The board needs to use the [PX4 bootloader protocol](https://github.com/PX4/PX4-Autopilot/tree/main/platforms/nuttx/src/bootloader).
   For more information on bootloaders see: [PX4 Nuttx Porting Guide > Bootloader](../hardware/porting_guide_nuttx.md#bootloader).
 1. Adequate documentation, which includes, but is not limited to:
-
   - A complete pinout made available publicly that maps PX4 pin definitions to:
     1. Microcontroller pins
     2. Physical external connectors
@@ -48,13 +46,11 @@ Manufacturer supported boards may be as well/better supported than Pixhawk board

 ## Pixhawk Standard

-A Pixhawk board is one that conforms to the Pixhawk standards. These standards are laid out on [http://pixhawk.org](http://pixhawk.org/), but at high-level require that the board passes electrical tests mandated by the standard and the manufacturer has signed the Pixhawk adopter and trademark agreement.
+A Pixhawk board is one that conforms to the Pixhawk standards. These standards are laid out on [pixhawk.org](https://pixhawk.org/), but at high-level require that the board passes electrical tests mandated by the standard and the manufacturer has signed the Pixhawk adopter and trademark agreement.

 PX4 generally only supports boards that are commercially available, which typically means that board standards released within the last five years are supported.

-<a id="ver_rev_id"></a>
-
-### VER and REV ID (Hardware Revision and Version Sensing)
+### VER and REV ID (Hardware Revision and Version Sensing) {#ver_rev_id}

 FMUv5 and onwards have an electrical sensing mechanism.
 This sensing coupled with optional configuration data will be used to define hardware’s configuration with respect to a mandatory device and power supply configuration. Manufacturers must obtain the VER and REV ID from PX4 board maintainers by issuing a PR to ammend the [DS-018 Pixhawk standard](https://github.com/pixhawk/Pixhawk-Standards) for board versions and revisions.
--- a/docs/en/index.md
+++ b/docs/en/index.md
@@ -127,7 +127,7 @@ The following icons used in this library are licensed separately (as shown below

 <img src="../assets/site/position_fixed.svg" title="Position fix required (e.g. GPS)" width="30px" /> _placeholder_ icon made by <a href="https://www.flaticon.com/authors/smashicons" title="Smashicons">Smashicons</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="https://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.

-<img src="../assets/site/automatic_mode.svg" title="Automatic mode" width="30px" /> _camera-automatic-mode_ icon made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.
+<img src="../assets/site/automatic_mode.svg" title="Automatic mode" width="30px" /> _camera-automatic-mode_ icon made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="https://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.

 ## Governance

--- a/Show More
+++ b/Show More