diff --git a/ko/FlyView/FlyView.md b/ko/FlyView/FlyView.md
index 44d29347b..b5efe6566 100644
--- a/ko/FlyView/FlyView.md
+++ b/ko/FlyView/FlyView.md
@@ -22,7 +22,7 @@ The screenshot above shows the main elements of the fly view:
- **Fly Toolbar:** Key status information for sensors (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status).
- Select the sensor indicators to view more detail.
- Press the *Flight mode* text (e.g. "Hold") to select a new mode. Not every mode may be available.
- - Press the *Armed/Disarmed* text to toggle the armed state. If flying you can press this text to *Emergency Stop*.
+ - Press the *Armed/Disarmed* text to toggle the armed state. While flying you can press this text for *Emergency Stop*.
- **Fly tools:** You can use these to:
- Toggle between takeoff/land.
- Pause/restart the current operation (e.g. landing, or the mission).
@@ -32,7 +32,7 @@ The screenshot above shows the main elements of the fly view:
- **[Instrument Panel](#instrument_panel):** A multi-page widget that displays vehicle information including: telemetry, camera, video, system health, and vibration.
- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window.
- Press the element to switch *Video* and *Map* to foreground.
- - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. It also support directly connected UVC device support. QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
+ - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. It also supports directly connected UVC devices. QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
- A [Telemetry Overlay](../FlyView/VideoOverlay.md) is automatically generated as a subtitle file
- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Slide to start operation. Press **X** to cancel.
@@ -42,7 +42,7 @@ There are a number of other elements that are not displayed by default/are only
The instrument panel is a multi-page widget that displays information about the current vehicle, including: telemetry, camera, video, system health, and vibration information.
-The default page displays vehicle telemetry - use the drop down menu on the to right to select the other options.
+The default page displays vehicle telemetry - use the drop down menu on the top right to select the other options.
### Values (Telemetry)
@@ -78,7 +78,7 @@ The video page is used to enable/disable video streaming. When enabled, you can
### Health
-The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any systems change to unhealthy.
+The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any system changes to unhealthy.
 
@@ -98,11 +98,11 @@ The following sections describe how to perform common operations/tasks in the Fl
An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly.
-To you the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
+To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
-Once you have performed each test, select it on it in the UI to mark it as complete.
+Once you have performed each test, select it on the UI to mark it as complete.
### Arm {#arm}
@@ -126,7 +126,7 @@ Disarming the vehicle stops the motors (making the vehicle safe). To disarm the
### Emergency Stop {#emergency_stop}
-Emergency stop is effectively the same as disarming the vehicle while you are flying. Your vehicle will crash!
+Emergency stop is effectively the same as disarming the vehicle while it is flying. Your vehicle will crash!
To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is flying.
@@ -134,7 +134,7 @@ To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is
### Takeoff {#takeoff}
-> **Tip** If you are starting a mission for a multicopter *QGroundControl* will automatically perform the takeoff step.
+> **Tip** If you are starting a mission for a multicopter, *QGroundControl* will automatically perform the takeoff step.
To takeoff (when landed):
@@ -155,14 +155,14 @@ You can land at the current position at any time while flying:
### RTL/Return
-Return to the home position at any time while flying:
+Return to a "safe point" at any time while flying:
1. Press the **RTL** button in the *Fly Tools*.
2. Confirm RTL using the slider.
-
+
-> **Note** The vehicle may also land at the home position, depending on its type and configuration.
+> **Note** Vehicles commonly return to the "home" (takeoff) location and land. This behaviour depends on the vehicle type and configuration. For example, rally points or mission landings may be used as alternative return targets.
### Change Altitude {#change_altitude}
@@ -181,7 +181,7 @@ You can change altitude while flying, except when in a mission:
After taking off you can specify that you want to fly to a particular location.
-1. Press the map where you want the vehicle to move and select **Go to location** on the popup.
+1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup.
@@ -197,7 +197,7 @@ After taking off you can specify that you want to fly to a particular location.
After taking off you can specify that you want to orbit a particular location.
-1. Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
+1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
@@ -211,7 +211,7 @@ After taking off you can specify that you want to orbit a particular location.
### Pause
-You can pause most operations, including taking off, landing, RTL, missions, Orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
+You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
> **Note** You cannot pause a *Goto location* operation.
@@ -247,7 +247,7 @@ To start a mission from landed:
You can *continue* mission from the *next* waypoint when you're flying (the *Continue Mission* confirmation slider is often displayed by default after you takeoff).
-> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from you place in the mission).
+> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission).
You can continue the current mission while (unless already in a mission!):
@@ -284,7 +284,7 @@ You will be prompted to remove the mission from the vehicle after the mission co
### Display Video {#video_switcher}
-When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (below we show the video in the foreground).
+When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (in the image below, the video is shown in the foreground).
@@ -295,7 +295,7 @@ You can further configure video display using controls on the switcher:
-- Resize the switcher by dragging the icon in the to right corner.
+- Resize the switcher by dragging the icon in the top right corner.
- Hide the switcher by pressing the toggle icon in the lower left.
- Detach the video switcher window by pressing on the icon in its top left corner (once detached, you can move and resize the window just like any other in your OS). If you close the detached window the switcher will re-lock to the QGC Fly view.
diff --git a/ko/FlyView/VideoOverlay.md b/ko/FlyView/VideoOverlay.md
index 081fd5dbc..bccb9895c 100644
--- a/ko/FlyView/VideoOverlay.md
+++ b/ko/FlyView/VideoOverlay.md
@@ -1,6 +1,6 @@
# Video Overlay
-When QGroundControl is recording a video stream to file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
+When QGroundControl is recording a video stream to a file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
diff --git a/ko/FlyView/replay_flight_data.md b/ko/FlyView/replay_flight_data.md
index 3b0a8b08a..b2af57ad7 100644
--- a/ko/FlyView/replay_flight_data.md
+++ b/ko/FlyView/replay_flight_data.md
@@ -2,7 +2,7 @@
> **Warning** This feature is intended primarily for **autopilot developers**/**vehicle creators**. It is only supported on desktop builds (Windows, Linux, Mac OS).
-The *Replay Flight Data* features allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
+The *Replay Flight Data* feature allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
> **Note** *QGroundControl* treats flight replay like an active connection. When you pause/stop playing, the ground station will report "Communication Lost" and wait for disconnection or for more messages.
@@ -18,7 +18,7 @@ To replay a flight:
1. When a log is loaded you can use the:
- **Pause/Play** button to pause and restart playing.
- *Slider* to drag to a new position in the log.
- - *Rate* selector to choose how quickly the log is run.
-1. To stop relay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting the **Load Telemetry Log** button will be displayed.
+ - *Rate* selector to choose the playback speed.
+1. To stop replay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting, the **Load Telemetry Log** button will be displayed.
> **Tip** You can inspect the running replay in more detail using the [MAVLink Inspector](../analyze_view/mavlink_inspector.md).
diff --git a/ko/PlanView/Pattern.md b/ko/PlanView/Pattern.md
index fd3fcd5a4..334b6e235 100644
--- a/ko/PlanView/Pattern.md
+++ b/ko/PlanView/Pattern.md
@@ -9,6 +9,6 @@ The *Pattern tools* (in the [PlanView](../PlanView/PlanView.md) *Plan Tools*) al
| [Survey](../PlanView/pattern_survey.md) | Create a grid flight pattern over a polygonal area.
You can specify the polygon as well as the specifications for the grid and camera settings appropriate for creating geotagged images. | All |
| [Structure Scan](../PlanView/pattern_structure_scan_v2.md) | Create a grid flight pattern that captures images over vertical surfaces (polygonal or circular).
-These are typically used for the visual inspection or creation of 3d models of structures. | MultiCopter, VTOL |
+These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL |
| [Corridor Scan](../PlanView/pattern_corridor_scan.md) | Create a flight pattern which follows a poly-line (for example, to survey a road). | All |
| [Fixed Wing Landing](../PlanView/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing |
\ No newline at end of file
diff --git a/ko/PlanView/PatternPresets.md b/ko/PlanView/PatternPresets.md
index ec58ca1ee..fd5718284 100644
--- a/ko/PlanView/PatternPresets.md
+++ b/ko/PlanView/PatternPresets.md
@@ -29,4 +29,4 @@ If you want to view what the exact settings are for a Preset switch back to **Cu
## Presets In A Plan File
-The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user incorrect behavior may occur if that other user also have a preset of the same name but different settings.
\ No newline at end of file
+The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user, incorrect behavior may occur if that other user also has a preset of the same name but different settings.
\ No newline at end of file
diff --git a/ko/PlanView/PlanGeoFence.md b/ko/PlanView/PlanGeoFence.md
index 89e856ccd..5a4c4df39 100644
--- a/ko/PlanView/PlanGeoFence.md
+++ b/ko/PlanView/PlanGeoFence.md
@@ -15,7 +15,7 @@ To create a GeoFence:
-3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** buttons, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
+3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** button, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
> **Tip** You can create multiple regions by pressing the buttons multiple times, allowing complex geofence definitions to be created.
@@ -24,7 +24,7 @@ To create a GeoFence:
- Move the region by dragging the central dot on the map
- - Resize the circle by dragging the map dot on the edge of the circle (or you can change the radius value in the fence panel).
+ - Resize the circle by dragging the dot on the edge of the circle (or you can change the radius value in the fence panel).
- Polygon region:
@@ -38,7 +38,7 @@ To create a GeoFence:
You can select a geofence region to edit by selecting its *Edit* radio button in the GeoFence panel. You can then edit the region on the map as described in the previous section.
-Regions can be deleted by pressing the associated **Del** button
+Regions can be deleted by pressing the associated **Del** button.
## Upload a GeoFence
diff --git a/ko/PlanView/PlanView.md b/ko/PlanView/PlanView.md
index 283be976e..be87510e8 100644
--- a/ko/PlanView/PlanView.md
+++ b/ko/PlanView/PlanView.md
@@ -36,7 +36,7 @@ The following sections explain some of the details in the view.
## Planned Home Position {#planned_home}
-The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to a vehicle). It is used by QGC to estimate mission times and to draw waypoint lines.
+The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC). It is used by QGC to estimate mission times and to draw waypoint lines.
@@ -44,7 +44,7 @@ You should move/drag the planned home position to roughly the location where you
-> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this where the vehicle will return in Return/RTL mode).
+> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
## Plan Tools {#plan_tools}
@@ -124,7 +124,7 @@ The [Planned Home Position](#planned_home) section allows you to simulate the ve
> **Note** This is only the *planned* home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming.
-The section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
+This section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
#### Camera
diff --git a/ko/PlanView/pattern_fixed_wing_landing.md b/ko/PlanView/pattern_fixed_wing_landing.md
index 765bf486e..43a12d2a9 100644
--- a/ko/PlanView/pattern_fixed_wing_landing.md
+++ b/ko/PlanView/pattern_fixed_wing_landing.md
@@ -12,7 +12,7 @@ Both the loiter and land points can be dragged to new positions, and a number of
To create a landing pattern:
-1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*).
+1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*.
2. Choose the *Pattern Tool* from the *Plan Tools* and then select *Fixed Wing Landing Pattern*.
@@ -21,7 +21,7 @@ To create a landing pattern:
-3. Click on the map to create both the loiter and landing points. These can be moved on the map.
+3. Click on the map to create both the loiter point and the landing point. These can be moved on the map.
Additional settings are covered in the next section.
@@ -52,8 +52,8 @@ The configurable options are:
- **Heading** - Heading from loiter point to land point.
- **Altitude** - Altitude for landing point (nominally zero).
- *Radio Buttons*
- - **Landing Dist** - Distance between loiter and landing points.
- - **Glide Slope** - Glide slope between loiter and landing points.
+ - **Landing Dist** - Distance between loiter point and landing point.
+ - **Glide Slope** - Glide slope between loiter point and landing point.
- **Altitudes relative to home** - Check to set all altitudes in mission item to be relative to home (default is AMSL).
## Implementation
diff --git a/ko/PlanView/pattern_structure_scan_v2.md b/ko/PlanView/pattern_structure_scan_v2.md
index 60d90ebbd..486d4bdcb 100644
--- a/ko/PlanView/pattern_structure_scan_v2.md
+++ b/ko/PlanView/pattern_structure_scan_v2.md
@@ -1,6 +1,6 @@
# Structure Scan (Plan Pattern)
-A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3d models of structures.
+A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3D models of structures.
*Structure Scans* may be inserted into a mission using the Plan view **Pattern > Structure Scan** tool.
@@ -58,7 +58,7 @@ The user can always configure the following settings:
- **Start scan from top/bottom:** The direction in which layers are scanned.
- **Structure height:** The height of the object being scanned.
-- **Scan distance:** Distance from the structure of the flight path.
+- **Scan distance:** Distance from the structure to the flight path.
- **Entrance/Exit Alt:** Use this setting to avoid obstacles between the last/next waypoint and the structure to be scanned.
- The vehicle will fly to the *Entrance/Exit* point at this altitude and then descend to the initial layer to start the scan.
- The vehicle will ascend to this altitude after completing the scan and then move to the next waypoint.
@@ -72,13 +72,13 @@ The remaining settings depend on the *camera mode*:
- **Trigger Distance:** The distance between each camera trigger. The camera is only triggered while flying the layer path. It does not trigger images while transitioning from one layer to the next.
- **Gimbal Pitch** - Gimbal pitch you want to use for the scan.
-- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is always pointed directly at the right angles to the surface which it is capturing images. The settings are:
+- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is pointed directly at the surface when it is capturing images (i.e. at a right angle rather than some tangent). The settings are:
- **Camera Orientation:** Portrait or Landscape
- *Overlap*:
- **Front Lap:** Image overlap from top to bottom (increasing shrinks layer height and increases layer count).
- **Side Lap:** Image overlap at sides (increasing takes more images in each lap/layer scan).
- - **Scan distance:** Distance from the structure of the flight path.
+ - **Scan distance:** Distance from the structure to the flight path.
- **Ground Res:** Required image resolution/sample quality of surface.
- *Custom camera* selection allows you to enter your own camera characteristics, but otherwise behaves the same as a predefined camera.
\ No newline at end of file
diff --git a/ko/PlanView/pattern_survey.md b/ko/PlanView/pattern_survey.md
index d61481457..bed02fab1 100644
--- a/ko/PlanView/pattern_survey.md
+++ b/ko/PlanView/pattern_survey.md
@@ -21,7 +21,7 @@ To create a survey:
This will add a survey grid to the map, and a *Survey* item to the mission list (on the right).
-3. On the map drag the vertices to the change the shape of the polygon.
+3. On the map drag the vertices to change the shape of the polygon.
4. Click the `(+)` symbol between existing vertices to create a new vertix. The new vertix can then be dragged into a new position.
diff --git a/ko/SettingsView/General.md b/ko/SettingsView/General.md
index 3e4e44181..254bce4d8 100644
--- a/ko/SettingsView/General.md
+++ b/ko/SettingsView/General.md
@@ -15,7 +15,7 @@ This section defines the display units used in the application.
The settings are:
- **Distance**: Meters | Feet
-- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres |SquareMiles
+- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres | SquareMiles
- **Speed**: Metres/second | Feet/second | Miles/hour | Kilometres/hour | Knots
- **Temperature**: Celsius | Fahrenheit
diff --git a/ko/SettingsView/OfflineMaps.md b/ko/SettingsView/OfflineMaps.md
index fb2a8407e..8165f0f96 100644
--- a/ko/SettingsView/OfflineMaps.md
+++ b/ko/SettingsView/OfflineMaps.md
@@ -2,12 +2,12 @@
-Offline Maps allows you to cache map tiles for use when not connected to the internet. You can create multiple offline sets, each for a different location.
+Offline Maps allows you to cache map tiles for use when not connected to the Internet. You can create multiple offline sets, each for a different location.
## Add new set
To create a new offline map set, click "Add new set". Which will take you to this page: 
-From here you can name you set as well as specify the zoom levels you want to cache. Move the map to the position you can to cache and then set the zoom levels and click Download to cache the tiles.
+From here you can name your set as well as specify the zoom levels you want to cache. Move the map to the position you want to cache and then set the zoom levels and click Download to cache the tiles.
To the left you can see previews of the min and max zoom levels you have chosen.
\ No newline at end of file
diff --git a/ko/SetupView/Firmware.md b/ko/SetupView/Firmware.md
index 6e31a6fb8..c06360457 100644
--- a/ko/SetupView/Firmware.md
+++ b/ko/SetupView/Firmware.md
@@ -8,7 +8,7 @@
## Connect Device for Firmware Update
-> **Caution** **Before you start installing Firmware** all USB connections to you vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
+> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
1. First select the **Gear** icon (*Vehicle Setup*) in the top toolbar and then **Firmware** in the sidebar.
@@ -26,7 +26,7 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
- If you select *ArduPilot* you will also have to choose the specific firmware the type of vehicle (as shown below).
+ If you select *ArduPilot* you will also have to choose the specific firmware and the type of vehicle (as shown below).
@@ -42,4 +42,4 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
-Once the firmware has completed loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
+Once the firmware has finished loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
diff --git a/ko/SetupView/FlightModes.md b/ko/SetupView/FlightModes.md
index 18d026577..dbbfae538 100644
--- a/ko/SetupView/FlightModes.md
+++ b/ko/SetupView/FlightModes.md
@@ -19,7 +19,7 @@ To access this section, select the **Gear** icon (Vehicle Setup) in the top tool
On ArduPilot you can assign up to 6 different flight modes to a single channel of your transmitter (the channel is selectable on Plane, but fixed to channel 5 on Copter).
-ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: \[Auxiliary Function Switches\](
+ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: [Auxiliary Function Switches](https://ardupilot.org/copter/docs/channel-7-and-8-options.html#channel-7-and-8-options)
To set the flight modes:
@@ -50,7 +50,7 @@ All values are automatically saved as they are changed.
- **Single Channel Mode Selection:** Assign up to 6 flight modes to switch positions encoded in a single channel.
- **Multi Channel Mode Selection:** Assign modes to switch positions encoded in one or more channels. Some modes are hard coded to share channels, or are defined/set automatically based on other mode selections (the behaviour of multi-channel mode selection can sometimes be confusing).
-> **Tip** The recommended approach is use *Single Channel Mode Selection* because it easy to understand and configure. It is similar to the approach used by ArduPilot.
+> **Tip** The recommended approach is to use *Single Channel Mode Selection* because it is easy to understand and configure. It is similar to the approach used by ArduPilot.
### Single-Channel Mode {#single_channel}
@@ -85,7 +85,7 @@ It is common to use the positions of a 2- and a 3-position switch on the transmi
The video below shows how this is done with the *FrSky Taranis* transmitter (a very popular and highly recommended RC transmitter). The process involves assigning a "logical switch" to each combination of positions of the two real switches. Each logical switch is then assigned to a different PWM value on the same channel.
-
+
The video then shows how to use *QGroundControl* to specify the mode channel and map modes to each of the 6 "slots". {% youtube %} http://www.youtube.com/watch?v=scqO7vbH2jo {% endyoutube %}
### Multi-Channel Mode
diff --git a/ko/SetupView/Joystick.md b/ko/SetupView/Joystick.md
index f719efb77..7e8fa169e 100644
--- a/ko/SetupView/Joystick.md
+++ b/ko/SetupView/Joystick.md
@@ -109,7 +109,7 @@ The following joysticks/controllers have been shown to work with relatively rece
### Sony Playstation 3/4 Controllers
-These are both highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
+Both these joysticks are highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
#### Sony PS4 - DualShock 4 Controller V2 (Wireless setup)
diff --git a/ko/SetupView/airframe_px4.md b/ko/SetupView/airframe_px4.md
index 83ef87c3d..89620f8b8 100644
--- a/ko/SetupView/airframe_px4.md
+++ b/ko/SetupView/airframe_px4.md
@@ -10,7 +10,7 @@ To select the airframe in PX4:
The example above shows *Generic Hexarotor X geometry* selected from the *Hexarotor X* group.
-4. Click the **Apply and Restart** button to the top right of the screen.
+4. Click the **Apply and Restart** button on the top right of the screen.
5. Click **Apply** in the following prompt to save the settings and restart the vehicle.
diff --git a/ko/SetupView/sensors_ardupilot.md b/ko/SetupView/sensors_ardupilot.md
index 586ada197..163a6c138 100644
--- a/ko/SetupView/sensors_ardupilot.md
+++ b/ko/SetupView/sensors_ardupilot.md
@@ -56,7 +56,7 @@ To perform **Pressure** calibration:
## CompassMot (Optional)
-CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and where there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
+CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and when there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
To perform **CompassMot** calibration:
diff --git a/ko/SetupView/sensors_px4.md b/ko/SetupView/sensors_px4.md
index a8ce3f3b9..76c5ccd9d 100644
--- a/ko/SetupView/sensors_px4.md
+++ b/ko/SetupView/sensors_px4.md
@@ -37,9 +37,9 @@ The calibration steps are:
-4. When finished, *QGroundControl* will display a progress bar *Calibration complete* 
+4. When finished, *QGroundControl* will display *Calibration complete* and the progress bar will fill completely. 
-> **Note** If you move the vehicle *QGroundControl* will automatically restart the calibration.
+> **Note** If you move the vehicle during calibration, *QGroundControl* will automatically restart the calibration.
You can then proceed to the next sensor.
diff --git a/ko/SetupView/tuning_px4.md b/ko/SetupView/tuning_px4.md
index 38b54c7c7..9352d2a29 100644
--- a/ko/SetupView/tuning_px4.md
+++ b/ko/SetupView/tuning_px4.md
@@ -17,7 +17,7 @@ To use advanced tuning:
1. First select the *Tuning axis* to tune: **Rol**, **Pitch** or **Yaw** (each axis is tuned separately).
2. Fly the vehicle, observing the tracking on the chart.
- Adjust the *Tuning Values* (parameters) to improve the tracking shown on the graph
- - Set the **Increment/Decrement %** to a larger/smaller value for course/fine tuning
+ - Set the **Increment/Decrement %** to a larger/smaller value for coarse/fine tuning
- Press the **Save Values** button if a change improves tracking. > **Tip** At any point you can press **Reset To Saved Values** to restore the last saved good state.
- You can also **Clear**/**Stop** the chart using the buttons provided.
3. Tune the other axes.
\ No newline at end of file
diff --git a/ko/analyze_view/README.md b/ko/analyze_view/README.md
index 19b5d215e..6276b4f8e 100644
--- a/ko/analyze_view/README.md
+++ b/ko/analyze_view/README.md
@@ -9,5 +9,4 @@ The view provides tools to:
* [Download Logs](../analyze_view/log_download.md) — List, download and clear logs on the vehicle.
* [GeoTag Images (PX4)](../analyze_view/geotag_images.md) — Geotag survey mission images using the flight log (on a computer).
* [MAVLink Console (PX4)](../analyze_view/mavlink_console.md) — Access the the nsh shell running on the vehicle.
-* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
-* Vibration clip count
\ No newline at end of file
+* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
\ No newline at end of file
diff --git a/ko/getting_started/download_and_install.md b/ko/getting_started/download_and_install.md
index 820afa94a..560fb107d 100644
--- a/ko/getting_started/download_and_install.md
+++ b/ko/getting_started/download_and_install.md
@@ -1,6 +1,6 @@
# Download and Install
-The sections below can be used download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
+The sections below can be used to download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
> **Tip** See [QGC Install/Config Problems](../Support/troubleshooting_qgc.md) if you have any problem running *QGroundControl* after installation!
diff --git a/ko/getting_started/quick_start.md b/ko/getting_started/quick_start.md
index e6f2f495f..8c261db3b 100644
--- a/ko/getting_started/quick_start.md
+++ b/ko/getting_started/quick_start.md
@@ -17,6 +17,7 @@ A good way to become familiar with *QGroundControl* is to start experimenting:
- [Setup](../SetupView/SetupView.md): Configure and tune your vehicle.
- [Plan](../PlanView/PlanView.md): Create autonomous missions.
- [Fly](../FlyView/FlyView.md): Monitor your vehicle(s) while flying, including streaming video.
+ - [Analyze] ** Description of Analyze view is missing **
- Click the *Status icons* on the toolbar to find out the status of the connected vehicle.
While the UI is fairly intuitive, this documentation can also be referenced to find out more.
\ No newline at end of file
diff --git a/ko/toolbar/toolbar.md b/ko/toolbar/toolbar.md
index bdb93bcc4..d667025a0 100644
--- a/ko/toolbar/toolbar.md
+++ b/ko/toolbar/toolbar.md
@@ -12,7 +12,7 @@ The following icons are used to switch between the main *Views*. These are displ
 **[Plan](../PlanView/PlanView.md)**
Create autonomous missions.
- **[Fly](../FlyView/FlyView.md)**
Monitor you vehicle(s) while flying, including streaming video.
+ **[Fly](../FlyView/FlyView.md)**
Monitor your vehicle(s) while flying, including streaming video.
 **[Analyze](../analyze_view/README.md)**
Download logs, geotag images from a survey mission, access the MAVLink console.
@@ -20,11 +20,11 @@ The following icons are used to switch between the main *Views*. These are displ
Status icons are displayed when *QGroundControl* is connected to a vehicle. These show the high level status of the vehicle, and can be clicked to see more detailed information.
- **Vehicle Messages**
Click to show a dropdown of messages from the vehicle. This will change to a Yield sign if there are critical messages.
+  **Vehicle Messages**
Click to show a list of messages from the vehicle. Note that version on the right is displayed when there are critical messages.
- **GPS Status**
Shows you satellite count and curent hdop.
+ **GPS Status**
Shows you satellite count and curent HDOP.
- **RC RSSI**
RS signal strength information.
+ **RC RSSI**
RC signal strength information.
 **Telemetry RSSI**
Telemetry signals strength information.
diff --git a/ru/FlyView/FlyView.md b/ru/FlyView/FlyView.md
index a258f7cc6..50d52cff3 100644
--- a/ru/FlyView/FlyView.md
+++ b/ru/FlyView/FlyView.md
@@ -22,7 +22,7 @@
- **Панель инструментов:** Информация о ключевом статусе датчиков (GPS, аккумулятора, управления РК) и состояния транспортного средства (режим полета, состояние "Армян/разоружен").
- Выберите индикаторы датчика для более подробного просмотра.
- Нажмите *Режим полета* текст (например, "Задержать") для выбора нового режима. Не каждый режим может быть доступен.
- - Нажмите *Armed/Disarmed* текст для переключения вооруженного состояния. При полете вы можете нажать этот текст на *аварийная остановка*.
+ - Нажмите *Armed/Disarmed* текст для переключения вооруженного состояния. While flying you can press this text for *Emergency Stop*.
- **Панель управление полетом:** Вы можете использовать его для:
- Переключение между взлет/посадка.
- Пауза/перезапуск текущую операцию (например, посадку или миссию).
@@ -32,7 +32,7 @@
- **[Панель инструментов](#instrument_panel):** многостраничный виджет с информацией о БПЛА, включающий в себя: телеметрию, камеру, видео, общее состояние системы и вибрацию.
- **[Video/Switcher](#video_switcher):** Переключение между видео или картой в окне.
- Нажмите на элемент для переключения *Видео* и *Карта* для переключения на передний план.
- - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. Также поддерживается поддержка устройств UVC. Поддержка видео QGC обсуждается в [Видео README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
+ - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. It also supports directly connected UVC devices. Поддержка видео QGC обсуждается в [Видео README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
- A [Telemetry Overlay](../FlyView/VideoOverlay.md) is automatically generated as a subtitle file
- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Проведите для начала операции. Нажмите **X** для отмены.
@@ -42,7 +42,7 @@
Это многостраничный виджет с информацией о БПЛА, включающий в себя: телеметрию, камеру, видео, общее состояние системы и вибрацию.
-По умолчанию отображается телеметрия БПЛА - используйте выпадающее меню справа для выбора других параметров.
+The default page displays vehicle telemetry - use the drop down menu on the top right to select the other options.
### Значения (Телеметрия)
@@ -78,7 +78,7 @@ The video page is used to enable/disable video streaming. When enabled, you can
### Health
-The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any systems change to unhealthy.
+The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any system changes to unhealthy.
 
@@ -98,11 +98,11 @@ The following sections describe how to perform common operations/tasks in the Fl
An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly.
-To you the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
+To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
-Once you have performed each test, select it on it in the UI to mark it as complete.
+Once you have performed each test, select it on the UI to mark it as complete.
### Arm {#arm}
@@ -126,7 +126,7 @@ Disarming the vehicle stops the motors (making the vehicle safe). To disarm the
### Emergency Stop {#emergency_stop}
-Emergency stop is effectively the same as disarming the vehicle while you are flying. Your vehicle will crash!
+Emergency stop is effectively the same as disarming the vehicle while it is flying. Your vehicle will crash!
To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is flying.
@@ -134,7 +134,7 @@ To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is
### Взлет {#takeoff}
-> **Tip** If you are starting a mission for a multicopter *QGroundControl* will automatically perform the takeoff step.
+> **Tip** If you are starting a mission for a multicopter, *QGroundControl* will automatically perform the takeoff step.
To takeoff (when landed):
@@ -155,14 +155,14 @@ You can land at the current position at any time while flying:
### RTL/Возврат
-Return to the home position at any time while flying:
+Return to a "safe point" at any time while flying:
1. Press the **RTL** button in the *Fly Tools*.
2. Confirm RTL using the slider.
-
+
-> **Note** The vehicle may also land at the home position, depending on its type and configuration.
+> **Note** Vehicles commonly return to the "home" (takeoff) location and land. This behaviour depends on the vehicle type and configuration. For example, rally points or mission landings may be used as alternative return targets.
### Смена высоты {#change_altitude}
@@ -181,7 +181,7 @@ You can change altitude while flying, except when in a mission:
After taking off you can specify that you want to fly to a particular location.
-1. Press the map where you want the vehicle to move and select **Go to location** on the popup.
+1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup.
@@ -197,7 +197,7 @@ After taking off you can specify that you want to fly to a particular location.
After taking off you can specify that you want to orbit a particular location.
-1. Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
+1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
@@ -211,7 +211,7 @@ After taking off you can specify that you want to orbit a particular location.
### Пауза
-You can pause most operations, including taking off, landing, RTL, missions, Orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
+You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
> **Note** You cannot pause a *Goto location* operation.
@@ -247,7 +247,7 @@ To start a mission from landed:
You can *continue* mission from the *next* waypoint when you're flying (the *Continue Mission* confirmation slider is often displayed by default after you takeoff).
-> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from you place in the mission).
+> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission).
You can continue the current mission while (unless already in a mission!):
@@ -284,7 +284,7 @@ You will be prompted to remove the mission from the vehicle after the mission co
### Показ видео {#video_switcher}
-When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (below we show the video in the foreground).
+When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (in the image below, the video is shown in the foreground).
@@ -295,7 +295,7 @@ You can further configure video display using controls on the switcher:
-- Resize the switcher by dragging the icon in the to right corner.
+- Resize the switcher by dragging the icon in the top right corner.
- Hide the switcher by pressing the toggle icon in the lower left.
- Detach the video switcher window by pressing on the icon in its top left corner (once detached, you can move and resize the window just like any other in your OS). If you close the detached window the switcher will re-lock to the QGC Fly view.
diff --git a/ru/FlyView/VideoOverlay.md b/ru/FlyView/VideoOverlay.md
index 081fd5dbc..bccb9895c 100644
--- a/ru/FlyView/VideoOverlay.md
+++ b/ru/FlyView/VideoOverlay.md
@@ -1,6 +1,6 @@
# Video Overlay
-When QGroundControl is recording a video stream to file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
+When QGroundControl is recording a video stream to a file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
diff --git a/ru/FlyView/replay_flight_data.md b/ru/FlyView/replay_flight_data.md
index 3b0a8b08a..b2af57ad7 100644
--- a/ru/FlyView/replay_flight_data.md
+++ b/ru/FlyView/replay_flight_data.md
@@ -2,7 +2,7 @@
> **Warning** This feature is intended primarily for **autopilot developers**/**vehicle creators**. It is only supported on desktop builds (Windows, Linux, Mac OS).
-The *Replay Flight Data* features allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
+The *Replay Flight Data* feature allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
> **Note** *QGroundControl* treats flight replay like an active connection. When you pause/stop playing, the ground station will report "Communication Lost" and wait for disconnection or for more messages.
@@ -18,7 +18,7 @@ To replay a flight:
1. When a log is loaded you can use the:
- **Pause/Play** button to pause and restart playing.
- *Slider* to drag to a new position in the log.
- - *Rate* selector to choose how quickly the log is run.
-1. To stop relay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting the **Load Telemetry Log** button will be displayed.
+ - *Rate* selector to choose the playback speed.
+1. To stop replay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting, the **Load Telemetry Log** button will be displayed.
> **Tip** You can inspect the running replay in more detail using the [MAVLink Inspector](../analyze_view/mavlink_inspector.md).
diff --git a/ru/PlanView/Pattern.md b/ru/PlanView/Pattern.md
index 43e999ee1..e12bb02e3 100644
--- a/ru/PlanView/Pattern.md
+++ b/ru/PlanView/Pattern.md
@@ -9,6 +9,6 @@ The *Pattern tools* (in the [PlanView](../PlanView/PlanView.md) *Plan Tools*) al
| [Survey](../PlanView/pattern_survey.md) | Create a grid flight pattern over a polygonal area.
You can specify the polygon as well as the specifications for the grid and camera settings appropriate for creating geotagged images. | All |
| [Structure Scan](../PlanView/pattern_structure_scan_v2.md) | Create a grid flight pattern that captures images over vertical surfaces (polygonal or circular).
-These are typically used for the visual inspection or creation of 3d models of structures. | MultiCopter, VTOL |
+These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL |
| [Corridor Scan](../PlanView/pattern_corridor_scan.md) | Create a flight pattern which follows a poly-line (for example, to survey a road). | All |
| [Fixed Wing Landing](../PlanView/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing |
\ No newline at end of file
diff --git a/ru/PlanView/PatternPresets.md b/ru/PlanView/PatternPresets.md
index ec58ca1ee..fd5718284 100644
--- a/ru/PlanView/PatternPresets.md
+++ b/ru/PlanView/PatternPresets.md
@@ -29,4 +29,4 @@ If you want to view what the exact settings are for a Preset switch back to **Cu
## Presets In A Plan File
-The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user incorrect behavior may occur if that other user also have a preset of the same name but different settings.
\ No newline at end of file
+The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user, incorrect behavior may occur if that other user also has a preset of the same name but different settings.
\ No newline at end of file
diff --git a/ru/PlanView/PlanGeoFence.md b/ru/PlanView/PlanGeoFence.md
index 89e856ccd..5a4c4df39 100644
--- a/ru/PlanView/PlanGeoFence.md
+++ b/ru/PlanView/PlanGeoFence.md
@@ -15,7 +15,7 @@ To create a GeoFence:
-3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** buttons, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
+3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** button, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
> **Tip** You can create multiple regions by pressing the buttons multiple times, allowing complex geofence definitions to be created.
@@ -24,7 +24,7 @@ To create a GeoFence:
- Move the region by dragging the central dot on the map
- - Resize the circle by dragging the map dot on the edge of the circle (or you can change the radius value in the fence panel).
+ - Resize the circle by dragging the dot on the edge of the circle (or you can change the radius value in the fence panel).
- Polygon region:
@@ -38,7 +38,7 @@ To create a GeoFence:
You can select a geofence region to edit by selecting its *Edit* radio button in the GeoFence panel. You can then edit the region on the map as described in the previous section.
-Regions can be deleted by pressing the associated **Del** button
+Regions can be deleted by pressing the associated **Del** button.
## Upload a GeoFence
diff --git a/ru/PlanView/PlanView.md b/ru/PlanView/PlanView.md
index 283be976e..be87510e8 100644
--- a/ru/PlanView/PlanView.md
+++ b/ru/PlanView/PlanView.md
@@ -36,7 +36,7 @@ The following sections explain some of the details in the view.
## Planned Home Position {#planned_home}
-The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to a vehicle). It is used by QGC to estimate mission times and to draw waypoint lines.
+The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC). It is used by QGC to estimate mission times and to draw waypoint lines.
@@ -44,7 +44,7 @@ You should move/drag the planned home position to roughly the location where you
-> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this where the vehicle will return in Return/RTL mode).
+> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
## Plan Tools {#plan_tools}
@@ -124,7 +124,7 @@ The [Planned Home Position](#planned_home) section allows you to simulate the ve
> **Note** This is only the *planned* home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming.
-The section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
+This section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
#### Camera
diff --git a/ru/PlanView/pattern_fixed_wing_landing.md b/ru/PlanView/pattern_fixed_wing_landing.md
index 765bf486e..43a12d2a9 100644
--- a/ru/PlanView/pattern_fixed_wing_landing.md
+++ b/ru/PlanView/pattern_fixed_wing_landing.md
@@ -12,7 +12,7 @@ Both the loiter and land points can be dragged to new positions, and a number of
To create a landing pattern:
-1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*).
+1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*.
2. Choose the *Pattern Tool* from the *Plan Tools* and then select *Fixed Wing Landing Pattern*.
@@ -21,7 +21,7 @@ To create a landing pattern:
-3. Click on the map to create both the loiter and landing points. These can be moved on the map.
+3. Click on the map to create both the loiter point and the landing point. These can be moved on the map.
Additional settings are covered in the next section.
@@ -52,8 +52,8 @@ The configurable options are:
- **Heading** - Heading from loiter point to land point.
- **Altitude** - Altitude for landing point (nominally zero).
- *Radio Buttons*
- - **Landing Dist** - Distance between loiter and landing points.
- - **Glide Slope** - Glide slope between loiter and landing points.
+ - **Landing Dist** - Distance between loiter point and landing point.
+ - **Glide Slope** - Glide slope between loiter point and landing point.
- **Altitudes relative to home** - Check to set all altitudes in mission item to be relative to home (default is AMSL).
## Implementation
diff --git a/ru/PlanView/pattern_structure_scan_v2.md b/ru/PlanView/pattern_structure_scan_v2.md
index 60d90ebbd..486d4bdcb 100644
--- a/ru/PlanView/pattern_structure_scan_v2.md
+++ b/ru/PlanView/pattern_structure_scan_v2.md
@@ -1,6 +1,6 @@
# Structure Scan (Plan Pattern)
-A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3d models of structures.
+A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3D models of structures.
*Structure Scans* may be inserted into a mission using the Plan view **Pattern > Structure Scan** tool.
@@ -58,7 +58,7 @@ The user can always configure the following settings:
- **Start scan from top/bottom:** The direction in which layers are scanned.
- **Structure height:** The height of the object being scanned.
-- **Scan distance:** Distance from the structure of the flight path.
+- **Scan distance:** Distance from the structure to the flight path.
- **Entrance/Exit Alt:** Use this setting to avoid obstacles between the last/next waypoint and the structure to be scanned.
- The vehicle will fly to the *Entrance/Exit* point at this altitude and then descend to the initial layer to start the scan.
- The vehicle will ascend to this altitude after completing the scan and then move to the next waypoint.
@@ -72,13 +72,13 @@ The remaining settings depend on the *camera mode*:
- **Trigger Distance:** The distance between each camera trigger. The camera is only triggered while flying the layer path. It does not trigger images while transitioning from one layer to the next.
- **Gimbal Pitch** - Gimbal pitch you want to use for the scan.
-- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is always pointed directly at the right angles to the surface which it is capturing images. The settings are:
+- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is pointed directly at the surface when it is capturing images (i.e. at a right angle rather than some tangent). The settings are:
- **Camera Orientation:** Portrait or Landscape
- *Overlap*:
- **Front Lap:** Image overlap from top to bottom (increasing shrinks layer height and increases layer count).
- **Side Lap:** Image overlap at sides (increasing takes more images in each lap/layer scan).
- - **Scan distance:** Distance from the structure of the flight path.
+ - **Scan distance:** Distance from the structure to the flight path.
- **Ground Res:** Required image resolution/sample quality of surface.
- *Custom camera* selection allows you to enter your own camera characteristics, but otherwise behaves the same as a predefined camera.
\ No newline at end of file
diff --git a/ru/PlanView/pattern_survey.md b/ru/PlanView/pattern_survey.md
index d61481457..bed02fab1 100644
--- a/ru/PlanView/pattern_survey.md
+++ b/ru/PlanView/pattern_survey.md
@@ -21,7 +21,7 @@ To create a survey:
This will add a survey grid to the map, and a *Survey* item to the mission list (on the right).
-3. On the map drag the vertices to the change the shape of the polygon.
+3. On the map drag the vertices to change the shape of the polygon.
4. Click the `(+)` symbol between existing vertices to create a new vertix. The new vertix can then be dragged into a new position.
diff --git a/ru/SettingsView/General.md b/ru/SettingsView/General.md
index 3e4e44181..254bce4d8 100644
--- a/ru/SettingsView/General.md
+++ b/ru/SettingsView/General.md
@@ -15,7 +15,7 @@ This section defines the display units used in the application.
The settings are:
- **Distance**: Meters | Feet
-- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres |SquareMiles
+- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres | SquareMiles
- **Speed**: Metres/second | Feet/second | Miles/hour | Kilometres/hour | Knots
- **Temperature**: Celsius | Fahrenheit
diff --git a/ru/SettingsView/OfflineMaps.md b/ru/SettingsView/OfflineMaps.md
index fb2a8407e..8165f0f96 100644
--- a/ru/SettingsView/OfflineMaps.md
+++ b/ru/SettingsView/OfflineMaps.md
@@ -2,12 +2,12 @@
-Offline Maps allows you to cache map tiles for use when not connected to the internet. You can create multiple offline sets, each for a different location.
+Offline Maps allows you to cache map tiles for use when not connected to the Internet. You can create multiple offline sets, each for a different location.
## Add new set
To create a new offline map set, click "Add new set". Which will take you to this page: 
-From here you can name you set as well as specify the zoom levels you want to cache. Move the map to the position you can to cache and then set the zoom levels and click Download to cache the tiles.
+From here you can name your set as well as specify the zoom levels you want to cache. Move the map to the position you want to cache and then set the zoom levels and click Download to cache the tiles.
To the left you can see previews of the min and max zoom levels you have chosen.
\ No newline at end of file
diff --git a/ru/SetupView/Firmware.md b/ru/SetupView/Firmware.md
index 28f61b689..42e99d03e 100644
--- a/ru/SetupView/Firmware.md
+++ b/ru/SetupView/Firmware.md
@@ -8,7 +8,7 @@
## Подключение полетного контроллера для обновления прошивки
-> **Caution** **Before you start installing Firmware** all USB connections to you vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
+> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
1. First select the **Gear** icon (*Vehicle Setup*) in the top toolbar and then **Firmware** in the sidebar.
@@ -26,7 +26,7 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
- If you select *ArduPilot* you will also have to choose the specific firmware the type of vehicle (as shown below).
+ If you select *ArduPilot* you will also have to choose the specific firmware and the type of vehicle (as shown below).
@@ -42,4 +42,4 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
-Once the firmware has completed loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
+Once the firmware has finished loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
diff --git a/ru/SetupView/FlightModes.md b/ru/SetupView/FlightModes.md
index 18d026577..dbbfae538 100644
--- a/ru/SetupView/FlightModes.md
+++ b/ru/SetupView/FlightModes.md
@@ -19,7 +19,7 @@ To access this section, select the **Gear** icon (Vehicle Setup) in the top tool
On ArduPilot you can assign up to 6 different flight modes to a single channel of your transmitter (the channel is selectable on Plane, but fixed to channel 5 on Copter).
-ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: \[Auxiliary Function Switches\](
+ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: [Auxiliary Function Switches](https://ardupilot.org/copter/docs/channel-7-and-8-options.html#channel-7-and-8-options)
To set the flight modes:
@@ -50,7 +50,7 @@ All values are automatically saved as they are changed.
- **Single Channel Mode Selection:** Assign up to 6 flight modes to switch positions encoded in a single channel.
- **Multi Channel Mode Selection:** Assign modes to switch positions encoded in one or more channels. Some modes are hard coded to share channels, or are defined/set automatically based on other mode selections (the behaviour of multi-channel mode selection can sometimes be confusing).
-> **Tip** The recommended approach is use *Single Channel Mode Selection* because it easy to understand and configure. It is similar to the approach used by ArduPilot.
+> **Tip** The recommended approach is to use *Single Channel Mode Selection* because it is easy to understand and configure. It is similar to the approach used by ArduPilot.
### Single-Channel Mode {#single_channel}
@@ -85,7 +85,7 @@ It is common to use the positions of a 2- and a 3-position switch on the transmi
The video below shows how this is done with the *FrSky Taranis* transmitter (a very popular and highly recommended RC transmitter). The process involves assigning a "logical switch" to each combination of positions of the two real switches. Each logical switch is then assigned to a different PWM value on the same channel.
-
+
The video then shows how to use *QGroundControl* to specify the mode channel and map modes to each of the 6 "slots". {% youtube %} http://www.youtube.com/watch?v=scqO7vbH2jo {% endyoutube %}
### Multi-Channel Mode
diff --git a/ru/SetupView/Joystick.md b/ru/SetupView/Joystick.md
index f719efb77..7e8fa169e 100644
--- a/ru/SetupView/Joystick.md
+++ b/ru/SetupView/Joystick.md
@@ -109,7 +109,7 @@ The following joysticks/controllers have been shown to work with relatively rece
### Sony Playstation 3/4 Controllers
-These are both highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
+Both these joysticks are highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
#### Sony PS4 - DualShock 4 Controller V2 (Wireless setup)
diff --git a/ru/SetupView/airframe_px4.md b/ru/SetupView/airframe_px4.md
index 83ef87c3d..89620f8b8 100644
--- a/ru/SetupView/airframe_px4.md
+++ b/ru/SetupView/airframe_px4.md
@@ -10,7 +10,7 @@ To select the airframe in PX4:
The example above shows *Generic Hexarotor X geometry* selected from the *Hexarotor X* group.
-4. Click the **Apply and Restart** button to the top right of the screen.
+4. Click the **Apply and Restart** button on the top right of the screen.
5. Click **Apply** in the following prompt to save the settings and restart the vehicle.
diff --git a/ru/SetupView/sensors_ardupilot.md b/ru/SetupView/sensors_ardupilot.md
index 586ada197..163a6c138 100644
--- a/ru/SetupView/sensors_ardupilot.md
+++ b/ru/SetupView/sensors_ardupilot.md
@@ -56,7 +56,7 @@ To perform **Pressure** calibration:
## CompassMot (Optional)
-CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and where there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
+CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and when there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
To perform **CompassMot** calibration:
diff --git a/ru/SetupView/sensors_px4.md b/ru/SetupView/sensors_px4.md
index a8ce3f3b9..76c5ccd9d 100644
--- a/ru/SetupView/sensors_px4.md
+++ b/ru/SetupView/sensors_px4.md
@@ -37,9 +37,9 @@ The calibration steps are:
-4. When finished, *QGroundControl* will display a progress bar *Calibration complete* 
+4. When finished, *QGroundControl* will display *Calibration complete* and the progress bar will fill completely. 
-> **Note** If you move the vehicle *QGroundControl* will automatically restart the calibration.
+> **Note** If you move the vehicle during calibration, *QGroundControl* will automatically restart the calibration.
You can then proceed to the next sensor.
diff --git a/ru/SetupView/tuning_px4.md b/ru/SetupView/tuning_px4.md
index 38b54c7c7..9352d2a29 100644
--- a/ru/SetupView/tuning_px4.md
+++ b/ru/SetupView/tuning_px4.md
@@ -17,7 +17,7 @@ To use advanced tuning:
1. First select the *Tuning axis* to tune: **Rol**, **Pitch** or **Yaw** (each axis is tuned separately).
2. Fly the vehicle, observing the tracking on the chart.
- Adjust the *Tuning Values* (parameters) to improve the tracking shown on the graph
- - Set the **Increment/Decrement %** to a larger/smaller value for course/fine tuning
+ - Set the **Increment/Decrement %** to a larger/smaller value for coarse/fine tuning
- Press the **Save Values** button if a change improves tracking. > **Tip** At any point you can press **Reset To Saved Values** to restore the last saved good state.
- You can also **Clear**/**Stop** the chart using the buttons provided.
3. Tune the other axes.
\ No newline at end of file
diff --git a/ru/analyze_view/README.md b/ru/analyze_view/README.md
index 58bd2fb45..d60e300ea 100644
--- a/ru/analyze_view/README.md
+++ b/ru/analyze_view/README.md
@@ -9,5 +9,4 @@ The view provides tools to:
* [Загрузка Журналов](../analyze_view/log_download.md) — Просмотр списка, загрузка и очистка журналов событий полета в памяти полетного контроллера.
* [GeoTag Images (PX4)](../analyze_view/geotag_images.md) — Geotag survey mission images using the flight log (on a computer).
* [MAVLink Console (PX4)](../analyze_view/mavlink_console.md) — Access the the nsh shell running on the vehicle.
-* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
-* Vibration clip count
\ No newline at end of file
+* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
\ No newline at end of file
diff --git a/ru/getting_started/download_and_install.md b/ru/getting_started/download_and_install.md
index a58e39570..7cd1ce20e 100644
--- a/ru/getting_started/download_and_install.md
+++ b/ru/getting_started/download_and_install.md
@@ -1,6 +1,6 @@
# Скачать и установить
-The sections below can be used download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
+The sections below can be used to download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
> **Совет** Смотрите раздел [QGC Установка/Проблеммы при конфигурировании](../Support/troubleshooting_qgc.md), если у вас возникли какие-либо проблемы с запуском *QGroundControl* после установки!
diff --git a/ru/getting_started/quick_start.md b/ru/getting_started/quick_start.md
index 920ae3a20..f1118aee8 100644
--- a/ru/getting_started/quick_start.md
+++ b/ru/getting_started/quick_start.md
@@ -17,6 +17,7 @@ Getting *QGroundControl* up and running is quick and easy:
- [Уставки](../SetupView/SetupView.md) Настройка и настройка БПЛА.
- [План](../PlanView/PlanView.md) Планирование и создание автономных планов полетов.
- [Полет](../FlyView/FlyView.md) Следите за БПЛА во время полёта, включая потоковое видео.
+ - [Analyze] ** Description of Analyze view is missing **
- Нажмите *Символы состояния* на панели инструментов, чтобы узнать состояние подключенного БПЛА.
Хотя пользовательский интерфейс достаточно интуитивен, из этой документации можно почерпнуть дополнительную информацию.
\ No newline at end of file
diff --git a/ru/toolbar/toolbar.md b/ru/toolbar/toolbar.md
index 87c4d43e1..823b5050c 100644
--- a/ru/toolbar/toolbar.md
+++ b/ru/toolbar/toolbar.md
@@ -12,7 +12,7 @@ The following icons are used to switch between the main *Views*. These are displ
 **[План](../PlanView/PlanView.md)**
Планирование и создание автономных планов полетов.
- **[Полет](../FlyView/FlyView.md)**
Следите за БПЛА во время полёта, включая потоковое видео.
+ **[Fly](../FlyView/FlyView.md)**
Monitor your vehicle(s) while flying, including streaming video.
 **[Анализ](../analyze_view/README.md)**
Скачивание журналов событий, запись географических метаданных в фотографии на основе трека полета, доступ к консоли MAVLink.
@@ -20,11 +20,11 @@ The following icons are used to switch between the main *Views*. These are displ
Символы статуса активны, когда *QGroundControl* подключено к полётному контроллеру. Они сигнализируют об уровнях состояния основных систем необходимых для навигации БПЛА и могут быть нажаты для получения более подробной информации.
- **Сообщения БПЛА**
Нажмите, чтобы показать раскрывающийся список сообщений от БПЛА. This will change to a Yield sign if there are critical messages.
+  **Vehicle Messages**
Click to show a list of messages from the vehicle. Note that version on the right is displayed when there are critical messages.
- **Статус GPS**
Показывает количество спутников и текущее HDOP (Horizontal Dilution of Precision) — снижение точности в горизонтальной плоскости.
+ **GPS Status**
Shows you satellite count and curent HDOP.
- **RSSI радиоуправления**
Информация об уровне сигнала радиоуправления.
+ **RC RSSI**
RC signal strength information.
 **RSSI Телеметрии **
Информация об уровене сигнала канала телеметрии.
diff --git a/tr/FlyView/FlyView.md b/tr/FlyView/FlyView.md
index fe84e796f..78821b6e8 100644
--- a/tr/FlyView/FlyView.md
+++ b/tr/FlyView/FlyView.md
@@ -22,7 +22,7 @@ Yukarıdaki ekran görüntüsü, uçuş ekranının ana öğelerini gösterir:
- **Uçuş Araç Çubuğu:** Sensörler (GPS, pil, RC kontrolü) ve araç durumu (Uçuş modu, Etkin (armed) / Devre Dışı (disarmed) durumu) hakkında anahtar bilgiler.
- Daha fazla ayrıntı görmek için sensör göstergelerini seçin.
- Yeni bir mod seçmek için * Flight mode * metnine (ör. "Hold") tıklayın. Tüm modlar mevcut olmayabilir.
- - Aracın uçuşa hazır olma durumunu değiştirmek için *Armed/Disarmed* metnine tıklayın. Eğer araç uçuyorsa *Emergency Stop* için bu metne tıklayın.
+ - Aracın uçuşa hazır olma durumunu değiştirmek için *Armed/Disarmed* metnine tıklayın. While flying you can press this text for *Emergency Stop*.
- **Uçuş araçları:** Şunları yapmak için kullanabilirsiniz:
- Kalkış/iniş arasında geçiş yapın.
- Mevcut işlemi durdur/tekrar başlat (ör. iniş, ya da görev).
@@ -32,7 +32,7 @@ Yukarıdaki ekran görüntüsü, uçuş ekranının ana öğelerini gösterir:
- **[Bilgi Paneli](#instrument_panel):** Telemetri, kamera, video, sistem durumu ve titreşim dahil olmak üzere araç bilgilerini görüntüleyebileceğiniz çok sekmeli widget.
- **[Video/Harita](#video_switcher):** Bir pencerede video ile harita arasında geçiş yapın.
- *Video* ya da *Map*'i ön plana almak için öne almak istediğinize tıklayın.
- - *QGroundControl*, aracınızın UDP bağlantısı üzerinden RTP ve RTSP video yayını yapmanızı destekler. Ayrıca direkt bağlantılı UVC cihazları da destekler. QGC'nin video desteği hakkında daha ayrıntılı bilgiyi [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md)'de bulabilirsiniz.
+ - *QGroundControl*, aracınızın UDP bağlantısı üzerinden RTP ve RTSP video yayını yapmanızı destekler. It also supports directly connected UVC devices. QGC'nin video desteği hakkında daha ayrıntılı bilgiyi [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md)'de bulabilirsiniz.
- Bir [Telemetry Overlay](../FlyView/VideoOverlay.md) dosyası otomatik olarak oluşturulacaktır
- **Kaydırmalı Onay Butonu:** İstenen işlemi gerçekleştirmek için onay butonu. Operasyonu başlatmak için kaydırın. İptal etmek için **X** 'e basın.
@@ -42,7 +42,7 @@ Ayrıca varsayılan olarak görüntülenmeyen/ belirli koşullarda görüntülen
Bilgi Paneli, telemetri, kamera, video, sistem durumu ve titreşim bilgileri dahil olmak üzere mevcut araç hakkında bilgileri görüntüleyebileceğiniz çok sekmeli bir widgettır.
-Varsayılan şekilde araç telemetrisini gösterir - diğer seçenekleri seçmek için sağdaki açılır menüyü kullanabilirsiniz.
+The default page displays vehicle telemetry - use the drop down menu on the top right to select the other options.
### Değerler (Telemetri)
@@ -78,7 +78,7 @@ Video sayfası video akışını etkinleştirmek ve devre dışı bırakmak içi
### Durum
-Durum sayfası aracınızdaki sistemin durumunu gösterir. Eğer sistemde bir sıkıntı olursa *QGroundControl* bu sayfayı otomatik olarak açacaktır.
+Durum sayfası aracınızdaki sistemin durumunu gösterir. *QGroundControl* will switch to this page automatically if any system changes to unhealthy.
 
@@ -98,11 +98,11 @@ Aşağıdaki bölümler, Uçuş Ekranı'nda genel işlemlerin / görevlerin nas
Aracın doğru ayarlandığını ve uçmak için güvenli olduğu gösteren standart kontrollerin yapılması için otomatik bir uçuş öncesi kontrol listesi kullanılabilir.
-Kontrol listesi için, önce [Application Settings > General > Fly View](../SettingsView/General.md) 'a gidip **Use preflight checklist** onay kutusunu seçerek etkinleştirin. Liste *Flight Tools*'a eklenecektir. Kontrol listesini oradan açabilirsiniz:
+To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. Liste *Flight Tools*'a eklenecektir. Kontrol listesini oradan açabilirsiniz:
-Tüm testleri gerçekleştirdikten sonra, tamamlandı olarak işaretlemek için kullanıcı arayüzünde testi seçin.
+Once you have performed each test, select it on the UI to mark it as complete.
### Aracı Devreye Alma {#arm}
@@ -126,7 +126,7 @@ Aracı devre dışı bırakmak motorları durdurur (aracı güvenli hale getirir
### Acil Durdurma {#emergency_stop}
-Acil durdurma, uçarken aracı durdurmakla aynı etkiye sahiptir. Aracınız çarpacaktır/çakılacaktır!
+Emergency stop is effectively the same as disarming the vehicle while it is flying. Aracınız çarpacaktır/çakılacaktır!
Aracı devre dışı bırakmak için uçuş sırasında *Fly Toolbar*'dan **Armed**'ı seçin.
@@ -134,7 +134,7 @@ Aracı devre dışı bırakmak için uçuş sırasında *Fly Toolbar*'dan **Arme
### Kalkış {#takeoff}
-> **Tip** Eğer bir multikopter için göreve başlıyorsanız, *QGroundControl* kalkışı otomatik olarak yapacaktır.
+> **Tip** If you are starting a mission for a multicopter, *QGroundControl* will automatically perform the takeoff step.
Kalkmak için (iniş yapıldığında):
@@ -155,14 +155,14 @@ Uçuş sırasında istediğiniz zaman mevcut konuma inebilirsiniz:
### RTL/Geri Dönüş
-Uçuş esnasında istediğiniz zaman ana konuma geri dönün:
+Return to a "safe point" at any time while flying:
1. *Fly Tools*'dan **RTL** butonuna basın.
2. Kaydırmalı onay butonunu kaydırarak RTL'i onaylayın.
-
+
-> **Note** Araç, türüne ve konfigürasyonuna bağlı olarak ana konuma inedebilir.
+> **Note** Vehicles commonly return to the "home" (takeoff) location and land. This behaviour depends on the vehicle type and configuration. For example, rally points or mission landings may be used as alternative return targets.
### Yükleklik Değiştirme {#change_altitude}
@@ -181,7 +181,7 @@ Uçuş esnasında eğer bir görevde değilse aracın yükseliği değiştirileb
Kalkıştan sonra belirli bir konuma uçmayı ayarlayabilirsiniz.
-1. Haritada aracın gitmesini istediğiniz yere basın ve açılır pencereden **Go to location**'ı seçin.
+1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup.
@@ -197,7 +197,7 @@ Kalkıştan sonra belirli bir konuma uçmayı ayarlayabilirsiniz.
Kalkıştan sonra belirli bir konumun çevresinde yörüngede dolaşmasını ayarlayabilirsiniz.
-1. Haritaya basın (istediğiniz yörüngenin merkezine yakın bir yere) ve açılır pencereden **Orbit at location**'i seçin.
+1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
@@ -211,7 +211,7 @@ Kalkıştan sonra belirli bir konumun çevresinde yörüngede dolaşmasını aya
### Duraklatma
-Kalkış, iniş, RTL, Yörünge dahil olmak üzere çoğu operasyonu aracın olduğu konumda duraklatabilirsiniz. Duraklatıldığında aracın davranışı aracın tipine bağlıdır, genellikle multikopterler havada asılı kalırken sabit kanatlar çember çizer.
+You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. Duraklatıldığında aracın davranışı aracın tipine bağlıdır, genellikle multikopterler havada asılı kalırken sabit kanatlar çember çizer.
> **Note** Bir *Goto location* operasyonunu durduramazsınız.
@@ -247,7 +247,7 @@ Yerdeki bir aracın görevini başlatmak için:
Göreve *sıradaki* hedef noktanızdan *devam* edebilirsiniz (*Continue Mission* kaydırmalı onay butonu kalkıştan sonra çoğu kez varsayılan olarak gösterilir).
-> **Note** Continue ve [Resume mission](#resume_mission) farklıdır! Continue komutu durdurulmuş bir görevi tekrar başlatmak veya zaten kalkmış bir araç için yani kalkış görevi komutunu kaçırmış durumdaysanız kullanılır. Resume ise eğer görevin ortasında RTL ya da iniş yaptığınızda (ör. batarya değiştirmek için) ve sonrasında göreve devam etmek istiyorsanız kullanılır (yani görevi olduğunuz yerden devam ettirmek yerine, görevdeki bir sonraki hedefinizden devam ettirir).
+> **Note** Continue ve [Resume mission](#resume_mission) farklıdır! Continue komutu durdurulmuş bir görevi tekrar başlatmak veya zaten kalkmış bir araç için yani kalkış görevi komutunu kaçırmış durumdaysanız kullanılır. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission).
Görevinize aşağıdakileri yaparak devam edebilirsiniz (hali hazırda bir görevde değilseniz!):
@@ -284,7 +284,7 @@ Görev bittikten sonra aracın inişi ve devre dışı bırakılmasının ardın
### Videoyu Görüntüleme {#video_switcher}
-Video akışı etkinleştirildiğinde, *QGroundControl* haritanın sol altında bulunan "videoya geçiş penceresi"nde videoyu göstermeye başlıyacaktır. Ön planda *Video* ya da *Map* hangisini görüntülemek istiyorsanız geçiş penceresinde istediğiniz yere tıklayabilirsiniz (aşağıda videonun ön planda olduğu hali görebilirsiniz).
+Video akışı etkinleştirildiğinde, *QGroundControl* haritanın sol altında bulunan "videoya geçiş penceresi"nde videoyu göstermeye başlıyacaktır. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (in the image below, the video is shown in the foreground).
@@ -295,7 +295,7 @@ Video görüntüsünü geçiş penceresindeki kontrolleri kullanararak daha da d
-- Sağ üst köşedeki ikonu sürükleyerek geçiş penceresini tekrar boyutlandırabilirsiniz.
+- Resize the switcher by dragging the icon in the top right corner.
- Geçiş penceresini sol alt köşede bulunan ikona basarak gizleyebilirsiniz.
- Sol üst köşedeki ikona basarak video geçiş pencersini ayırabilirsiniz. (ayrıldığında, işletim sisteminizdeki her hangi bir pencere gibi hareket ettirip tekrar boyutlandırabilirsiniz). Eğer ayrılan pencereyi kapatırsanız, geçiş penceresi tekrardan QGC uçuş görünüme sabitlenecektir.
diff --git a/tr/FlyView/VideoOverlay.md b/tr/FlyView/VideoOverlay.md
index 4f0eaf378..1212da9b5 100644
--- a/tr/FlyView/VideoOverlay.md
+++ b/tr/FlyView/VideoOverlay.md
@@ -1,6 +1,6 @@
# Video Overlay
-QGroundControl bir video akışını dosyaya kaydederken, aynı zamanda oynatma sırasında video üzerinde telemetriyi göstermek için kullanılabilen, telemetri verilerini içeren bir altyazı dosyasını da dışa aktarır. Telemetri [değerleri widget](FlyView.md#values-telemetry)ında gösterilmesi için hangi telemetri değerleri seçilirse seçilsin, onlar da overlaye aktarılacaktır. Overlay değerleri 1Hz hızla güncellenecektir.
+When QGroundControl is recording a video stream to a file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Telemetri [değerleri widget](FlyView.md#values-telemetry)ında gösterilmesi için hangi telemetri değerleri seçilirse seçilsin, onlar da overlaye aktarılacaktır. Overlay değerleri 1Hz hızla güncellenecektir.
diff --git a/tr/FlyView/replay_flight_data.md b/tr/FlyView/replay_flight_data.md
index 871f70291..43190ab30 100644
--- a/tr/FlyView/replay_flight_data.md
+++ b/tr/FlyView/replay_flight_data.md
@@ -2,7 +2,7 @@
> **Warning** Bu özellik, öncelikle ** otopilot geliştiricileri ** / ** araç tasarlayıcıları ** için tasarlanmıştır. Bu özellik, sadece bilgisayar sürümlerinde desteklenmektedir (Windows, Linux, Mac OS).
-* Uçuş Verilerini Yeniden Oynat * özelliği, kullanıcıların bir telemetri günlüğünü yeniden oynatmasına olanak vererek geçmiş veya sorunlu uçuşların incelenmesine olanak tanır. Uçuş başlatılabilir, duraklatılabilir, durdurulabilir, yeniden başlatılabilir vb.
+The *Replay Flight Data* feature allows users to replay a telemetry log, enabling review of past or problematic flights. Uçuş başlatılabilir, duraklatılabilir, durdurulabilir, yeniden başlatılabilir vb.
> **Note** *QGroundControl* uçuş tekrarını aktif bir bağlantı gibi görür. Oynatmayı duraklattığınızda / durdurduğunuzda, yer istasyonu "İletişim Kaybı" olarak rapor edecek ve bağlantının kesilmesini veya daha fazla komut bekleyecektir.
@@ -18,7 +18,7 @@ Bir uçuşu tekrar etmek için:
1. Bir kayıt yüklendiğinde şunları kullanabilirsiniz:
- Oynatmayı durdurmak ve yeniden başlatmak için **Pause/Play** butonuna basın.
- Kayıtta yeni bir konuma ilerlemek için *Slider*.
- - Kaydın ne kadar hızlı oynatılacağını ayarlamak için *Rate*.
-1. Oynatımı durdurmak (stop) için (ör. oynatılması için yeni bir dosya yüklemek için), ilk olarak uçuşu duraklatın (pause) ve ardından **Disconnect**'i seçin (ortaya çıktığında). Bağlantıyı kestikten sonra **Load Telemetry Log** butonu ortaya çıkacaktır.
+ - *Rate* selector to choose the playback speed.
+1. To stop replay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting, the **Load Telemetry Log** button will be displayed.
> **Tip** [ MAVLink Inspector ](../analyze_view/mavlink_inspector.md) 'ı kullanarak devam eden tekrarı daha ayrıntılı olarak inceleyebilirsiniz.
diff --git a/tr/PlanView/Pattern.md b/tr/PlanView/Pattern.md
index a4df6bbff..98661c3d8 100644
--- a/tr/PlanView/Pattern.md
+++ b/tr/PlanView/Pattern.md
@@ -4,11 +4,11 @@
-| Şablon | Tanım | Araçlar |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| Şablon | Tanım | Araçlar |
+| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| [Yüzey](../PlanView/pattern_survey.md) | Çok köşeli bir alan üstünde ızgara şeklinde bir uçuş şablonu oluşturun.
-Alanı ve coğrafi etiketli görüntüler oluşturmak için uygun ızgara ve kamera ayarlarını belirleyebilirsiniz. | Tüm |
+Alanı ve coğrafi etiketli görüntüler oluşturmak için uygun ızgara ve kamera ayarlarını belirleyebilirsiniz. | Tüm |
| [Yapı Taraması](../PlanView/pattern_structure_scan_v2.md) | Dikey yüzeyler üzerinde (çok köşeli ya da dairesel) görüntüler yakalayabilmek için ızgara şeklinde bir uçuş şablonu oluşturun.
-Bunlar genellikle görsel inceleme ya da yapıların 3 boyutlu modellemesi için kullanılır. | MultiCopter, VTOL |
-| [Koridor Taraması](../PlanView/pattern_corridor_scan.md) | Çoklu çizgileri takip eden bir uçuş planı oluşturun (mesela, bir yolu gözlemlemek için). | Tüm |
-| [Sabit Kanat İnişi](../PlanView/pattern_fixed_wing_landing.md) | Bir göreve sabit kanatlı araçlar için iniş yolu ekleyin. | Sabit Kanat |
\ No newline at end of file
+These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL |
+| [Koridor Taraması](../PlanView/pattern_corridor_scan.md) | Çoklu çizgileri takip eden bir uçuş planı oluşturun (mesela, bir yolu gözlemlemek için). | Tüm |
+| [Sabit Kanat İnişi](../PlanView/pattern_fixed_wing_landing.md) | Bir göreve sabit kanatlı araçlar için iniş yolu ekleyin. | Sabit Kanat |
\ No newline at end of file
diff --git a/tr/PlanView/PatternPresets.md b/tr/PlanView/PatternPresets.md
index b46b2e9e8..f861f4e5d 100644
--- a/tr/PlanView/PatternPresets.md
+++ b/tr/PlanView/PatternPresets.md
@@ -29,4 +29,4 @@ Bir ön ayarın ayarlarının neler olduğunu görmek istiyorsanız **Custom (sp
## Plan Dosyasında Ön Ayarlar
-Halihazırda seçili olan Ön Ayar Plan dosyasına da kaydedilir, böylece Planı geri yüklediğinizde ön ayar tekrar seçilebilecektir. Ön ayarların kullandığınız QGroundControl sürümüne özel olduğunu unutmayınız. Bir Plan dosyasını bir ön ayar ile başka bir kullanıcıyla paylaşırsanız, diğer kullanıcının da aynı adı taşıyan ancak farklı ayarlara sahip bir ön ayarı varsa, hatalı olaylar gerçekleşebilir.
\ No newline at end of file
+Halihazırda seçili olan Ön Ayar Plan dosyasına da kaydedilir, böylece Planı geri yüklediğinizde ön ayar tekrar seçilebilecektir. Ön ayarların kullandığınız QGroundControl sürümüne özel olduğunu unutmayınız. If you share a Plan file with a preset with another user, incorrect behavior may occur if that other user also has a preset of the same name but different settings.
\ No newline at end of file
diff --git a/tr/PlanView/PlanGeoFence.md b/tr/PlanView/PlanGeoFence.md
index 97bdf4219..0eaddc093 100644
--- a/tr/PlanView/PlanGeoFence.md
+++ b/tr/PlanView/PlanGeoFence.md
@@ -15,7 +15,7 @@ Coğrafi Sınır Oluşturmak için:
-3. **Circular Fence** ya da **Polygon Fence** butonlarına basarak, sırasıyla dairesel ya da çokgen bölgeler ekleyin. Haritaya yeni bir bölge ve butonların altına sınırlarla ilgili yeni bir liste eklenecektir.
+3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** button, respectively. Haritaya yeni bir bölge ve butonların altına sınırlarla ilgili yeni bir liste eklenecektir.
> **Tip** Butonlara birden çok kez basarak birden çok bölge oluşturabilirsiniz, böylece karmaşık coğrafi sınırlar oluşturulabilir.
@@ -24,7 +24,7 @@ Coğrafi Sınır Oluşturmak için:
- Merkezi noktayı kaydırarak bölgeyi haritada hareket ettirin
- - Dairenin sınırındaki noktayı sürükleyerek boyutunu ayarlayın (veya sınırlar panelindeki yarıçapı değiştirebilirsiniz).
+ - Resize the circle by dragging the dot on the edge of the circle (or you can change the radius value in the fence panel).
- Çokgen Bölge:
@@ -38,7 +38,7 @@ Coğrafi Sınır Oluşturmak için:
Coğrafi Sınır panelinde *Edit* butonunu seçerek düzenlemek için bir coğrafi sınır bölgesi seçebilirsiniz. Daha sonra, önceki bölümde anlatıldığı gibi haritadaki bölgeyi düzenleyebilirsiniz.
-Bölgeler, **Del** düğmesine basılarak silinebilir
+Regions can be deleted by pressing the associated **Del** button.
## Coğrafi Sınır Yükleme
diff --git a/tr/PlanView/PlanView.md b/tr/PlanView/PlanView.md
index 438dcfa00..4775244d0 100644
--- a/tr/PlanView/PlanView.md
+++ b/tr/PlanView/PlanView.md
@@ -36,7 +36,7 @@ Aşağıdaki bölümler, ekrandaki bazı ayrıntıları açıklamaktadır.
## Planlanmış Ev Konumu {#planned_home}
-*Plan View* 'de gösterilen *Planned Home*, bir görev planlanırken (mesela bir araca bağlı değilken) yaklaşık başlangıç noktasını ayarlamak için kullanılır. QGC tarafından görev sürelerini tahmin etmek ve hedef noktalar arası çizgileri çizmek için kullanılır.
+The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC). QGC tarafından görev sürelerini tahmin etmek ve hedef noktalar arası çizgileri çizmek için kullanılır.
@@ -44,7 +44,7 @@ Planlanan ev konumunu yaklaşık olarak kalkış yapmayı planladığınız konu
-> **Tip** Uçuş ekranı, araç devreye alındığında araın yazılımı tarafından ayarlanan *asıl* ev konumunu gösterir (bu konum, aracın Geri Dönüş/RTL modunda gideceği konumdur).
+> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
## Plan Araçları {#plan_tools}
@@ -124,7 +124,7 @@ Aracınızın son görev öğesinden sonra Geri Dönmesini/RTL istiyorsanız bun
> **Note** Bu yalnızca * planlanan * ev konumudur ve aracı çalıştırmayı planladığınız yere konumlandırılmalıdır. Görevin gerçekleşmesinde gerçek bir etkisi yoktur. Asıl ev konumu, araç tarafından devreye alınırken ayarlanır.
-Bu bölüm, **Altitude** ve ** Set Home to Map Centre** 'ı ayarlamanıza olanak tanır (haritada sürükleyerek başka bir konuma taşıyabilirsiniz).
+This section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
#### Kamera
diff --git a/tr/PlanView/pattern_fixed_wing_landing.md b/tr/PlanView/pattern_fixed_wing_landing.md
index 81ed327c2..005b3da32 100644
--- a/tr/PlanView/pattern_fixed_wing_landing.md
+++ b/tr/PlanView/pattern_fixed_wing_landing.md
@@ -12,7 +12,7 @@ Hem oyalanma hem de iniş noktaları, istenilen yeni noktalara sürüklenebilir
İniş yolu oluşturmak için:
-1. [PlanView](../PlanView/PlanView.md)'den *Plan Tools*'u açın.
+1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*.
2. *Plan Tools* 'dan *Plan Tools*'u açın ve *Fixed Wing Landing Pattern*'i seçin.
@@ -21,7 +21,7 @@ Hem oyalanma hem de iniş noktaları, istenilen yeni noktalara sürüklenebilir
-3. Oyalanma ve iniş noktalarını ayarlamak için haritaya tıklayın. Bu noktalar harita üzerinde hareket ettirilebilir.
+3. Click on the map to create both the loiter point and the landing point. Bu noktalar harita üzerinde hareket ettirilebilir.
Ek ayarlar bir sonraki bölümde ele alınmıştır.
@@ -52,8 +52,8 @@ Ayarlanabilir seçenekler şunlardır:
- **Heading** - Oyalanma noktasından iniş noktasına yönelme.
- **Altitude** - İniş noktası için yükseklik (nominal olarak sıfır).
- *Radyo Butonları*
- - **Landing Dist** - Oyalanma ve iniş noktaları arası mesafe.
- - **Glide Slope** - Oyalanma ve iniş noktaları arasındaki alçalma eğrisi.
+ - **Landing Dist** - Distance between loiter point and landing point.
+ - **Glide Slope** - Glide slope between loiter point and landing point.
- **Altitudes relative to home** - Tüm yüksekliklerin ev konumuna bağlı olması için işaretleyin (varsayılan olarak deniz seviyesidir).
## Uygulama
diff --git a/tr/PlanView/pattern_structure_scan_v2.md b/tr/PlanView/pattern_structure_scan_v2.md
index 4af659368..cd10f56ef 100644
--- a/tr/PlanView/pattern_structure_scan_v2.md
+++ b/tr/PlanView/pattern_structure_scan_v2.md
@@ -1,6 +1,6 @@
# Yapı Taraması (Plan Şablonu)
-*Structure Scan*, çok köşeli (veya dairesel) zemin ayak izine sahip bir yapının *dikey yüzeyleri* üzerinde (ör. duvarlar) görüntüler yakalayabilmek için ızgara şeklinde bir uçuş şablonu oluşturmanıza olanak sağlar. Yapı Taraması genellikle görsel inceleme ya da yapıların 3 boyutlu modellemesi için kullanılır.
+*Structure Scan*, çok köşeli (veya dairesel) zemin ayak izine sahip bir yapının *dikey yüzeyleri* üzerinde (ör. duvarlar) görüntüler yakalayabilmek için ızgara şeklinde bir uçuş şablonu oluşturmanıza olanak sağlar. Structure Scans are typically used for the visual inspection or creating 3D models of structures.
*Yapı Taramaları*, Plan ekranında **Pattern > Structure Scan** aracı kullanılarak bir görevin içine yerleştirilebilir.
@@ -58,7 +58,7 @@ Kullanıcı her zaman aşağıdaki ayarları yapılandırabilir:
- **Start scan from top/bottom:** Katmanların taranma yönü.
- **Structure height:**Taranan nesnenin yüksekliği.
-- **Scan distance:**Uçuş yolunun yapıya olan mesafesi.
+- **Scan distance:** Distance from the structure to the flight path.
- **Entrance/Exit Alt:** Son/sonraki hedef noktası ile taranacak yapı arasındaki engellerden kaçınmak için bu ayarı kullanın.
- Araç, bu irtifada *Entrance/Exit* noktasına yükselecek ve ardından taramayı başlatmak için ilk katmana alçalacaktır.
- Araç, taramayı tamamladıktan sonra bu irtifaya yükselecek ve ardından bir sonraki hedef noktaya geçecektir.
@@ -72,13 +72,13 @@ Kalan ayarlar *camera mode*'a bağlıdır:
- **Trigger Distance:** Her kamera çekimi arasındaki mesafe. Kamera sadece katman yolunda uçarken çekim yapar. Bir katmandan diğerine geçerken görüntü çekmez.
- **Gimbal Pitch** -Tarama için kullanmak istediğiniz gimbal eğimi.
-- *Bilinen/önceden tanımlanmış kameralar* görüntü örtüşmesi için gerekli katman yüksekliklerini ve görüntü çekim aralıklarını otomatik olarak hesaplar ve tarama mesafesini değiştirmenize ve görüntü çözünürlüğü ayarlamanıza olanak tanır. Aynı zamanda kameranın her zaman görüntülerin alındığı yüzeye doğru açılarla tutulması doğrudan tutulmasını sağlar. Ayarlar şunlardır:
+- *Bilinen/önceden tanımlanmış kameralar* görüntü örtüşmesi için gerekli katman yüksekliklerini ve görüntü çekim aralıklarını otomatik olarak hesaplar ve tarama mesafesini değiştirmenize ve görüntü çözünürlüğü ayarlamanıza olanak tanır. It also ensures that the camera is pointed directly at the surface when it is capturing images (i.e. at a right angle rather than some tangent). Ayarlar şunlardır:
- **Camera Orientation:** Dikey veya Yatay
- *Örtüşme*:
- **Front Lap:** Görüntünün yukardan aşağıya örtüşmesi. (arttırılırsa katman boyu küçülür katman sayısı artar).
- **Side Lap:** Görüntü kenarlarda örtüşür. (arttırılırsa, her turda/katman taramasında daha fazla görüntü çeker).
- - **Scan distance:**Uçuş yolunun yapıya olan mesafesi.
+ - **Scan distance:** Distance from the structure to the flight path.
- **Ground Res:** Yüzey için gerekli görüntü çözünürlüğü/numune kalitesi.
- *Custom camera* seçimi, kendi kamera özelliklerinizi girmenize olanak tanır, ancak aksi takdirde önceden tanımlanmış bir kamerayla aynı şekilde davranır.
\ No newline at end of file
diff --git a/tr/PlanView/pattern_survey.md b/tr/PlanView/pattern_survey.md
index f2b7aa8df..413810560 100644
--- a/tr/PlanView/pattern_survey.md
+++ b/tr/PlanView/pattern_survey.md
@@ -21,7 +21,7 @@ Bir gözlem görevi oluşturmak için:
Bu haritaya bir gözlem alanı ve görev listesine (sağda) bir *Survey* öğesi ekleyecektir.
-3. Haritada köşeleri sürükleyerek çokgenin şeklini değiştirebilirsiniz.
+3. On the map drag the vertices to change the shape of the polygon.
4. Yeni bir köşe noktası oluşturmak için var olan köşelerin ortalarındaki `(+)` semboüne tıklayın. Yeni köşe, yeni pozisyonlara çekilebilir.
diff --git a/tr/SettingsView/General.md b/tr/SettingsView/General.md
index 3e4e44181..254bce4d8 100644
--- a/tr/SettingsView/General.md
+++ b/tr/SettingsView/General.md
@@ -15,7 +15,7 @@ This section defines the display units used in the application.
The settings are:
- **Distance**: Meters | Feet
-- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres |SquareMiles
+- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres | SquareMiles
- **Speed**: Metres/second | Feet/second | Miles/hour | Kilometres/hour | Knots
- **Temperature**: Celsius | Fahrenheit
diff --git a/tr/SettingsView/OfflineMaps.md b/tr/SettingsView/OfflineMaps.md
index fb2a8407e..8165f0f96 100644
--- a/tr/SettingsView/OfflineMaps.md
+++ b/tr/SettingsView/OfflineMaps.md
@@ -2,12 +2,12 @@
-Offline Maps allows you to cache map tiles for use when not connected to the internet. You can create multiple offline sets, each for a different location.
+Offline Maps allows you to cache map tiles for use when not connected to the Internet. You can create multiple offline sets, each for a different location.
## Add new set
To create a new offline map set, click "Add new set". Which will take you to this page: 
-From here you can name you set as well as specify the zoom levels you want to cache. Move the map to the position you can to cache and then set the zoom levels and click Download to cache the tiles.
+From here you can name your set as well as specify the zoom levels you want to cache. Move the map to the position you want to cache and then set the zoom levels and click Download to cache the tiles.
To the left you can see previews of the min and max zoom levels you have chosen.
\ No newline at end of file
diff --git a/tr/SetupView/Firmware.md b/tr/SetupView/Firmware.md
index 72cba9db4..04c5add0d 100644
--- a/tr/SetupView/Firmware.md
+++ b/tr/SetupView/Firmware.md
@@ -8,7 +8,7 @@
## Yazılım Güncellemesi için Cihazı Bağlayın
-> **Caution** ** Aygıt Yazılımını yüklemeye başlamadan önce ** aracınıza olan tüm USB bağlantılarının * kesilmesi * (hem doğrudan hem de telemetri radyosu aracılığıyla) gerekir. Araca bir batarya ile * güç verilmemelidir *.
+> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be *disconnected* (both direct or through a telemetry radio). Araca bir batarya ile * güç verilmemelidir *.
1. İlk olarak üstteki araç çubuğundan **dişli** simgesini (*Vehicle Setup*), daha sonra kenar çubuğundan **Firmware**'i seçin.
@@ -26,7 +26,7 @@ Cihaz bağlandıktan sonra, hangi aygıt yazılımının yükleneceğini seçebi
- * ArduPilot * 'ı seçerseniz, aynı zamanda araç tipini belirleyen donanım yazılımını da seçmeniz gerekecektir (aşağıda gösterildiği gibi).
+ If you select *ArduPilot* you will also have to choose the specific firmware and the type of vehicle (as shown below).
@@ -42,4 +42,4 @@ Cihaz bağlandıktan sonra, hangi aygıt yazılımının yükleneceğini seçebi
-Yazılım yüklemesi tamamlandığında, cihaz / araç yeniden başlatılacak ve yeniden bağlanacaktır. Daha sonra [ gövdeyi](../SetupView/Airframe.md) (ve sonra sensörler, radyo vb.) Yapılandırmanız gerekir
\ No newline at end of file
+Once the firmware has finished loading the device/vehicle will reboot and reconnect. Daha sonra [ gövdeyi](../SetupView/Airframe.md) (ve sonra sensörler, radyo vb.) Yapılandırmanız gerekir
\ No newline at end of file
diff --git a/tr/SetupView/FlightModes.md b/tr/SetupView/FlightModes.md
index 7f3973ec8..d3cb75517 100644
--- a/tr/SetupView/FlightModes.md
+++ b/tr/SetupView/FlightModes.md
@@ -19,7 +19,7 @@ Bu bölüme erişmek için, üstteki araç çubuğundan **dişli** simgesini (Ve
ArduPilot'ta vericinizin tek bir kanalına 6'ya kadar farklı uçuş modu atayabilirsiniz (kanal Plane'de seçilebilir, ancak Copter'de kanal 5'e sabitlenmiştir).
-ArduCopter (yalnızca), 7-12. Kanallar için ek * Kanal Seçenekleri * belirlemenize de olanak tanır. Bunlar, bu anahtarlara işlevler atamanıza izin verir (örneğin, bir kamerayı açmak veya başlatmak için geri dönmek için). ArduCopter belgelerinde kanal yapılandırması hakkında ek bilgi bulunmaktadır: [Auxiliary Function Switches]
+ArduCopter (yalnızca), 7-12. Kanallar için ek * Kanal Seçenekleri * belirlemenize de olanak tanır. Bunlar, bu anahtarlara işlevler atamanıza izin verir (örneğin, bir kamerayı açmak veya başlatmak için geri dönmek için). There is additional information about channel configuration in the ArduCopter docs: [Auxiliary Function Switches](https://ardupilot.org/copter/docs/channel-7-and-8-options.html#channel-7-and-8-options)
Uçuş modlarını ayarlamak için:
@@ -50,7 +50,7 @@ Tüm değerler değiştirildikçe otomatik olarak kaydedilir.
- ** Tek Kanallı Mod Seçimi: ** Tek bir kanalda kodlanmış konumları değiştirmek için 6'ya kadar uçuş modu atayın.
- ** Çok Kanallı Mod Seçimi: ** Bir veya daha fazla kanalda kodlanmış konumların değiştirilmesi için modlar atayın. Bazı modlar, kanalları paylaşmak için kodlanmıştır veya diğer mod seçimlerine göre otomatik olarak tanımlanır / ayarlanır (çok kanallı mod seçiminin davranışı bazen kafa karıştırıcı olabilir).
-> **Tip** Önerilen yaklaşım * Tek Kanallı Mod Seçimi * 'i kullanmaktır çünkü anlaşılması ve yapılandırılması kolaydır. ArduPilot tarafından kullanılan yaklaşıma benzer.
+> **Tip** The recommended approach is to use *Single Channel Mode Selection* because it is easy to understand and configure. ArduPilot tarafından kullanılan yaklaşıma benzer.
### Tek Kanal Modu {#single_channel}
@@ -85,7 +85,7 @@ Verici üzerindeki 2 ve 3'de konumlu bir anahtarın konumlarını 6 uçuş modun
Aşağıdaki video, bunun * FrSky Taranis * vericisi (çok popüler ve şiddetle tavsiye edilen bir RC vericisi) ile nasıl yapıldığını göstermektedir. İşlem, iki gerçek anahtarın her bir pozisyon kombinasyonuna bir "mantıksal anahtar" atamayı içerir. Her mantıksal anahtar daha sonra aynı kanal üzerinde farklı bir PWM değerine atanır.
-
+
Ardından video, mod kanalını özelleştirmek ve 6 "slot" un her birine modları eşlemek için * QGroundControl * 'ın nasıl kullanılacağını gösterir. {% youtube %} http://www.youtube.com/watch?v=scqO7vbH2jo {% endyoutube %}
### Çok Kanallı Mod
diff --git a/tr/SetupView/Joystick.md b/tr/SetupView/Joystick.md
index d4a8eb268..f10bc1646 100644
--- a/tr/SetupView/Joystick.md
+++ b/tr/SetupView/Joystick.md
@@ -109,7 +109,7 @@ Aşağıdaki kumanda kollarının/kontrol cihazlarının nispeten yeni * QGround
### Sony Playstation 3/4 Kontrolcüleri
-İkisi de oldukça tavsiye edilir. "Kutudan çıkar çıkmaz" iyi çalışırlar ve uçuş modlarına eşleyebileceğiniz birçok düğme vardır.
+Both these joysticks are highly recommended. "Kutudan çıkar çıkmaz" iyi çalışırlar ve uçuş modlarına eşleyebileceğiniz birçok düğme vardır.
#### Sony PS4 - DualShock 4 Kontrolcü V2 (Kablosuz kurulum)
diff --git a/tr/SetupView/airframe_px4.md b/tr/SetupView/airframe_px4.md
index 22744ddd2..b8522e539 100644
--- a/tr/SetupView/airframe_px4.md
+++ b/tr/SetupView/airframe_px4.md
@@ -10,7 +10,7 @@ PX4 de gövde seçmek için:
The example above shows *Generic Hexarotor X geometry* selected from the *Hexarotor X* group.
-4. Click the **Apply and Restart** button to the top right of the screen.
+4. Click the **Apply and Restart** button on the top right of the screen.
5. Click **Apply** in the following prompt to save the settings and restart the vehicle.
diff --git a/tr/SetupView/sensors_ardupilot.md b/tr/SetupView/sensors_ardupilot.md
index 586ada197..163a6c138 100644
--- a/tr/SetupView/sensors_ardupilot.md
+++ b/tr/SetupView/sensors_ardupilot.md
@@ -56,7 +56,7 @@ To perform **Pressure** calibration:
## CompassMot (Optional)
-CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and where there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
+CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and when there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
To perform **CompassMot** calibration:
diff --git a/tr/SetupView/sensors_px4.md b/tr/SetupView/sensors_px4.md
index a8ce3f3b9..76c5ccd9d 100644
--- a/tr/SetupView/sensors_px4.md
+++ b/tr/SetupView/sensors_px4.md
@@ -37,9 +37,9 @@ The calibration steps are:
-4. When finished, *QGroundControl* will display a progress bar *Calibration complete* 
+4. When finished, *QGroundControl* will display *Calibration complete* and the progress bar will fill completely. 
-> **Note** If you move the vehicle *QGroundControl* will automatically restart the calibration.
+> **Note** If you move the vehicle during calibration, *QGroundControl* will automatically restart the calibration.
You can then proceed to the next sensor.
diff --git a/tr/SetupView/tuning_px4.md b/tr/SetupView/tuning_px4.md
index 38b54c7c7..9352d2a29 100644
--- a/tr/SetupView/tuning_px4.md
+++ b/tr/SetupView/tuning_px4.md
@@ -17,7 +17,7 @@ To use advanced tuning:
1. First select the *Tuning axis* to tune: **Rol**, **Pitch** or **Yaw** (each axis is tuned separately).
2. Fly the vehicle, observing the tracking on the chart.
- Adjust the *Tuning Values* (parameters) to improve the tracking shown on the graph
- - Set the **Increment/Decrement %** to a larger/smaller value for course/fine tuning
+ - Set the **Increment/Decrement %** to a larger/smaller value for coarse/fine tuning
- Press the **Save Values** button if a change improves tracking. > **Tip** At any point you can press **Reset To Saved Values** to restore the last saved good state.
- You can also **Clear**/**Stop** the chart using the buttons provided.
3. Tune the other axes.
\ No newline at end of file
diff --git a/tr/analyze_view/README.md b/tr/analyze_view/README.md
index 19b5d215e..6276b4f8e 100644
--- a/tr/analyze_view/README.md
+++ b/tr/analyze_view/README.md
@@ -9,5 +9,4 @@ The view provides tools to:
* [Download Logs](../analyze_view/log_download.md) — List, download and clear logs on the vehicle.
* [GeoTag Images (PX4)](../analyze_view/geotag_images.md) — Geotag survey mission images using the flight log (on a computer).
* [MAVLink Console (PX4)](../analyze_view/mavlink_console.md) — Access the the nsh shell running on the vehicle.
-* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
-* Vibration clip count
\ No newline at end of file
+* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — Display and chart received MAVLink messages/values.
\ No newline at end of file
diff --git a/tr/getting_started/download_and_install.md b/tr/getting_started/download_and_install.md
index f65bdf98b..69565e816 100644
--- a/tr/getting_started/download_and_install.md
+++ b/tr/getting_started/download_and_install.md
@@ -1,6 +1,6 @@
# İndirme ve Kurulum
-Aşağıdaki bölümler tüm platformlar için *QGroundControl*'ün [current stable release](../releases/release_notes.md)'lerini indirmek için kullanılabilir.
+The sections below can be used to download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
> **Tip** *QGroundControl*'i indirdikten sonra çalıştırmakta bir problem yaşıyorsanız [QGC Install/Config Problems](../Support/troubleshooting_qgc.md)'e bir göz atın!
diff --git a/tr/getting_started/quick_start.md b/tr/getting_started/quick_start.md
index 1a0cfcacd..a89cc6357 100644
--- a/tr/getting_started/quick_start.md
+++ b/tr/getting_started/quick_start.md
@@ -17,6 +17,7 @@
- [Setup](../SetupView/SetupView.md): Aracınızı yapılandırın ve ayarlayın.
- [Plan](../PlanView/PlanView.md): Otonom görevler oluşturun.
- [Fly](../FlyView/FlyView.md): Video akışıyla birlikte araç(lar)ınızı uçarken izleyin.
+ - [Analyze] ** Description of Analyze view is missing **
- Bağlı aracın durumunu öğrenmek için araç çubuğundaki *Status icons*'a tıklayın.
Kullanıcı arayüzü gayet açık olsa da, daha fazlasını öğrenmek için bu dokümantasyona başvurulabilir.
\ No newline at end of file
diff --git a/tr/toolbar/toolbar.md b/tr/toolbar/toolbar.md
index 3b669b33d..6aa75d799 100644
--- a/tr/toolbar/toolbar.md
+++ b/tr/toolbar/toolbar.md
@@ -12,7 +12,7 @@ Aşağıdaki simgeler ana *Views * arasında geçiş yapmak için kullanılır.
 **[Plan](../PlanView/PlanView.md)**
Otonom göevler oluşturun.
- **[Fly](../FlyView/FlyView.md)**
Araç(lar)ınızı uçarken video akışıyla birlikte gözlemleyin.
+ **[Fly](../FlyView/FlyView.md)**
Monitor your vehicle(s) while flying, including streaming video.
 **[Analyze](../analyze_view/README.md)**
Uçuş kayıtlarını indirebilir, gözlem görevindeki görüntüler coğrafi olark etiketlenebilir, MAVLink konsoluna erişebilirsiniz.
@@ -20,11 +20,11 @@ Aşağıdaki simgeler ana *Views * arasında geçiş yapmak için kullanılır.
Durum simgeleri *QGroundControl* bir araca bağlıyken gözükür. Bunlar araçla ilgili önemli bilgileri gösterir ve üstlerine tıklayarak daha ayrıntılı bilgilere erişilebilir.
- **Vehicle Messages**
Araçtan gelen mesajları görmek için tıklayın. Eğer kritik bir mesaj varsa bir Yield işaretine dönüşecektir.
+  **Vehicle Messages**
Click to show a list of messages from the vehicle. Note that version on the right is displayed when there are critical messages.
- **GPS Status**
Uydu sayısını ve geçerli hdopu gösterir.
+ **GPS Status**
Shows you satellite count and curent HDOP.
- **RC RSSI**
RS sinyal gücü bilgisi.
+ **RC RSSI**
RC signal strength information.
 **Telemetry RSSI**
Telemetri sinyalleri güç bilgisi.
diff --git a/zh/FlyView/FlyView.md b/zh/FlyView/FlyView.md
index 7c6af0c42..e7667fa9f 100644
--- a/zh/FlyView/FlyView.md
+++ b/zh/FlyView/FlyView.md
@@ -22,7 +22,7 @@
- **Fly Toolbar:** Key status information for sensors (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status).
- Select the sensor indicators to view more detail.
- Press the *Flight mode* text (e.g. "Hold") to select a new mode. Not every mode may be available.
- - Press the *Armed/Disarmed* text to toggle the armed state. If flying you can press this text to *Emergency Stop*.
+ - Press the *Armed/Disarmed* text to toggle the armed state. While flying you can press this text for *Emergency Stop*.
- **Fly tools:** You can use these to:
- Toggle between takeoff/land.
- Pause/restart the current operation (e.g. landing, or the mission).
@@ -32,7 +32,7 @@
- **[Instrument Panel](#instrument_panel):** A multi-page widget that displays vehicle information including: telemetry, camera, video, system health, and vibration.
- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window.
- Press the element to switch *Video* and *Map* to foreground.
- - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. It also support directly connected UVC device support. QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
+ - *QGroundControl* supports RTP and RTSP video streaming over your vehicles UDP connection. It also supports directly connected UVC devices. QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md).
- A [Telemetry Overlay](../FlyView/VideoOverlay.md) is automatically generated as a subtitle file
- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Slide to start operation. Press **X** to cancel.
@@ -42,7 +42,7 @@ There are a number of other elements that are not displayed by default/are only
The instrument panel is a multi-page widget that displays information about the current vehicle, including: telemetry, camera, video, system health, and vibration information.
-The default page displays vehicle telemetry - use the drop down menu on the to right to select the other options.
+The default page displays vehicle telemetry - use the drop down menu on the top right to select the other options.
### Values (Telemetry)
@@ -78,7 +78,7 @@ The video page is used to enable/disable video streaming. When enabled, you can
### Health
-The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any systems change to unhealthy.
+The health page shows you the health of the systems within your vehicle. *QGroundControl* will switch to this page automatically if any system changes to unhealthy.
 
@@ -98,11 +98,11 @@ The following sections describe how to perform common operations/tasks in the Fl
An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly.
-To you the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
+To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../SettingsView/General.md) and selecting the **Use preflight checklist** checkbox. The tool will then be added to the *Flight Tools*. Press it to open the checklist:
-Once you have performed each test, select it on it in the UI to mark it as complete.
+Once you have performed each test, select it on the UI to mark it as complete.
### Arm {#arm}
@@ -126,7 +126,7 @@ Disarming the vehicle stops the motors (making the vehicle safe). To disarm the
### Emergency Stop {#emergency_stop}
-Emergency stop is effectively the same as disarming the vehicle while you are flying. Your vehicle will crash!
+Emergency stop is effectively the same as disarming the vehicle while it is flying. Your vehicle will crash!
To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is flying.
@@ -134,7 +134,7 @@ To disarm the vehicle select **Armed** in the *Fly Toolbar* when the vehicle is
### Takeoff {#takeoff}
-> **Tip** If you are starting a mission for a multicopter *QGroundControl* will automatically perform the takeoff step.
+> **Tip** If you are starting a mission for a multicopter, *QGroundControl* will automatically perform the takeoff step.
To takeoff (when landed):
@@ -155,14 +155,14 @@ You can land at the current position at any time while flying:
### RTL/Return
-Return to the home position at any time while flying:
+Return to a "safe point" at any time while flying:
1. Press the **RTL** button in the *Fly Tools*.
2. Confirm RTL using the slider.
-
+
-> **Note** The vehicle may also land at the home position, depending on its type and configuration.
+> **Note** Vehicles commonly return to the "home" (takeoff) location and land. This behaviour depends on the vehicle type and configuration. For example, rally points or mission landings may be used as alternative return targets.
### Change Altitude {#change_altitude}
@@ -181,7 +181,7 @@ You can change altitude while flying, except when in a mission:
After taking off you can specify that you want to fly to a particular location.
-1. Press the map where you want the vehicle to move and select **Go to location** on the popup.
+1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup.
@@ -197,7 +197,7 @@ After taking off you can specify that you want to fly to a particular location.
After taking off you can specify that you want to orbit a particular location.
-1. Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
+1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup.
@@ -211,7 +211,7 @@ After taking off you can specify that you want to orbit a particular location.
### Pause
-You can pause most operations, including taking off, landing, RTL, missions, Orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
+You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle.
> **Note** You cannot pause a *Goto location* operation.
@@ -247,7 +247,7 @@ To start a mission from landed:
You can *continue* mission from the *next* waypoint when you're flying (the *Continue Mission* confirmation slider is often displayed by default after you takeoff).
-> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from you place in the mission).
+> **Note** Continue and [Resume mission](#resume_mission) are different! Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission).
You can continue the current mission while (unless already in a mission!):
@@ -284,7 +284,7 @@ You will be prompted to remove the mission from the vehicle after the mission co
### Display Video {#video_switcher}
-When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (below we show the video in the foreground).
+When video streaming is enabled, *QGroundControl* will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. You can press the switcher anywhere to toggle *Video* and *Map* to foreground (in the image below, the video is shown in the foreground).
@@ -295,7 +295,7 @@ You can further configure video display using controls on the switcher:
-- Resize the switcher by dragging the icon in the to right corner.
+- Resize the switcher by dragging the icon in the top right corner.
- Hide the switcher by pressing the toggle icon in the lower left.
- Detach the video switcher window by pressing on the icon in its top left corner (once detached, you can move and resize the window just like any other in your OS). If you close the detached window the switcher will re-lock to the QGC Fly view.
diff --git a/zh/FlyView/VideoOverlay.md b/zh/FlyView/VideoOverlay.md
index 081fd5dbc..bccb9895c 100644
--- a/zh/FlyView/VideoOverlay.md
+++ b/zh/FlyView/VideoOverlay.md
@@ -1,6 +1,6 @@
# Video Overlay
-When QGroundControl is recording a video stream to file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
+When QGroundControl is recording a video stream to a file, it will also export a subtitle file with telemetry data that can be used to overlay the telemetry on the video during playback. Whichever telemetry values are selected for display in the telemetry [values widget](FlyView.md#values-telemetry) will also be exported to the overlay. The overlay values are updated at 1Hz.
diff --git a/zh/FlyView/replay_flight_data.md b/zh/FlyView/replay_flight_data.md
index 3b0a8b08a..b2af57ad7 100644
--- a/zh/FlyView/replay_flight_data.md
+++ b/zh/FlyView/replay_flight_data.md
@@ -2,7 +2,7 @@
> **Warning** This feature is intended primarily for **autopilot developers**/**vehicle creators**. It is only supported on desktop builds (Windows, Linux, Mac OS).
-The *Replay Flight Data* features allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
+The *Replay Flight Data* feature allows users to replay a telemetry log, enabling review of past or problematic flights. The flight can be started, paused, stopped, restarted etc.
> **Note** *QGroundControl* treats flight replay like an active connection. When you pause/stop playing, the ground station will report "Communication Lost" and wait for disconnection or for more messages.
@@ -18,7 +18,7 @@ To replay a flight:
1. When a log is loaded you can use the:
- **Pause/Play** button to pause and restart playing.
- *Slider* to drag to a new position in the log.
- - *Rate* selector to choose how quickly the log is run.
-1. To stop relay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting the **Load Telemetry Log** button will be displayed.
+ - *Rate* selector to choose the playback speed.
+1. To stop replay (i.e. to load a new file to replay), first pause the flight, and then select **Disconnect** (when it appears). After disconnecting, the **Load Telemetry Log** button will be displayed.
> **Tip** You can inspect the running replay in more detail using the [MAVLink Inspector](../analyze_view/mavlink_inspector.md).
diff --git a/zh/PlanView/Pattern.md b/zh/PlanView/Pattern.md
index fd3fcd5a4..334b6e235 100644
--- a/zh/PlanView/Pattern.md
+++ b/zh/PlanView/Pattern.md
@@ -9,6 +9,6 @@ The *Pattern tools* (in the [PlanView](../PlanView/PlanView.md) *Plan Tools*) al
| [Survey](../PlanView/pattern_survey.md) | Create a grid flight pattern over a polygonal area.
You can specify the polygon as well as the specifications for the grid and camera settings appropriate for creating geotagged images. | All |
| [Structure Scan](../PlanView/pattern_structure_scan_v2.md) | Create a grid flight pattern that captures images over vertical surfaces (polygonal or circular).
-These are typically used for the visual inspection or creation of 3d models of structures. | MultiCopter, VTOL |
+These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL |
| [Corridor Scan](../PlanView/pattern_corridor_scan.md) | Create a flight pattern which follows a poly-line (for example, to survey a road). | All |
| [Fixed Wing Landing](../PlanView/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing |
\ No newline at end of file
diff --git a/zh/PlanView/PatternPresets.md b/zh/PlanView/PatternPresets.md
index ec58ca1ee..fd5718284 100644
--- a/zh/PlanView/PatternPresets.md
+++ b/zh/PlanView/PatternPresets.md
@@ -29,4 +29,4 @@ If you want to view what the exact settings are for a Preset switch back to **Cu
## Presets In A Plan File
-The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user incorrect behavior may occur if that other user also have a preset of the same name but different settings.
\ No newline at end of file
+The currently selected Preset is also saved in the Plan file such that when you load the Plan back the preset will once again be selected. Keep in mind that presets are specific to your version of QGroundControl. If you share a Plan file with a preset with another user, incorrect behavior may occur if that other user also has a preset of the same name but different settings.
\ No newline at end of file
diff --git a/zh/PlanView/PlanGeoFence.md b/zh/PlanView/PlanGeoFence.md
index 89e856ccd..5a4c4df39 100644
--- a/zh/PlanView/PlanGeoFence.md
+++ b/zh/PlanView/PlanGeoFence.md
@@ -15,7 +15,7 @@ To create a GeoFence:
-3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** buttons, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
+3. Insert a circular or polygon region by pressing the **Circular Fence** or **Polygon Fence** button, respectively. A new region will be added to the map and to the associated list of fences below the buttons.
> **Tip** You can create multiple regions by pressing the buttons multiple times, allowing complex geofence definitions to be created.
@@ -24,7 +24,7 @@ To create a GeoFence:
- Move the region by dragging the central dot on the map
- - Resize the circle by dragging the map dot on the edge of the circle (or you can change the radius value in the fence panel).
+ - Resize the circle by dragging the dot on the edge of the circle (or you can change the radius value in the fence panel).
- Polygon region:
@@ -38,7 +38,7 @@ To create a GeoFence:
You can select a geofence region to edit by selecting its *Edit* radio button in the GeoFence panel. You can then edit the region on the map as described in the previous section.
-Regions can be deleted by pressing the associated **Del** button
+Regions can be deleted by pressing the associated **Del** button.
## Upload a GeoFence
diff --git a/zh/PlanView/PlanView.md b/zh/PlanView/PlanView.md
index 283be976e..be87510e8 100644
--- a/zh/PlanView/PlanView.md
+++ b/zh/PlanView/PlanView.md
@@ -36,7 +36,7 @@ The following sections explain some of the details in the view.
## Planned Home Position {#planned_home}
-The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to a vehicle). It is used by QGC to estimate mission times and to draw waypoint lines.
+The *Planned Home* shown in *Plan View* is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC). It is used by QGC to estimate mission times and to draw waypoint lines.
@@ -44,7 +44,7 @@ You should move/drag the planned home position to roughly the location where you
-> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this where the vehicle will return in Return/RTL mode).
+> **Tip** The Fly View displays the *actual* home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
## Plan Tools {#plan_tools}
@@ -124,7 +124,7 @@ The [Planned Home Position](#planned_home) section allows you to simulate the ve
> **Note** This is only the *planned* home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming.
-The section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
+This section allows you to set the **Altitude** and **Set Home to Map Centre** (you can move it to another position by dragging it on the map).
#### Camera
diff --git a/zh/PlanView/pattern_fixed_wing_landing.md b/zh/PlanView/pattern_fixed_wing_landing.md
index 765bf486e..43a12d2a9 100644
--- a/zh/PlanView/pattern_fixed_wing_landing.md
+++ b/zh/PlanView/pattern_fixed_wing_landing.md
@@ -12,7 +12,7 @@ Both the loiter and land points can be dragged to new positions, and a number of
To create a landing pattern:
-1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*).
+1. Open [PlanView](../PlanView/PlanView.md) *Plan Tools*.
2. Choose the *Pattern Tool* from the *Plan Tools* and then select *Fixed Wing Landing Pattern*.
@@ -21,7 +21,7 @@ To create a landing pattern:
-3. Click on the map to create both the loiter and landing points. These can be moved on the map.
+3. Click on the map to create both the loiter point and the landing point. These can be moved on the map.
Additional settings are covered in the next section.
@@ -52,8 +52,8 @@ The configurable options are:
- **Heading** - Heading from loiter point to land point.
- **Altitude** - Altitude for landing point (nominally zero).
- *Radio Buttons*
- - **Landing Dist** - Distance between loiter and landing points.
- - **Glide Slope** - Glide slope between loiter and landing points.
+ - **Landing Dist** - Distance between loiter point and landing point.
+ - **Glide Slope** - Glide slope between loiter point and landing point.
- **Altitudes relative to home** - Check to set all altitudes in mission item to be relative to home (default is AMSL).
## Implementation
diff --git a/zh/PlanView/pattern_structure_scan_v2.md b/zh/PlanView/pattern_structure_scan_v2.md
index 60d90ebbd..486d4bdcb 100644
--- a/zh/PlanView/pattern_structure_scan_v2.md
+++ b/zh/PlanView/pattern_structure_scan_v2.md
@@ -1,6 +1,6 @@
# Structure Scan (Plan Pattern)
-A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3d models of structures.
+A *Structure Scan* allows you to create a grid flight pattern that captures images over *vertical surfaces* (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint. Structure Scans are typically used for the visual inspection or creating 3D models of structures.
*Structure Scans* may be inserted into a mission using the Plan view **Pattern > Structure Scan** tool.
@@ -58,7 +58,7 @@ The user can always configure the following settings:
- **Start scan from top/bottom:** The direction in which layers are scanned.
- **Structure height:** The height of the object being scanned.
-- **Scan distance:** Distance from the structure of the flight path.
+- **Scan distance:** Distance from the structure to the flight path.
- **Entrance/Exit Alt:** Use this setting to avoid obstacles between the last/next waypoint and the structure to be scanned.
- The vehicle will fly to the *Entrance/Exit* point at this altitude and then descend to the initial layer to start the scan.
- The vehicle will ascend to this altitude after completing the scan and then move to the next waypoint.
@@ -72,13 +72,13 @@ The remaining settings depend on the *camera mode*:
- **Trigger Distance:** The distance between each camera trigger. The camera is only triggered while flying the layer path. It does not trigger images while transitioning from one layer to the next.
- **Gimbal Pitch** - Gimbal pitch you want to use for the scan.
-- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is always pointed directly at the right angles to the surface which it is capturing images. The settings are:
+- *Known/pre-defined cameras* automatically calculates layer heights and image triggering from required image overlap, and allows you to trade off scan distance and require image resolution. It also ensures that the camera is pointed directly at the surface when it is capturing images (i.e. at a right angle rather than some tangent). The settings are:
- **Camera Orientation:** Portrait or Landscape
- *Overlap*:
- **Front Lap:** Image overlap from top to bottom (increasing shrinks layer height and increases layer count).
- **Side Lap:** Image overlap at sides (increasing takes more images in each lap/layer scan).
- - **Scan distance:** Distance from the structure of the flight path.
+ - **Scan distance:** Distance from the structure to the flight path.
- **Ground Res:** Required image resolution/sample quality of surface.
- *Custom camera* selection allows you to enter your own camera characteristics, but otherwise behaves the same as a predefined camera.
\ No newline at end of file
diff --git a/zh/PlanView/pattern_survey.md b/zh/PlanView/pattern_survey.md
index d61481457..bed02fab1 100644
--- a/zh/PlanView/pattern_survey.md
+++ b/zh/PlanView/pattern_survey.md
@@ -21,7 +21,7 @@ To create a survey:
This will add a survey grid to the map, and a *Survey* item to the mission list (on the right).
-3. On the map drag the vertices to the change the shape of the polygon.
+3. On the map drag the vertices to change the shape of the polygon.
4. Click the `(+)` symbol between existing vertices to create a new vertix. The new vertix can then be dragged into a new position.
diff --git a/zh/SettingsView/General.md b/zh/SettingsView/General.md
index 3e4e44181..254bce4d8 100644
--- a/zh/SettingsView/General.md
+++ b/zh/SettingsView/General.md
@@ -15,7 +15,7 @@ This section defines the display units used in the application.
The settings are:
- **Distance**: Meters | Feet
-- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres |SquareMiles
+- **Area**: SquareMetres | SquareFeet | SquareKilometers | Hectares | Acres | SquareMiles
- **Speed**: Metres/second | Feet/second | Miles/hour | Kilometres/hour | Knots
- **Temperature**: Celsius | Fahrenheit
diff --git a/zh/SettingsView/OfflineMaps.md b/zh/SettingsView/OfflineMaps.md
index fb2a8407e..8165f0f96 100644
--- a/zh/SettingsView/OfflineMaps.md
+++ b/zh/SettingsView/OfflineMaps.md
@@ -2,12 +2,12 @@
-Offline Maps allows you to cache map tiles for use when not connected to the internet. You can create multiple offline sets, each for a different location.
+Offline Maps allows you to cache map tiles for use when not connected to the Internet. You can create multiple offline sets, each for a different location.
## Add new set
To create a new offline map set, click "Add new set". Which will take you to this page: 
-From here you can name you set as well as specify the zoom levels you want to cache. Move the map to the position you can to cache and then set the zoom levels and click Download to cache the tiles.
+From here you can name your set as well as specify the zoom levels you want to cache. Move the map to the position you want to cache and then set the zoom levels and click Download to cache the tiles.
To the left you can see previews of the min and max zoom levels you have chosen.
\ No newline at end of file
diff --git a/zh/SetupView/Firmware.md b/zh/SetupView/Firmware.md
index 6e31a6fb8..c06360457 100644
--- a/zh/SetupView/Firmware.md
+++ b/zh/SetupView/Firmware.md
@@ -8,7 +8,7 @@
## Connect Device for Firmware Update
-> **Caution** **Before you start installing Firmware** all USB connections to you vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
+> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be *disconnected* (both direct or through a telemetry radio). The vehicle must *not be* powered by a battery.
1. First select the **Gear** icon (*Vehicle Setup*) in the top toolbar and then **Firmware** in the sidebar.
@@ -26,7 +26,7 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
- If you select *ArduPilot* you will also have to choose the specific firmware the type of vehicle (as shown below).
+ If you select *ArduPilot* you will also have to choose the specific firmware and the type of vehicle (as shown below).
@@ -42,4 +42,4 @@ Once the device is connected you can choose which firmware to load (*QGroundCont
-Once the firmware has completed loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
+Once the firmware has finished loading the device/vehicle will reboot and reconnect. Next you will need to configure the [airframe](../SetupView/Airframe.md) (and then sensors, radio, etc.)
\ No newline at end of file
diff --git a/zh/SetupView/FlightModes.md b/zh/SetupView/FlightModes.md
index 18d026577..dbbfae538 100644
--- a/zh/SetupView/FlightModes.md
+++ b/zh/SetupView/FlightModes.md
@@ -19,7 +19,7 @@ To access this section, select the **Gear** icon (Vehicle Setup) in the top tool
On ArduPilot you can assign up to 6 different flight modes to a single channel of your transmitter (the channel is selectable on Plane, but fixed to channel 5 on Copter).
-ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: \[Auxiliary Function Switches\](
+ArduCopter (only) also allows you to specify additional *Channel Options* for channels 7-12. These allow you to assign functions to these switches (for example, to turn on a camera, or return to launch). There is additional information about channel configuration in the ArduCopter docs: [Auxiliary Function Switches](https://ardupilot.org/copter/docs/channel-7-and-8-options.html#channel-7-and-8-options)
To set the flight modes:
@@ -50,7 +50,7 @@ All values are automatically saved as they are changed.
- **Single Channel Mode Selection:** Assign up to 6 flight modes to switch positions encoded in a single channel.
- **Multi Channel Mode Selection:** Assign modes to switch positions encoded in one or more channels. Some modes are hard coded to share channels, or are defined/set automatically based on other mode selections (the behaviour of multi-channel mode selection can sometimes be confusing).
-> **Tip** The recommended approach is use *Single Channel Mode Selection* because it easy to understand and configure. It is similar to the approach used by ArduPilot.
+> **Tip** The recommended approach is to use *Single Channel Mode Selection* because it is easy to understand and configure. It is similar to the approach used by ArduPilot.
### Single-Channel Mode {#single_channel}
@@ -85,7 +85,7 @@ It is common to use the positions of a 2- and a 3-position switch on the transmi
The video below shows how this is done with the *FrSky Taranis* transmitter (a very popular and highly recommended RC transmitter). The process involves assigning a "logical switch" to each combination of positions of the two real switches. Each logical switch is then assigned to a different PWM value on the same channel.
-
+
The video then shows how to use *QGroundControl* to specify the mode channel and map modes to each of the 6 "slots". {% youtube %} http://www.youtube.com/watch?v=scqO7vbH2jo {% endyoutube %}
### Multi-Channel Mode
diff --git a/zh/SetupView/Joystick.md b/zh/SetupView/Joystick.md
index f719efb77..7e8fa169e 100644
--- a/zh/SetupView/Joystick.md
+++ b/zh/SetupView/Joystick.md
@@ -109,7 +109,7 @@ The following joysticks/controllers have been shown to work with relatively rece
### Sony Playstation 3/4 Controllers
-These are both highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
+Both these joysticks are highly recommended. They work well "out of the box" and have many buttons that you can map to flight modes.
#### Sony PS4 - DualShock 4 Controller V2 (Wireless setup)
diff --git a/zh/SetupView/airframe_px4.md b/zh/SetupView/airframe_px4.md
index 83ef87c3d..89620f8b8 100644
--- a/zh/SetupView/airframe_px4.md
+++ b/zh/SetupView/airframe_px4.md
@@ -10,7 +10,7 @@ To select the airframe in PX4:
The example above shows *Generic Hexarotor X geometry* selected from the *Hexarotor X* group.
-4. Click the **Apply and Restart** button to the top right of the screen.
+4. Click the **Apply and Restart** button on the top right of the screen.
5. Click **Apply** in the following prompt to save the settings and restart the vehicle.
diff --git a/zh/SetupView/sensors_ardupilot.md b/zh/SetupView/sensors_ardupilot.md
index 586ada197..163a6c138 100644
--- a/zh/SetupView/sensors_ardupilot.md
+++ b/zh/SetupView/sensors_ardupilot.md
@@ -56,7 +56,7 @@ To perform **Pressure** calibration:
## CompassMot (Optional)
-CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and where there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
+CompassMot calibration is optional! It is recommended for vehicles that only have an internal compass and when there is significant interference on the compass from the motors, power wires, etc. CompassMot only works well if you have a battery current monitor because the magnetic interference is linear with current drawn.
To perform **CompassMot** calibration:
diff --git a/zh/SetupView/sensors_px4.md b/zh/SetupView/sensors_px4.md
index a8ce3f3b9..76c5ccd9d 100644
--- a/zh/SetupView/sensors_px4.md
+++ b/zh/SetupView/sensors_px4.md
@@ -37,9 +37,9 @@ The calibration steps are:
-4. When finished, *QGroundControl* will display a progress bar *Calibration complete* 
+4. When finished, *QGroundControl* will display *Calibration complete* and the progress bar will fill completely. 
-> **Note** If you move the vehicle *QGroundControl* will automatically restart the calibration.
+> **Note** If you move the vehicle during calibration, *QGroundControl* will automatically restart the calibration.
You can then proceed to the next sensor.
diff --git a/zh/SetupView/tuning_px4.md b/zh/SetupView/tuning_px4.md
index 38b54c7c7..9352d2a29 100644
--- a/zh/SetupView/tuning_px4.md
+++ b/zh/SetupView/tuning_px4.md
@@ -17,7 +17,7 @@ To use advanced tuning:
1. First select the *Tuning axis* to tune: **Rol**, **Pitch** or **Yaw** (each axis is tuned separately).
2. Fly the vehicle, observing the tracking on the chart.
- Adjust the *Tuning Values* (parameters) to improve the tracking shown on the graph
- - Set the **Increment/Decrement %** to a larger/smaller value for course/fine tuning
+ - Set the **Increment/Decrement %** to a larger/smaller value for coarse/fine tuning
- Press the **Save Values** button if a change improves tracking. > **Tip** At any point you can press **Reset To Saved Values** to restore the last saved good state.
- You can also **Clear**/**Stop** the chart using the buttons provided.
3. Tune the other axes.
\ No newline at end of file
diff --git a/zh/analyze_view/README.md b/zh/analyze_view/README.md
index 38de32323..eeb41638a 100644
--- a/zh/analyze_view/README.md
+++ b/zh/analyze_view/README.md
@@ -9,5 +9,4 @@ The view provides tools to:
* [日志下载](../analyze_view/log_download.md) - 列出、下载和清空设备上的日志。
* [图像地理信息标签(PX4)](../analyze_view/geotag_images.md) - 利用飞行日志将航测图片打上地理信息(导入电脑后)。
* [MAVLink Console (PX4)](../analyze_view/mavlink_console.md) — 读写存取 nsh shell 在已经启动运行的设备上。
-* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — 显示和记录已接收到的 信息/参数。
-* Vibration clip count
\ No newline at end of file
+* [MAVLink Inspector](../analyze_view/mavlink_inspector.md) — 显示和记录已接收到的 信息/参数。
\ No newline at end of file
diff --git a/zh/getting_started/download_and_install.md b/zh/getting_started/download_and_install.md
index 7d97c85e7..8f2b287bc 100644
--- a/zh/getting_started/download_and_install.md
+++ b/zh/getting_started/download_and_install.md
@@ -1,6 +1,6 @@
# 下载和安装
-以下部分内容可被用于在对应每个工作平台上，下载*QGroundControl*当前的[稳定版本](../releases/release_notes.md)。
+The sections below can be used to download the [current stable release](../releases/release_notes.md) of *QGroundControl* for each platform.
> **小贴士** 如果您在安装完*QGroundControl*后运行时遇到了任何问题，可以查看 [QGC 安装/配置问题集](../Support/troubleshooting_qgc.md)
diff --git a/zh/getting_started/quick_start.md b/zh/getting_started/quick_start.md
index aceb84ec4..812be748a 100644
--- a/zh/getting_started/quick_start.md
+++ b/zh/getting_started/quick_start.md
@@ -17,6 +17,7 @@
- [Setup](../SetupView/SetupView.md)：配置和调试你的设备。
- [Plan](../PlanView/PlanView.md)：创建自主自动执行的任务
- [Fly](../FlyView/FlyView.md)：在飞行时监测您的车辆，包括视频流。
+ - [Analyze] ** Description of Analyze view is missing **
- 点击工具栏上的*Status 图标*来确认已连接设备的状态。
虽然软件的界面相当直观亲和，但是这篇文档也能给您带来更多信息让您更加容易上手把玩QGC。
\ No newline at end of file
diff --git a/zh/toolbar/toolbar.md b/zh/toolbar/toolbar.md
index bdb93bcc4..d667025a0 100644
--- a/zh/toolbar/toolbar.md
+++ b/zh/toolbar/toolbar.md
@@ -12,7 +12,7 @@ The following icons are used to switch between the main *Views*. These are displ
 **[Plan](../PlanView/PlanView.md)**
Create autonomous missions.
- **[Fly](../FlyView/FlyView.md)**
Monitor you vehicle(s) while flying, including streaming video.
+ **[Fly](../FlyView/FlyView.md)**
Monitor your vehicle(s) while flying, including streaming video.
 **[Analyze](../analyze_view/README.md)**
Download logs, geotag images from a survey mission, access the MAVLink console.
@@ -20,11 +20,11 @@ The following icons are used to switch between the main *Views*. These are displ
Status icons are displayed when *QGroundControl* is connected to a vehicle. These show the high level status of the vehicle, and can be clicked to see more detailed information.
- **Vehicle Messages**
Click to show a dropdown of messages from the vehicle. This will change to a Yield sign if there are critical messages.
+  **Vehicle Messages**
Click to show a list of messages from the vehicle. Note that version on the right is displayed when there are critical messages.
- **GPS Status**
Shows you satellite count and curent hdop.
+ **GPS Status**
Shows you satellite count and curent HDOP.
- **RC RSSI**
RS signal strength information.
+ **RC RSSI**
RC signal strength information.
 **Telemetry RSSI**
Telemetry signals strength information.