Browse Source

Fix a few wording issues in the PR template (reverse changes accidentally squashed in #285)

Chia-Che Tsai 5 years ago
parent
commit
478130abe3
1 changed files with 3 additions and 3 deletions
  1. 3 3
      .github/PULL_REQUEST_TEMPLATE.md

+ 3 - 3
.github/PULL_REQUEST_TEMPLATE.md

@@ -20,10 +20,10 @@ Please fill in the following form before submitting this PR:
 
 Please follow the [coding style guidelines](CODESTYLE.md). Do not submit PRs which violate these rules.
 - [ ] Comments and commit messages: no spelling or grammatical errors
-- [ ] 4 spaces per indention level, at most 100 chars per line
+- [ ] 4 spaces per indentation level, at most 100 chars per line
 - [ ] Asterisks (`*`) next to types: `int* pointer;` (one pointer each line)
-- [ ] Braces (`{`) begin in the same line as function names, if-else, while, switch, union, and struct keywords.
-- [ ] Naming: Macros - `NAMED_THIS_WAY`; global variables - `g_named_this_way`; others - `named_this_way`.
+- [ ] Braces (`{`) begin in the same line as function names, `if`, `else`, `while`, `do`, `for`, `switch`, `union`, and `struct` keywords.
+- [ ] Naming: Macros, constants - `NAMED_THIS_WAY`; global variables - `g_named_this_way`; others - `named_this_way`.
 - Other styling issues may be pointed out by reviewers.