I have fixed a grammatical mistake (specifically, a lack of number agreement). Previously, the sentence in question did not, construed strictly, make sense. Also, I'm doing this to practice doing pull requests!
Cleaned up translation guidelines:
- Reworded and simplified the first paragraph.
- Do not require the optional BCP47 region code for language tags.
- Do not require the existence of the relative English page before
adding a new page in a different language.
- Fix spelling and wording.
the cla-assistant link leads to a page requesting the user to sign it, which may not be as friendly
since prospective contributors may want to simply read the CLA without a prompt to sign it.
- moved one entry from the general guidelines, since now there's a specific section for tokens;
- reordered and numbered the entries, for clarity and ease of reference
- rewrote some passages for clarity and conciseness.
- adjust whitespace & line breaks to make the markdown source more readable and consistent
- remove "we"/"our", to avoid reinforcing the "us vs. them" paradigm
- clarify a couple passages
- remove obsolete license agreement notice, now covered by the CLA
- remove redundant (and oddly specific) plea for contributions and the end of the document,
since there's already one at the beginning
- remove a redundant example of commit message format
* add subsections to "submit a PR" section
this allows the reader to visually separate the instructions and makes the longer git-command section less prone to trigger a TLDR (heh) when reading this part.
also, line wrapping tweaks, split a paragraph into two, and reword a couple passages for clarity
* compact the list of git commands
* CONTRIBUTING: greatly simplify the PR instructions
plus some wording tweaks here and there
* improve instructions to use tldrl
* brace expansion is not as common in the wild
removing it keeps the examples of unix features to a manageable/readable 3
* use actual commands in the git section
* use only one-liners on the git section
* add subsection header for commit message
* slight reword of licensing note
- merge do's and don'ts, since they had mostly the same advice
- move token formatting info to the guideline section and the markdown section, as appropriate
- tweak spelling and fix a couple typos
- fix options vs. values in the formatting example, and add a token there.