summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Vandaƫle <joshua@vandaele.software>2025-02-06 15:16:23 +0100
committerJoshua Vandaƫle <joshua@vandaele.software>2025-02-06 15:16:23 +0100
commitb5978148b58143230facaafebe9417b51e07ffb2 (patch)
tree7bfa8afc433ee5fdae6316e0c9131d4ca90cfb51
parentd0b7c96fdb7ea50d55bb3cf581e5820d7b27b7e1 (diff)
Contributing.md: Improve clarity and specify clang-format version
-rw-r--r--Contributing.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/Contributing.md b/Contributing.md
index 78f9facdac..485fdd1ba7 100644
--- a/Contributing.md
+++ b/Contributing.md
@@ -35,11 +35,11 @@ Summary:
## <a name="intro-aims"></a>Aims
-This guide is for developers who wish to contribute to the Dolphin codebase. It will detail how to properly style and format code to fit this project. This guide also offers suggestions on specific functions and other varia that may be used in code.
+This guide is for developers who wish to contribute to the Dolphin codebase. It details how to properly style and format code for this project. This guide also offers suggestions on specific functions and other elements that may be used in code.
-Following this guide and formatting your code as detailed will likely get your pull request merged much faster than if you don't (assuming the written code has no mistakes in itself).
+Following this guide and formatting your code as detailed will likely get your pull request merged much faster than if you don't (assuming the code itself has no mistakes).
-This project uses clang-format (stable branch) to check for common style issues. In case of conflicts between this guide and clang-format rules, the latter should be followed instead of this guide.
+This project uses clang-format 13.0 to check for common style issues. In case of conflicts between this guide and clang-format rules, the latter should be followed instead of this guide.
## <a name="intro-formatting-issues"></a>Checking and fixing formatting issues