Replace string

Ardupilot -> ArduPilot

README.md

@@ -1,5 +1,5 @@
 
-# Ardupilot Wiki Sources
+# ArduPilot Wiki Sources
 
 ## ArduPilot Wiki Editing Guide
 

build_parameters.py

@@ -9,15 +9,15 @@
 
     * Before start:
         * Folder and file management tested only in linux;
-        * It is supposed to have the wiki repo in a same level of an Ardupilot repo and two other folders named new_params_mvesion/ and old_params_mversion/
+        * It is supposed to have the wiki repo in a same level of an ArduPilot repo and two other folders named new_params_mvesion/ and old_params_mversion/
 
     * First step is go to each vehicle on firmware.ardupilot.org and get all available versions namely as stable/beta/latest.
         * For each version it gets a board and get git_version.txt file;
         * It parsers that to get the version and commit hash;
         * It creates a dictionary with vehicles, versions and commit hashes.
     
-    * Second step is use the dict to navigates on a Ardupilot Repo, changing checkouts to desidered hashes.
-        * Relies on ArdupilotRepoFolder/Tools/autotest/param_metadata/param_parse.py to generate the parameters files;
+    * Second step is use the dict to navigates on a ArduPilot Repo, changing checkouts to desidered hashes.
+        * Relies on ArduPilotRepoFolder/Tools/autotest/param_metadata/param_parse.py to generate the parameters files;
         * It renames the anchors for all files, except for latest versions. 
 
     * Third step: create the json files and move all generated files.
@@ -506,7 +506,7 @@ def print_versions(commits_to_checkout_and_parse):
 
 
 # Step 1 - Select the versions for generate parameters
-setup()                                                             # Reset the Ardupilot folder/repo
+setup()                                                             # Reset the ArduPilot folder/repo
 feteched_releases = fetch_releases(BASEURL, VEHICLES)               # All folders/releases.
 commits_to_checkout_and_parse = get_commit_dict(feteched_releases)  # Parse names, and git hashes.
 print_versions(commits_to_checkout_and_parse)                       # Present work dict.

common/source/docs/common-aerotenna-usd1.rst

@@ -14,7 +14,7 @@ The user manual for this radar unit can be found `here <https://cdn.shopify.com/
 
 .. note::
 
-   Support for this sensor is available in Ardupilot firmware versions 4.0 and later
+   Support for this sensor is available in ArduPilot firmware versions 4.0 and later
 
 Where to Buy
 ------------

common/source/docs/common-connect-mission-planner-autopilot.rst

@@ -9,7 +9,7 @@ in order to receive telemetry and control the vehicle.
 
 .. note::
 
-   There are separate instructions for connecting in order to :ref:`Load Firmware <common-loading-firmware-onto-pixhawk>` for existing Ardupilot firmware installations, or for boards :ref:`without existing Ardupilot firmware <common-loading-firmware-onto-chibios-only-boards>` .
+   There are separate instructions for connecting in order to :ref:`Load Firmware <common-loading-firmware-onto-pixhawk>` for existing ArduPilot firmware installations, or for boards :ref:`without existing ArduPilot firmware <common-loading-firmware-onto-chibios-only-boards>` .
 
 
 Setting up the connection

common/source/docs/common-external-leds.rst

@@ -34,7 +34,7 @@ Because most users use an external :ref:`GPS and Compass module <common-position
 Serially Connected Devices
 ==========================
 
-Currently, Ardupilot supports Neopixel and ProfiLED RGB LED strings. They can be used for NTF notifications from the autopilot on status and warnings like other RGB LEDs, or be programmed in unlimited ways using LUA scripts on the autopilot's SD card. For use with scripting the output function must be set to a scripting output function (94 - 109) the script then assignees this output to LEDs. See :ref:`common-lua-scripts` for more use examples using LUA scripts.
+Currently, ArduPilot supports Neopixel and ProfiLED RGB LED strings. They can be used for NTF notifications from the autopilot on status and warnings like other RGB LEDs, or be programmed in unlimited ways using LUA scripts on the autopilot's SD card. For use with scripting the output function must be set to a scripting output function (94 - 109) the script then assignees this output to LEDs. See :ref:`common-lua-scripts` for more use examples using LUA scripts.
 
 ..  youtube:: ytW538e_cQw
 

common/source/docs/common-fettec-onewire.rst

@@ -202,6 +202,6 @@ Troubleshooting
 - The ESCs are not initializing.
    Check if the parameters are correct. Also make sure the telemetry pin is connected, as it will not work without it. 
 - ESCs are not found in FETtec configurator.
-   A halfduplex 2MBaud/s serial connection is required for the use with the FETtec configurator, which is currently not supported by Ardupilot. You need to use a external serial  device like a FETtec FC or a USB serial adapter. Please disconnect the Ardupilot FC from the ESCs to find it in the FETtec configurator.
+   A halfduplex 2MBaud/s serial connection is required for the use with the FETtec configurator, which is currently not supported by ArduPilot. You need to use a external serial  device like a FETtec FC or a USB serial adapter. Please disconnect the ArduPilot FC from the ESCs to find it in the FETtec configurator.
 
 

common/source/docs/common-flight-controller-wiring.rst

@@ -39,7 +39,7 @@ Radio Control Receivers are normally used for pilot control. While exclusive pil
 .. image:: ../../../images/rx-connection.jpg
   :width: 450px
 
-Ardupilot autodetects the following serial RC receiver protocols:
+ArduPilot autodetects the following serial RC receiver protocols:
 
    #. PPM remote control (R/C) receivers
    #. SBus receivers
@@ -53,7 +53,7 @@ Ardupilot autodetects the following serial RC receiver protocols:
 For traditional single-wire-per-channel (PWM) receivers a PPM encoder
 can be used to convert the receiver outputs to PPM. 
 
-.. tip:: As of Ardupilot 4.0 versions of firmware, any autopilot UART may be used as an input for an RC receiver, instead of the designated RCin or SBUS input pin, by setting that port's ``SERIALx_PROTOCOL`` to 23. However, some serial protocols require inversion (SBUS,FPort) and the UART must be capable of using the ``SERIALx_OPTIONS`` parameter to invert the RX input, otherwise, an external inverter will be required. This also allows a second RC receiver to be attached to the autopilot for redundancy. If the first receiver (first detected valid after boot) fails, then the second will be used. Note that whatever RC input ranges and trims were calibrated will be used for the second when it becomes active. Both receivers MUST be set to send no pulses in failsafe for this to work properly. :ref:`RC_OPTIONS<RC_OPTIONS>` bit 10 must be set also.
+.. tip:: As of ArduPilot 4.0 versions of firmware, any autopilot UART may be used as an input for an RC receiver, instead of the designated RCin or SBUS input pin, by setting that port's ``SERIALx_PROTOCOL`` to 23. However, some serial protocols require inversion (SBUS,FPort) and the UART must be capable of using the ``SERIALx_OPTIONS`` parameter to invert the RX input, otherwise, an external inverter will be required. This also allows a second RC receiver to be attached to the autopilot for redundancy. If the first receiver (first detected valid after boot) fails, then the second will be used. Note that whatever RC input ranges and trims were calibrated will be used for the second when it becomes active. Both receivers MUST be set to send no pulses in failsafe for this to work properly. :ref:`RC_OPTIONS<RC_OPTIONS>` bit 10 must be set also.
 
 .. tip::
 

common/source/docs/common-installing-3dr-ublox-gps-compass-module.rst

@@ -102,4 +102,4 @@ Advanced Configuration
 ======================
 
 Advanced configuration of the UBlox GPS's internal settings is
-documented in :ref:`UBlox GPS Configuration <common-ublox-gps>`. But this is never used by the average user. Ardupilot automatically configures the gps during initialization.
+documented in :ref:`UBlox GPS Configuration <common-ublox-gps>`. But this is never used by the average user. ArduPilot automatically configures the gps during initialization.

common/source/docs/common-magnetic-interference.rst

@@ -159,7 +159,7 @@ Natural and Artificial Magnetic Anomalies Warning
 GPS for yaw
 ===========
 
-Ardupilot supports the use of GPS heading information to reduce malfunctions caused by changes in the magnetic field in certain environments.
+ArduPilot supports the use of GPS heading information to reduce malfunctions caused by changes in the magnetic field in certain environments.
   - `Configure GPS for yaw <https://ardupilot.org/copter/docs/common-gps-for-yaw.html>`__
 
   .. note::

common/source/docs/common-mro-uavcan-adapter-node.rst

@@ -5,16 +5,16 @@ mRobotics DroneCAN Adapter Node
 ===============================
 
 
-The mRo CAN Node is a collaborative project with Ardupilot. It began with a desire to make CAN peripherals more standard in the drone community. Compared to other boards that have open-source hardware but closed source code, mRo CAN node is completely open. The CAN Node F303 is the version 2 of mRobotics' CAN Node, featuring more flash space.
+The mRo CAN Node is a collaborative project with ArduPilot. It began with a desire to make CAN peripherals more standard in the drone community. Compared to other boards that have open-source hardware but closed source code, mRo CAN node is completely open. The CAN Node F303 is the version 2 of mRobotics' CAN Node, featuring more flash space.
 
-With this board, you can easily utilize the Ardupilot driver library to convert ArduPilot supported GPS, I2C, and GPIO based (ie Safety Switch) peripherals to DroneCAN bus peripherals.
+With this board, you can easily utilize the ArduPilot driver library to convert ArduPilot supported GPS, I2C, and GPIO based (ie Safety Switch) peripherals to DroneCAN bus peripherals.
 
 .. image:: ../../../images/mRo-can-node.jpg
 
 
-mRo CAN Node uses open-source code, which utilizes the existing and proven Ardupilot DroneCAN driver library (see :ref:`DroneCAN Adapter Nodes <common-uavcan-adapter-node>` for firmware versions and capabilities). It features a  bootloader for "over CAN" firmware updates and an RTOS running Chibios.
+mRo CAN Node uses open-source code, which utilizes the existing and proven ArduPilot DroneCAN driver library (see :ref:`DroneCAN Adapter Nodes <common-uavcan-adapter-node>` for firmware versions and capabilities). It features a  bootloader for "over CAN" firmware updates and an RTOS running Chibios.
 
-The adapter's CAN Node ID can be set manually or automatically (Not yet supported in stable Ardupilot). The hardware design is open source, so that anyone can contribute to the CAN peripheral world with a proven CAN / MCU interface.
+The adapter's CAN Node ID can be set manually or automatically (Not yet supported in stable ArduPilot). The hardware design is open source, so that anyone can contribute to the CAN peripheral world with a proven CAN / MCU interface.
 
 As delivered, it is setup to be plug-and-play as a DroneCAN GPS/Magnetometer/LED/Airspeed by simply plugging in the 6pin GH connector from any mRo or other GPS, and connecting I2C Compasses, RGB LEDs, and/or Airspeed sensors supported by ArduPilot, as desired. 
 

common/source/docs/common-msp-osd-overview-4.2.rst

@@ -4,7 +4,7 @@
 MSP OSD
 =======
 
-Ardupilot supports 2 types of MSP OSDs:
+ArduPilot supports 2 types of MSP OSDs:
 
  - Telemetry based OSDs such as DJI FPV Goggles V1/V2, DJI Goggles RE, FatShark ByteFrost, FatShark SharkByte, MWOSD, etc
  - DisplayPort (aka CANVAS MODE) based OSD's such as FatShark SharkByte (fw 09042021 and later) and MWOSD

common/source/docs/common-object-avoidance-landing-page.rst

@@ -4,7 +4,7 @@
 Object Avoidance
 ================
 
-Ardupilot supports several kinds of object avoidance. Avoidance of Airborne Vehicles (ADSB) and Object Avoidance (Object/Ground/Ceiling).
+ArduPilot supports several kinds of object avoidance. Avoidance of Airborne Vehicles (ADSB) and Object Avoidance (Object/Ground/Ceiling).
 
 Supported types vary with vehicle (Plane only supports ADSB). Some kinds of avoidance require external hardware, such as ADSB receivers or  Rangefinders.
 

common/source/docs/common-pixhawk-camera-trigger-setup.rst

@@ -8,7 +8,7 @@ Camera Trigger Setup for Pixhawk
     :width: 450px
 
 This guide is intended to help you modify a remote shutter release cable
-for use with Ardupilot autopilots and setup the flight
+for use with ArduPilot autopilots and setup the flight
 controller for triggering the camera. This method eliminates the need
 (and costs) for 3\ :sup:`rd` party triggering devices. In this specific
 example, we will use a Sony Alpha 6000 (A6000) camera. This procedure

common/source/docs/common-pomegranate-systems-pm.rst

@@ -13,7 +13,7 @@ Intelligent power monitor, accurate fuel gauge, and efficient 5V/2A power supply
 -    High-resolution current and voltage monitoring with state of charge integration.
 -    Power monitoring for battery, 5V, and 3V rails.
 -    Supports 2-6S batteries (6-26V) and currents of up to 100A, when actively cooled.
--    CANbus interface using DroneCAN v0 protocol (PX4 / Ardupilot Compatible).
+-    CANbus interface using DroneCAN v0 protocol (PX4 / ArduPilot Compatible).
 -    Efficient 5V switching regulator provides up to 2A of low noise current.
 -    Daytime visible state of charge LED
 -    Electronic CANbus termination simplifies wiring.

common/source/docs/common-rc-systems.rst

@@ -148,7 +148,7 @@ With integrated telemetry:
     DragonLink <common-dragonlink-rc>
     FRSky <common-frsky-rc>
     Graupner (HOTT) <common-graupner-rc>
-    Multiplex (no support in Ardupilot for M-Link telemetry yet) <common-multiplex-rc>
+    Multiplex (no support in ArduPilot for M-Link telemetry yet) <common-multiplex-rc>
     Spektrum SRXL2 <common-spektrum-rc>
     TBS CRSF <common-tbs-rc>
 

common/source/docs/common-telemetry-landingpage.rst

@@ -9,7 +9,7 @@ transmitter) using telemetry. Follow the links below for configuration
 information based upon your set-up.
 
 .. note:: Some RC systems incorporate telemetry in addition to RC control
-.. note:: Ardupilot will automatically fall back to back to MAVLink1 if MAVLink 2 serial port protocol is selected and no MAVLink 2 data is received from the groundstation in response
+.. note:: ArduPilot will automatically fall back to back to MAVLink1 if MAVLink 2 serial port protocol is selected and no MAVLink 2 data is received from the groundstation in response
 .. image:: ../../../images/Telemetry_LandingImage.jpg
     :target: ../_images/Telemetry_LandingImage.jpg
 

common/source/docs/common-uavcan-adapter-node.rst

@@ -101,7 +101,7 @@ The firmware can also be used for I2C peripherals.
 Rangefinder
 -----------
 
- To use rangefinders, follow the instructions at  :ref:`DroneCAN Setup Advanced<common-uavcan-setup-advanced>` to set up the Ardupilot parameters. Using MissionPlanner or DroneCAN Gui, set the parameters on the adaptor node following the instructions for the relevant rangefinder.
+ To use rangefinders, follow the instructions at  :ref:`DroneCAN Setup Advanced<common-uavcan-setup-advanced>` to set up the ArduPilot parameters. Using MissionPlanner or DroneCAN Gui, set the parameters on the adaptor node following the instructions for the relevant rangefinder.
 
  .. note::
 
@@ -110,7 +110,7 @@ Rangefinder
 
  .. note::
 
- 	The RNGFNDx_ADDR Ardupilot parameter must be set above 0 and be equal to the number set on the DroneCAN adapter node.
+ 	The RNGFNDx_ADDR ArduPilot parameter must be set above 0 and be equal to the number set on the DroneCAN adapter node.
 
 DroneCAN Adapter Nodes
 ======================

common/source/docs/common-uavcan-setup-advanced.rst

@@ -28,7 +28,7 @@ Detailed description of protocol can be found at https://uavcan.org/
 DroneCAN Peripheral Types Supported
 ===================================
 
-Ardupilot currently supports the following types of DroneCAN peripherals:
+ArduPilot currently supports the following types of DroneCAN peripherals:
 
 +---------------------+--------------------+-------------------+
 |GPS                  |Compass             |Barometer          |
@@ -111,7 +111,7 @@ When a device is attached and recognized, it's node ID and hardware ID are enter
 SLCAN
 =====
 
-Ardupilot and DroneCAN provides a means to directly communicate with DroneCAN devices on the CAN BUS attached to the autopilot: SLCAN. Enabling SLCAN and communicating with the DroneCAN devices is dependent on the autopilot's processor. F7/H7 processors use one method and F4, a different method.
+ArduPilot and DroneCAN provides a means to directly communicate with DroneCAN devices on the CAN BUS attached to the autopilot: SLCAN. Enabling SLCAN and communicating with the DroneCAN devices is dependent on the autopilot's processor. F7/H7 processors use one method and F4, a different method.
 
 .. toctree::
     :maxdepth: 1

common/source/docs/common-velocity-can-escs.rst

@@ -30,7 +30,7 @@ Connection and Configuration
 
 .. note::
 
-    The Velocity ESC uses the PiccoloCAN protocol. Originally developed for the Piccolo autopilot, the protocol is now natively supported by Ardupilot 
+    The Velocity ESC uses the PiccoloCAN protocol. Originally developed for the Piccolo autopilot, the protocol is now natively supported by ArduPilot 
 
 To enable communication with the Velocity ESCs using PiccoloCAN, the following parameters must be set.
 

common/source/docs/common-wiki_editing_guide.rst

@@ -32,7 +32,7 @@ All content on this wiki is licensed under the terms of the `Creative Commons At
 Translating wiki pages
 ======================
 
-Translation is currently not supported, but it is possible to view Ardupilot.org in other languages through services such as `Google Translate <https://translate.google.com/translate?hl=&sl=en&tl=es&u=https%3A%2F%2Fardupilot.org%2F>`__.
+Translation is currently not supported, but it is possible to view ArduPilot.org in other languages through services such as `Google Translate <https://translate.google.com/translate?hl=&sl=en&tl=es&u=https%3A%2F%2Fardupilot.org%2F>`__.
 
 
 FAQ - Why are my changes not published?

copter/source/docs/reference-frames-holybro-s500.rst

@@ -11,7 +11,7 @@ The Holybro S500 is a relatively low cost and easy to assemble frame including f
 Parts List
 ----------
 
-- `S500 V2 Kit-Pix32v5 (Ardupilot) <https://shop.holybro.com/s500-v2-kitmotor2216-880kv-propeller1045_p1153.html>`__ (be sure to push the, "S500 V2 Kit-Pix32v5 (Ardupilot)" button on the right side of the page) 
+- `S500 V2 Kit-Pix32v5 (ArduPilot) <https://shop.holybro.com/s500-v2-kitmotor2216-880kv-propeller1045_p1153.html>`__ (be sure to push the, "S500 V2 Kit-Pix32v5 (ArduPilot)" button on the right side of the page) 
 - 3300mAh to 5300mAh 3S or 4S battery
 - RC transmitter with at least 6 channels
 

copter/source/docs/traditional-helicopter-connecting-apm.rst

@@ -22,7 +22,7 @@ The RC input for many ardupilot compatible autopilots is either PPM SUM (8 chann
 The default receiver channel to ArduCopter RC input function mapping is as follows:
 
 +--------------+--------------------+
-| RC Receiver  | Ardupilot RC       |
+| RC Receiver  | ArduPilot RC       |
 | Channel      | Input Function     |
 +--------------+--------------------+
 | 1 (Aileron)  | Roll (note1)       |

dev/source/docs/building-ardupilot-apm-with-visual-studio-visual-micro.rst

@@ -240,19 +240,19 @@ Multiple installs of Arduino:  It is important to note that Arduino has
 only one location where the parameters are stored -
 in C:\\Users\\....\\AppData\\Roaming\\Arduino\\preferences.txt.  Any
 time you start any installation of Arduino - a standard version, the
-Ardupilot Arduino version or even changing settings in Visual Micro -
+ArduPilot Arduino version or even changing settings in Visual Micro -
 that file may get changed.  So, it is very important to check all the
 settings in the IDE you are using each time you change the IDE - to
 avoid having the preferences set to that of the last IDE you used.
 
 **Referencing a standard Arduino in Visual Micro:** 
 Normally, Visual Micro is setup to reference a standard installation of Arduino instead
-of the special Ardupilot Ardunio for the HAL versions of APM.  You can
+of the special ArduPilot Ardunio for the HAL versions of APM.  You can
 configure Visual Studio or Atmel Studio to reference a standard
 installation and it may build and upload the APM code but that upload
 will not work.  The build size is different and it does not connect to
 Mission Planner. It is strongly suggested you only reference the special
-Ardupilot Arduino installation when working with APM code.
+ArduPilot Arduino installation when working with APM code.
 
 **Using Arduino statements and libraries:**  
 This is better stated as