-
Notifications
You must be signed in to change notification settings - Fork 38
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.
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
manual typos and formatting inconsistencies #361
Merged
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
muzimuzhi
reviewed
Jun 28, 2020
Mo-Gul
commented
Jul 10, 2020
muzimuzhi
approved these changes
Jul 10, 2020
Many thanks for reviewing (again) @muzimuzhi! |
hmenke
reviewed
Apr 3, 2021
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.
So far fixed some typos and removed double/multiple spaces.
Things that still can be done to harmonize/correct stuff in manual:
behaviour
tobehavior
--> I prefer US spellingsection~
<-->Section~
--> most of the\ref
prefixes use the latter, so I'd harmonize to that$x$ coordinate
<-->$x$-coordinate
B\'ezier
--> replace by UTF-8 character -->Bézier
Are there any opinions/arguments against that proposed changes? If not, I would apply them one by one.
The changes should be in sync with the TikZ manual, see the corresponding pull request pgf-tikz/pgf#886.