diff options
| author | George Rodrigues <georgerodrigues@live.com.au> | 2022-10-05 13:32:07 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-05 17:32:07 +0100 |
| commit | 959f4cbb621868a4f0c1701f54ad2a1f45d889af (patch) | |
| tree | 96b126c802cacb3645ed9a0bfda3a13ae5c915dd /docs/coding_conventions_c.md | |
| parent | 5f671de13a01c88ceb86874dba91e4e66c4a3d51 (diff) | |
docs: some typos (#18582)
probably hacktoberism
Diffstat (limited to 'docs/coding_conventions_c.md')
| -rw-r--r-- | docs/coding_conventions_c.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/coding_conventions_c.md b/docs/coding_conventions_c.md index c4bace66cc..3f44da713d 100644 --- a/docs/coding_conventions_c.md +++ b/docs/coding_conventions_c.md @@ -24,7 +24,7 @@ Most of our style is pretty easy to pick up on, but right now it's not entirely * Readability is more important than consistency. * Follow the file's existing style. If the file is mixed, follow the style that makes sense for the section you are modifying. * When indenting, keep the hash at the start of the line and add whitespace between `#` and `if`, starting with 4 spaces after the `#`. - * You can follow the indention level of the surrounding C code, or preprocessor directives can have their own indentation levels. Choose the style that best communicates the intent of your code. + * You can follow the indentation level of the surrounding C code, or preprocessor directives can have their own indentation levels. Choose the style that best communicates the intent of your code. Here is an example for easy reference: |