diff options
| author | Nathan Scott <nathans@redhat.com> | 2020-12-01 14:15:16 +1100 |
|---|---|---|
| committer | Nathan Scott <nathans@redhat.com> | 2020-12-01 14:15:16 +1100 |
| commit | 65866c69d6e60f51ed3ae657d21d799169886d47 (patch) | |
| tree | c4ae41bfe6cc7513c2217fffb81730cbccaec207 /docs | |
| parent | f59af39684cbf058dde8bf369978378f81e2222e (diff) | |
Fix a little typo (spelling) in the styleguide
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/styleguide.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/styleguide.md b/docs/styleguide.md index 22c5157f..a0856c46 100644 --- a/docs/styleguide.md +++ b/docs/styleguide.md @@ -146,7 +146,7 @@ if (answer) else if (again) continue; else - goto bowl_of_petunias; + break; ``` When the statements that form control flow constructs are complex (e.g. more than just a simple assignment or jump) or need explanatory comments you should use braces. @@ -171,7 +171,7 @@ Try to separate such changes into a single, clean-up only commit to reduce noise When writing your code consistency with the surrounding codebase is favoured. -Don't shy away from leaving (sinlge) blank lines to separate different groups of related statements. +Don't shy away from leaving (single) blank lines to separate different groups of related statements. They can be a great asset to structure the flow of a method. ```c |