From 959f4cbb621868a4f0c1701f54ad2a1f45d889af Mon Sep 17 00:00:00 2001 From: George Rodrigues Date: Wed, 5 Oct 2022 13:32:07 -0300 Subject: docs: some typos (#18582) probably hacktoberism --- docs/coding_conventions_c.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/coding_conventions_c.md') 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: -- cgit v1.2.3