Fix up MAV_X_RATE as html tag doesn't render #12449
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-Authored-By: Beat Küng <beat-kueng@gmx.net>
|
Thanks. YOur change suggestion committed. Merge at will. |
bkueng
approved these changes
Jul 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A HTML tag in the MAV_X_PARAM doc is not rendered when the param is displayed in markdown so the text makes no sense. This removes the tags and also clarifies how maximum data rate is determined.
See PX4/PX4-user_guide#508 for more context.
@bkueng FYI, we can use
>etc if you want to use this kind of markup in params.