Use "low-level" and "high-level" instead of "low level" and "high level" #10285
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
Co-Authored-By: John Veness <2512915+JohnVeness@users.noreply.github.com>
tetrapod00
added
enhancement
area:manual
This was referenced Nov 18, 2024
mhilbrunner
approved these changes
Nov 18, 2024
Member
|
Thanks for the salvage, and thanks @JohnVeness for bringing this up and doing all the initial work. Apologies again that we didn't get back on that one in time! |
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.
Supersedes #9882.
This PR consistently uses "low-level" and "high-level" as adjective phrases. Notably, "High-level multiplayer" is already used as the title of a section in the manual.