From c8e44dd359b62fdf8dfb547d9e2dd410f03311d7 Mon Sep 17 00:00:00 2001 From: ydnd <1843212188@qq.com> Date: Fri, 19 Jun 2026 22:11:48 +0800 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F(docs)=20fix=20typos=20in=20c?= =?UTF-8?q?ontributing=20guide?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Correct minor wording and spelling mistakes in the contribution guidelines. Signed-off-by: ydnd <1843212188@qq.com> --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 82127d6f9f..6556e7f51d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,7 +2,7 @@ Thank you for taking the time to contribute! Please follow these guidelines to ensure a smooth and productive workflow. 🚀🚀🚀 -We appreciate and value all kind of contributions (code, bug reports, design, feature requests, translations or documentation) the more diverse the Docs contributors community is, the better, because that's how [we make commons](http://wemakecommons.org/). +We appreciate and value all kinds of contributions (code, bug reports, design, feature requests, translations or documentation) the more diverse the Docs contributors community is, the better, because that's how [we make commons](http://wemakecommons.org/). ## Meet the maintainers team @@ -60,7 +60,7 @@ The project is licensed with Mozilla Public License Version 2.0 but be aware tha ### Coordination around issues -We use use EPICs to group improvements on features. (See an [example](https://github.com/suitenumerique/docs/issues/1650)) +We use EPICs to group improvements on features. (See an [example](https://github.com/suitenumerique/docs/issues/1650)) We use GitHub Projects to: * Track progress on [accessibility](https://github.com/orgs/suitenumerique/projects/19) @@ -83,8 +83,8 @@ For the CI to pass contributors are required to: * [sign their commits with your SSH or GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) with `git commit -S`. * use a special formatting for their commits (see instructions below) * check the linting: `make lint && make frontend-lint` -* Run the tests: `make test` and make sure all require test pass (we can't merge otherwise) -* add a changelog entry (not required for small changes +* Run the tests: `make test` and make sure all required tests pass (we can't merge otherwise) +* add a changelog entry (not required for small changes) ### Pull requests @@ -161,7 +161,7 @@ Please remember: LaSuite is maintained by humans for humans. Using AI to help write, review, or improve your contribution is fine. -Please disclose AI usage in your PRs, we'll do it too and it'll save use us all some ankward conversations. +Please disclose AI usage in your PRs, we'll do it too and it'll save us all some awkward conversations. The rules are simple: **you must understand and be able to explain the code that you submit.**