diff --git a/CODING_STYLE.md b/CODING_STYLE.md
index ac71650..e61073f 100644
--- a/CODING_STYLE.md
+++ b/CODING_STYLE.md
@@ -11,97 +11,97 @@ The rules don't follow any particular order and don't intend to cover every sing
 1. Use 2-spaced indentation.
 
 2. This is the preferred style for statement braces (`if`, `for`, `switch`, etc.):
-   ```c
-   if (condition) {
+    ```c
+    if (condition) {
      do_x();
-   } else {
+    } else {
      do_y();
-   }
-   ```
+    }
+    ```
 
 3. Braces can be skipped when there's only one statement:
-   ```c
-   if (condition)
-     do_x();
-   ```
+    ```c
+    if (condition)
+      do_x();
+    ```
 
 4. This is also acceptable when line is not too long:
-   ```c
-   if (condition) return -1;
-   ```
+    ```c
+    if (condition) return -1;
+    ```
 
 5. Functions are a special case, with opening brace at the beginning of a new line:
-   ```c
-   int function(int x)
-   {
-     /* Body goes here */
-   }
-   ```
+    ```c
+    int function(int x)
+    {
+      /* Body goes here */
+    }
+    ```
 
 6. Put a space after these keywords: `if, switch, case, for, do, while`
 
 7. When declaring pointers, the preferred use of * is adjacent to the data name or function name and not adjacent to the type name:
-   ```c
-   char *str;
-   char *copy_str(const char *str);
-   ```
+    ```c
+    char *str;
+    char *copy_str(const char *str);
+    ```
 
 8. Avoid using typedefs as much as possible. Read rationale here: https://www.kernel.org/doc/html/v4.10/process/coding-style.html#typedefs
 
 9. Function names are `snake_case`:
-   ```c
-   int process_request(const struct *request);
-   ```
+    ```c
+    int process_request(const struct *request);
+    ```
 
 10. Variable names are `snake_case`:
-   ```c
-   size_t arr_len;
-   char *tmp, *filter_name;
-   ```
+    ```c
+    size_t arr_len;
+    char *tmp, *filter_name;
+    ```
 
 11. Struct names are `snake_case`:
-   ```c
-   struct decoding_ctx {
-     size_t processed;
-     size_t remaining;
-   };
-   ```
+    ```c
+    struct decoding_ctx {
+      size_t processed;
+      size_t remaining;
+    };
+    ```
 
 12. Enum names are `snake_case`:
-   ```c
-   enum response_error {
-     BAD_REQUEST_ERROR,
-     UNREACHABLE_ERROR
-   };
-   ```
+    ```c
+    enum response_error {
+      BAD_REQUEST_ERROR,
+      UNREACHABLE_ERROR
+    };
+    ```
 
 13. Names of macros defining constants are `CAPITALISED`:
-   ```c
-   #define MAGIC_NUMBER 42
-   ```
+    ```c
+    #define MAGIC_NUMBER 42
+    ```
 
 14. Labels in enums are `CAPITALISED`:
-   ```c
-   enum {
-     PERSIST,
-     CONTINUE,
-     ABORT
-   };
-   ```
+    ```c
+    enum {
+      PERSIST,
+      CONTINUE,
+      ABORT
+    };
+    ```
 
 15. Macros resembling functions may be named in lower case:
-   ```c
-   #define list_add(list, element)
-   ```
+    ```c
+    #define list_add(list, element)
+    ```
 
 16. The preferred style for multi-line comments is:
-   ```c
-   /*
-    * This is a multi-line comment that doesn't fit in a
-    * single line.
-    *
-    * Leave a blank line between paragraphs within the block
-    * comment.
-    */
-   ```
+    ```c
+    /*
+     * This is a multi-line comment that doesn't fit in a
+     * single line.
+     *
+     * Leave a blank line between paragraphs within the block
+     * comment.
+     */
+    ```