clearpathrobotics · tonybaltovski · Aug 28, 2025 · Aug 27, 2025 · Aug 28, 2025
@@ -4,7 +4,7 @@ The _Sensor Arch_ places Husky's cameras and GNSS antennas above the robot for o
 These steps will give you access to the related cable routings for repairs:
 
 1.  Remove the 3 screws from the inside access panel.
-2.  Remove the panel by sliding is toward the end of the robot.
+2.  Remove the panel by sliding it toward the end of the robot.
 3.  The _Arch Posts_ have cable tie anchors.
     You can remove the cable ties with side cutters.
 4.  Cables route through an obround cutout in the _Enclosure_.

@@ -11,7 +11,7 @@
 </center>
 
 To make a Husky AMP, we take a Husky A300, remove the Top Plate, and then install an enclosure on top of the base robot.
-We added a connector bulkhead between the base robot and the enclosure to keep cable routings tidy, and make the maintenence process quick.
+We added a connector bulkhead between the base robot and the enclosure to keep cable routings tidy, and make the maintenance process quick.
 The connectors on this bulkhead are extension cables from existing [Husky A300 interfaces](/docs_robots/outdoor_robots/husky/a300/integration_husky/#system-interface-circuit-board-connector-summary), which are listed below.
 
 <center>

@@ -32,6 +32,6 @@ Refer to the [Husky A300 AMP's Components Overview](/docs_robots/solutions/husky
       src="/img/robot_images/husky_a300_images/husky_a300_observer_isometric_3.png"
       width="800"
     />
-    <figcaption>The Husky Oberver, with the included Stationary Dock.</figcaption>
+    <figcaption>The Husky Observer, with the included Stationary Dock.</figcaption>
   </figure>
 </center>
@@ -34,7 +34,7 @@ These fans operate similar to a server; as all 4 push air into the robot to crea
             src="/img/robot_images/husky_a300_images/husky_a300_fans_2.png"
             width="500"
           />
-          <figcaption>Fiew From The Front Of Husky</figcaption>
+          <figcaption>View From The Front Of Husky</figcaption>
         </figure>
       </center>
   7.  Disconnect the fan's latching connector, and remove the fan.

@@ -2,7 +2,7 @@
 
 [//]: <> (TODO, add image of an internal integration)
 
-There are interfaces inside the Husky for your custom compnents.
+There are interfaces inside the Husky for your custom components.
 This [Interface Control Drawing](/assets/pdf/clearpath_robotics_034163.pdf) shows the available volume near the robot's batteries, 
   noting that the size of this volume changes depending on what battery configuration your Husky has—_(40 Ah, 80 Ah, or 120 Ah)_.
 The drawing also shows mounting provisions on the robot's Electronics Tray, for including these components:

@@ -10,7 +10,7 @@
   </figure>
 </center>
 
-The lifting equipment and straps must rated for the weight of Husky and any mounted payloads, plus any factor of safety per your local worksite regulations.
+The lifting equipment and straps must be rated for the weight of Husky and any mounted payloads, plus any factor of safety per your local worksite regulations.
 Refer to the [Husky's Technical Specifications](#technical-specifications) for the weight of Husky and its maximum payload.
 
 :::note

@@ -22,7 +22,7 @@
         width="600"
       />
     </center>
-  3. Disconnect the both sets of motor power and cables from the chassis on the side of the robot with the motor being replaced.
+  3. Disconnect both sets of motor power and cables from the chassis on the side of the robot with the motor being replaced.
     The thick power cables are removed by pulling on the cable.
     The thinner data cables have a latch on the connector; press on the latch and then pull on the connector.
     <center>

@@ -31,7 +31,7 @@ The network switch connects the primary computer, the rear debugging port, and a
     When reinstalling the switch:
 
     * Make sure the power cable is connected.
-    * Make sure the waterfroofing washers are included.
+    * Make sure the waterproofing washers are included.
     * Torque the 4 screws to 1.2 N·m.
 
   :::

@@ -209,8 +209,8 @@ You must enable the output, via the ROS topic above, each time after the system
 
 ### AUX Inputs {#aux-inputs}
 
-The System Interface circuit board has 3 auxilliary inputs—_(AUX1 IN, AUX2 IN, AUX3 IN)_—that allow external payloads to provide inputs to the robot.
-Each of these auxilliary inputs can be driven by one of the following:
+The System Interface circuit board has 3 auxiliary inputs—_(AUX1 IN, AUX2 IN, AUX3 IN)_—that allow external payloads to provide inputs to the robot.
+Each of these auxiliary inputs can be driven by one of the following:
 
 - a 12 V input
 - a 24 V input

@@ -4,7 +4,7 @@ Performing a circle check can reduce safety risks, increase the operating lifesp
 These are our suggested daily checks before sending the Husky on missions:
 
 1.  Check that the weather forecast has acceptable conditions for the robot.
-2.  Check that the intended worksite's terrain is acceptable, without deep trenches, overhanging obstacles, children, of other hazards that were not acceptable per your Risk Assessment.
+2.  Check that the intended worksite's terrain is acceptable, without deep trenches, overhanging obstacles, children, or other hazards that were not acceptable per your Risk Assessment.
 3.  Check the tire pressures.
 4.  Inspect the tire treads for excessive wear or punctures.
 5.  Inspect the drivetrain for loose screws.

@@ -445,7 +445,7 @@ export function ComponentRiskAssessmentLine_27() {
           Racking must be securely fastened, and be loaded to prevent falling items.
           <br/>
           <br/>
-          It is the commissioning and operating teams's responibility to ensure that the Husky A300 colliding with racking will not cause items to fall on a person.
+          It is the commissioning and operating teams's responsibility to ensure that the Husky A300 colliding with racking will not cause items to fall on a person.
           It is the commissioning team's responsibility to ensure local regulations are followed.
         </>
       </SafetyAdmonition>

@@ -11,7 +11,7 @@ Husky A300 is equipped with 3 safety functions to reduce the system risk:
 :::info
 
 Your commissioning team must evaluate the functionality of Husky's safety functions in the context of your worksite and use case.
-Perfrom a Risk Assessment to understand the risks of deploying Husky in your application, and whether customizations should be made to reduce these risks.
+Perform a Risk Assessment to understand the risks of deploying Husky in your application, and whether customizations should be made to reduce these risks.
 
 ISO 12100 is the Risk Assessment guide that we use at Clearpath Robotics, but there are other options from standards agencies like ISO, and IEC.
 

@@ -57,7 +57,7 @@ The wrong orientation will irreparably damage the motor controller.
 
 :::warning
 
-Remove jewlery and similar electrically conductive objects from your hands and arms.
+Remove jewelry and similar electrically conductive objects from your hands and arms.
 The capacitors on the motor controllers store energy even after the robot is turned off.
 Conductive objects that electrically-short the motor controller's terminals can cause shocks or burns to your hands.
 
@@ -156,7 +156,7 @@ Change the permissions to `Allow executing file as a program`.
   </center>
 </figure>
 
-Alternatively; you can add execute permissions to sflash using a termainal.
+Alternatively; you can add execute permissions to sflash using a terminal.
 Navigate to the file through a terminal, and running:
 
 ```

@@ -1,7 +1,7 @@
 In general, following these tips will help maximize the life of the battery:
 
 - Always fully charge the battery as soon as you are finished using it.
-- Charge batteries at room temperature. Never charge LiFEPO4 batteries at temperatures above 45°C or below 0°C.
+- Charge batteries at room temperature. Never charge LiFePO4 batteries at temperatures above 45°C or below 0°C.
 - Charge batteries in a well-ventilated area.
 - Do not allow the battery to freeze. Never charge a frozen battery.
 - Stored batteries should be charged and balanced every 4 -6 months.

@@ -144,7 +144,7 @@ You want to make sure the inner tube does not get pinched between the two rims i
 
 #### 9. Connect the two halves of the split-rim using the installation tool or two bolts.
 
-Note that the threaded adaper plate does on the side of the rim with the air-fill-stem.
+Note that the threaded adapter plate does on the side of the rim with the air-fill-stem.
 This adapter plate will be visible on the outside of the robot.
 
 <figure>
@@ -231,7 +231,7 @@ This will let you know if screws have loosened in service.
 #### 13. Inflate the inner tube to 138 kPa (20 psi).
 
 Bounce the tire on the floor a few times after you have inflated it, and removed the compressor.
-The bounching will help seat the tire's bead.
+The bouncing will help seat the tire's bead.
 
 :::note
 

@@ -8,7 +8,7 @@ toc_max_heading_level: 4
 
 We have enabled the ability to view, through a web browser, the robot filesystem
 for the specific version that is running. To access the file browser, either open the user
-interface, access the **Menu** &srarr; **File** &srarr; **File Broswer** or navigate to the
+interface, access the **Menu** &srarr; **File** &srarr; **File Browser** or navigate to the
 following [URL](http://192.168.131.1/_/files).
 
 <center>

@@ -25,4 +25,4 @@ the IP address of the host (UGV) computer, typically 192.168.131.1.
   </figure>
 </center>
 
-For more information on the available Foxglove panels and how to more thoroughly us it, please consult the [Foxglove documentation](https://foxglove.dev/docs/studio).
+For more information on the available Foxglove panels and how to more thoroughly use it, please consult the [Foxglove documentation](https://foxglove.dev/docs/studio).
@@ -44,7 +44,7 @@ methods that can be used to stop the moving UGV.
     to 80%.
 5.  **UI Lockout:** The lockout toggle that will prevent the Joystick from 
     sending commands to the UGV. The purpose of this is to help prevent 
-    unwanted users from teloperating the UGV.  This feature
+    unwanted users from teleoperating the UGV.  This feature
     does not lock out the controller connected to the robot.
 
 ## Remote Controller Connection
@@ -69,5 +69,5 @@ the time a command is sent and the time it is executed (and/or visible
 on the UI camera views) will increase as the distance increases. This
 effect will be further amplified by any obstacles between the UGV and
 the base (eg. walls, vehicles, mounds, etc.). It is important to monitor
-this delay an be cautious when driving the UGV with larger delay for
+this delay and be cautious when driving the UGV with larger delay for
 risk of crashing into obstacles.
@@ -25,7 +25,7 @@ The list below defines what a "Map" and "Mission" are in relation to the Map mod
 their relevant components. These terms are referred to throughout this page.
 
 - **Mission** A Mission is a set of one or more Goalpoints.
-- **Map** A Operator created map that goes over the aerial view and is used to define valid driveable
+- **Map** An Operator created map that goes over the aerial view and is used to define valid driveable
   areas for a mission.
 - **Point** A map point used to help define a path.
 - **Path** A connection between two points that the UGV can travel along for missions. Can be defined as
@@ -34,7 +34,7 @@ their relevant components. These terms are referred to throughout this page.
   position relative to the datum in meters. These points are travelled to as part of the Mission.
 - **Task** A Task is an automated activity or wait time implemented as
   a ROS action at a specific event or Goalpoint.
-- **GoToPoint** A Goalpoint that is independant of a mission. This point is meant to be a one off
+- **GoToPoint** A Goalpoint that is independent of a mission. This point is meant to be a one off
   position to send the UGV to.
 - **Ghost point** A transparent point that is not part of the map. This
   point appears between two other points when in map edit mode. The Operator can
@@ -98,7 +98,7 @@ system will automatically create a map for them with default settings.
 To add points to the map, ensure that the UI is still in "Map Edit Mode" and click on the map. This will
 add a point to the map and also trigger the "Connection Mode". The path type button (one-way/two-way) will
 turn blue to indicate that the next point that is added will be connected to the previously created point.
-A Operator may cancel this connection by pressing the ESC key or by clicking the path type button. Points can be
+An Operator may cancel this connection by pressing the ESC key or by clicking the path type button. Points can be
 dragged and dropped to adjust their positions. To delete a point, right click the point and select Delete.
 
 While in edit mode, Ghost points will appear in the center of each path that can be dragged and dropped to split the
@@ -107,12 +107,12 @@ path.
 ### Map Paths
 
 Paths are generally added as part of the Point placement process as mentioned above. However, there may be
-cases where a Operator would like to connect existing points. To accomplish this, simply exit out of connection mode
+cases where an Operator would like to connect existing points. To accomplish this, simply exit out of connection mode
 then click on the existing points. Once the first point is clicked on, connection mode will be re-established with
 the previously clicked point as the starting location.
 
 As paths are added they will be visible in the Map properties table, along with their relevant details. To edit a
-path's details a Operator can simply right click on the path or select the gear icon for the specific path in the table.
+path's details an Operator can simply right click on the path or select the gear icon for the specific path in the table.
 This will open an overlay on the map that will allow the Operator to edit both one-way paths and two-way paths. In the
 case of two-way paths users can keep both ways in sync with each other or vary the properties depending on the
 direction.
@@ -147,7 +147,7 @@ modified. Press enter/click aside to save the change.
 ### Map Defaults
 
 When adding paths the map uses defined default values to set the maximum driving radius
-and speed limit. If a Operator wishes to adjust these defaults this can be done here. This will
+and speed limit. If an Operator wishes to adjust these defaults this can be done here. This will
 only affect paths created after the changes have been made.
 
 ### Network Path Recorder
@@ -225,7 +225,7 @@ modified. Press enter/click aside to save the change.
 
 ### Return to Dock
 
-A Operator may wish to add a flag to the mission to indicate when and if the UGV should
+An Operator may wish to add a flag to the mission to indicate when and if the UGV should
 return to the dock while executing the mission. When enabled, the Operator can input a
 battery percentage that once reached the UGV will begin navigating back to the specified
 dock or to the closest dock. They can then set the minimum battery life before the UGV
@@ -266,7 +266,7 @@ To add a Task to a Goalpoint:
 
 4.  The check box next to the Task name controls mission behaviour in the event that the Task fails. If the checkbox is
     checked the Mission will proceed to the next step in it's process, such as the next task or navigating to the next Goalpoint.
-    If its not checked, the Mission will become cancelled upon the Task's failure.
+    If it's not checked, the Mission will become cancelled upon the Task's failure.
 
 5.  Click the Gear icon next to the selected Task to modify or add required Task testings.
 

@@ -6,7 +6,7 @@ toc_min_heading_level: 2
 toc_max_heading_level: 4
 ---
 
-The Web User Interface (Web UI) provides a easy, graphical, means to
+The Web User Interface (Web UI) provides an easy, graphical, means to
 control both manual and autonomous operation of your UGV. The following
 sections outline: the components and views of the UI, the details of
 operating in manual mode, and the details of operating in autonomous
@@ -92,7 +92,7 @@ Operator can access the following views:
     is activity (ie. where the datum is set or where features have been
     set on the map.)
 3.  **Table Button:** This button opens the Map/Mission table. When in Waypoint Mode it will open the table directly, while in
-    Map mode it will allow users to select the table to open or open a table based on which mode is being editted.
+    Map mode it will allow users to select the table to open or open a table based on which mode is being edited.
 4.  **Edit Mode Buttons:** This button will allow the user to set the current map edit mode.  
     By clicking the button, a panel opens on the right with the available modes to edit with.
     <center>

@@ -214,7 +214,7 @@ The pins should be connected as follows:
 - 1: 12 V @ 500mA max
 - 2: GND
 
-Then, the use can publish a ROS message to the `/mcu/fans` topic to control the fan.
+Then, the user can publish a ROS message to the `/mcu/fans` topic to control the fan.
 
 #### Optional External Motion Stop {#dingo-external-motion-stop}
 

@@ -22,7 +22,7 @@ Refer to the [Networking page](/docs/ros/networking/overview).
 
 ### Cannot connect to the robot's computer over a network cable
 
-Reter to the [Networking page](/docs/ros/networking/overview).
+Refer to the [Networking page](/docs/ros/networking/overview).
 
 ---
 
@@ -42,7 +42,7 @@ Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_it
 
 ### ROS package is not starting
 
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
+Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any errors during upstart.
 
 ### Sensors are not turning on
 

@@ -14,7 +14,7 @@ import Support from "/components/support.mdx";
 
 ### Introduction
 
-Dingo a lightweight and easy-to-use unmanned indoor ground vehicle for ROS, suitable for research and rapid prototyping applications.
+Dingo is a lightweight and easy-to-use unmanned indoor ground vehicle for ROS, suitable for research and rapid prototyping applications.
 These tutorials will assist you with setting up and operating your Dingo.
 
 For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/dingo).

@@ -21,7 +21,7 @@ It may also be necessary to remove the antenna cables carefully prior to removin
 
 ## Long-term storage
 
-When storing Ridgeback for long periods of time, its important to properly maintain the batteries to fully
+When storing Ridgeback for long periods of time, it's important to properly maintain the batteries to fully
 maximize their life. Consider one of the following two procedures when placing Ridgeback in long-term storage:
 
 - Fully charge Ridgeback, turn it off and put it into storage. Once a week, connect power to the charger

@@ -22,7 +22,7 @@ Refer to the [Networking page](/docs/ros/networking/overview).
 
 ### Cannot connect to the robot's computer over a network cable
 
-Reter to the [Networking page](/docs/ros/networking/overview).
+Refer to the [Networking page](/docs/ros/networking/overview).
 
 ---
 
@@ -42,7 +42,7 @@ Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_it
 
 ### ROS package is not starting
 
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
+Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any errors during upstart.
 
 ### Sensors are not turning on
 

@@ -97,7 +97,7 @@ Lower tire pressures, for example 68.5 kPa (10 psi), ensure better traction in r
 or other obstacles may be encountered. This has the adverse effect of lowering drivetrain efficiency and decreasing
 battery charge, so high pressures up to a maximum of 137 kPa (20 psi) should be used when driving on flat surfaces.
 
-Lower tire pressuses also reduce the effective diameter of the wheel, and will impact your odometry readings.
+Lower tire pressures also reduce the effective diameter of the wheel, and will impact your odometry readings.
 Odometry is calculated using the average diameter of a tire inflated to 137 kPa (20 psi).
 
 :::