Skip to content

docs: fix Mission API reference links and messages typo #2924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
julianoes merged 1 commit into from
Jul 14, 2026
+4 −4
Merged

docs: fix Mission API reference links and messages typo #2924

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/en/cpp/guide/general_usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,11 +115,11 @@ The implication is that developers will need to separately monitor the completio

### Missions

The [Mission](../api_reference/classmavsdk_1_1_mission.html) and [MissionItem](../api_reference/structmavsdk_1_1_mission_1_1_mission_item.html) APIs provide a simplified but often useful *subset* of MAVLink mission commands as a developer-friendly API.
The [Mission](../api_reference/classmavsdk_1_1_mission.md) and [MissionItem](../api_reference/structmavsdk_1_1_mission_1_1_mission_item.md) APIs provide a simplified but often useful *subset* of MAVLink mission commands as a developer-friendly API.

Not every mission command behaviour supported by the protocol and PX4 will be supported by the Mission plugins.

In order to access the full mission API, the [MissionRaw](../api_reference/classmavsdk_1_1_mission_raw.html) plugin can be used instead.
In order to access the full mission API, the [MissionRaw](../api_reference/classmavsdk_1_1_mission_raw.md) plugin can be used instead.

The MissionRaw also allows to [import QGC mission files](https://mavsdk.mavlink.io/main/en/cpp/api_reference/classmavsdk_1_1_mission_raw.html#classmavsdk_1_1_mission_raw_1a2a4ca261c37737e691c6954693d6d0a5).
The MissionRaw also allows to [import QGC mission files](https://mavsdk.mavlink.io/main/en/cpp/api_reference/classmavsdk_1_1_mission_raw.md#classmavsdk_1_1_mission_raw_1a2a4ca261c37737e691c6954693d6d0a5).

2 changes: 1 addition & 1 deletion docs/en/cpp/guide/mavlink_direct.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ MavlinkDirect works at runtime instead of compile-time, so instead of having the

## Load custom MAVLink XML/ MAVLink dialects

By default all messsages from the [common.xml](https://mavlink.io/en/messages/common.html) MAVLink dialect are available, loaded in.
By default all messages from the [common.xml](https://mavlink.io/en/messages/common.html) MAVLink dialect are available, loaded in.

MavlinkDirect allows to load your own/custom MAVLink messages or other dialects.

Expand Down
Loading