Browse Source

APMrover2: Fix typos

mission-4.1.18
Ricardo de Almeida Gonzaga 9 years ago committed by Lucas De Marchi
parent
commit
63f2ab38dd
  1. 2
      APMrover2/commands_logic.cpp
  2. 2
      APMrover2/release-notes.txt

2
APMrover2/commands_logic.cpp

@ -225,7 +225,7 @@ bool Rover::verify_nav_wp(const AP_Mission::Mission_Command& cmd) @@ -225,7 +225,7 @@ bool Rover::verify_nav_wp(const AP_Mission::Mission_Command& cmd)
// We should always go through the waypoint i.e. the above code
// first before we go past it.
if (location_passed_point(current_loc, prev_WP, next_WP)) {
// check if we have gone futher past the wp then last time and output new message if we have
// check if we have gone further past the wp then last time and output new message if we have
if ((uint32_t)distance_past_wp != (uint32_t)get_distance(current_loc, next_WP)) {
distance_past_wp = get_distance(current_loc, next_WP);
gcs_send_text_fmt(MAV_SEVERITY_INFO, "Passed waypoint #%i. Distance %um",

2
APMrover2/release-notes.txt

@ -329,7 +329,7 @@ The changes in this release are: @@ -329,7 +329,7 @@ The changes in this release are:
The most important bug fix is the one for short term loss of RC
control. This is a very long standing bug which didn't have a
noticible impact for most people, but could cause loss of RC control
noticeable impact for most people, but could cause loss of RC control
for around 1 or 2 seconds for some people in certain circumstances.
The bug was in the the AP_HAL RCInput API. Each HAL backend has a flag

Loading…
Cancel
Save