Docs are now in user guide and main (#19977)

* Fix links to docs in source to point to docs on main not master

* More docs and scripts that need to point to main

src/modules/commander/Arming/PreFlightCheck/checks/airframeCheck.cpp

@@ -48,7 +48,7 @@ bool PreFlightCheck::airframeCheck(orb_advert_t *mavlink_log_pub, const vehicle_
 	// We no longer support VTOL on fmu-v2, so we need to warn existing users.
 	if (status.is_vtol) {
 		mavlink_log_critical(mavlink_log_pub,
-				     "VTOL is not supported with fmu-v2, see docs.px4.io/master/en/config/firmware.html#bootloader");
+				     "VTOL is not supported with fmu-v2, see docs.px4.io/main/en/config/firmware.html#bootloader");
 		success = false;
 	}
 

src/modules/ekf2/EKF2.cpp

@@ -2249,7 +2249,7 @@ int EKF2::print_usage(const char *reason)
 ### Description
 Attitude and position estimator using an Extended Kalman Filter. It is used for Multirotors and Fixed-Wing.
 
-The documentation can be found on the [ECL/EKF Overview & Tuning](https://docs.px4.io/master/en/advanced_config/tuning_the_ecl_ekf.html) page.
+The documentation can be found on the [ECL/EKF Overview & Tuning](https://docs.px4.io/main/en/advanced_config/tuning_the_ecl_ekf.html) page.
 
 ekf2 can be started in replay mode (`-r`): in this mode, it does not access the system time, but only uses the
 timestamps from the sensor topics.

src/modules/gimbal/gimbal.cpp

@@ -539,7 +539,7 @@ static void usage()
 Mount/gimbal Gimbal control driver. It maps several different input methods (eg. RC or MAVLink) to a configured
 output (eg. AUX channels or MAVLink).
 
-Documentation how to use it is on the [gimbal_control](https://docs.px4.io/master/en/advanced/gimbal_control.html) page.
+Documentation how to use it is on the [gimbal_control](https://docs.px4.io/main/en/advanced/gimbal_control.html) page.
 
 ### Examples
 Test the output by setting a angles (all omitted axes are set to 0):

src/modules/mavlink/mavlink_receiver.cpp

@@ -1228,7 +1228,7 @@ MavlinkReceiver::handle_message_set_actuator_control_target(mavlink_message_t *m
 #if defined(ENABLE_LOCKSTEP_SCHEDULER)
 	PX4_ERR("SET_ACTUATOR_CONTROL_TARGET not supported with lockstep enabled");
 	PX4_ERR("Please disable lockstep for actuator offboard control:");
-	PX4_ERR("https://dev.px4.io/master/en/simulation/#disable-lockstep-simulation");
+	PX4_ERR("https://docs.px4.io/main/en/simulation/#disable-lockstep-simulation");
 	return;
 #endif
 

src/modules/micrortps_bridge/README.md

@@ -1 +1 @@
-For see a complete documentation, please follow this [link](https://dev.px4.io/master/en/middleware/micrortps.html)
+For see a complete documentation, please follow this [link](https://docs.px4.io/main/en/middleware/micrortps.html)

src/modules/replay/Replay.cpp

@@ -1171,7 +1171,7 @@ The module is typically used together with uORB publisher rules, to specify whic
 The replay module will just publish all messages that are found in the log. It also applies the parameters from
 the log.
 
-The replay procedure is documented on the [System-wide Replay](https://dev.px4.io/master/en/debug/system_wide_replay.html)
+The replay procedure is documented on the [System-wide Replay](https://docs.px4.io/main/en/debug/system_wide_replay.html)
 page.
 )DESCR_STR");