Minor grammar and filename fixes in docs (#7559)
Grammar in coding_conventions_c.md and coding_conventions_python.md `rule.mk` to `rules.mk` in feature_haptic_feedback.md and feature_rgb_matrix.md
This commit is contained in:
		| @@ -14,7 +14,7 @@ Most of our style is pretty easy to pick up on, but right now it's not entirely | ||||
|   * Think of them as a story describing the feature | ||||
|   * Use them liberally to explain why particular decisions were made. | ||||
|   * Do not write obvious comments | ||||
|   * If you not sure if a comment is obvious, go ahead and include it. | ||||
|   * If you're not sure if a comment is obvious, go ahead and include it. | ||||
| * In general we don't wrap lines, they can be as long as needed. If you do choose to wrap lines please do not wrap any wider than 76 columns. | ||||
| * We use `#pragma once` at the start of header files rather than old-style include guards (`#ifndef THIS_FILE_H`, `#define THIS_FILE_H`, ..., `#endif`) | ||||
| * We accept both forms of preprocessor if's: `#ifdef DEFINED` and `#if defined(DEFINED)` | ||||
|   | ||||
		Reference in New Issue
	
	Block a user