Use intra-doc links, capitalize GBM wording
#7
Conversation
This file contains hidden or 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
And some more fixes: - Don't use `no_run` in markdown, this only works in rustdoc; - Replace `gbm_bo_write`/`gbm_bo_get_fd` with intra-doc link to its Rust counterpart; - Consistently use two spaces after a period; - Fix a tiny typo in `optain`.
Contributor
Author
|
Rebased and updated the targeting branch to |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
And some more fixes:
no_runin markdown, this only works in rustdoc;gbm_bo_writewith intra-doc link to its Rust counterpart;optain.Not sure whether to submit this to
masterordevelop, is there any reason to have two branches when a release will eventually be tagged anyway?