From effcf08ef076af47622941965f144b62b0ff8fe1 Mon Sep 17 00:00:00 2001 From: Yanis BINARD Date: Wed, 1 Apr 2026 17:14:42 +0200 Subject: [PATCH] contributor-guide/submit-changes.rst: Added missing word (From yocto-docs rev: 5b4cc93a2f19019871f66e192f67b96fa3861620) Signed-off-by: Yanis BINARD Signed-off-by: Antonin Godard (cherry picked from commit 4656516415d8ff6b1bc25ef64acabee01dd5a78e) Signed-off-by: Antonin Godard Signed-off-by: Paul Barker --- documentation/contributor-guide/submit-changes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst index 24a3fc751a..230d528e04 100644 --- a/documentation/contributor-guide/submit-changes.rst +++ b/documentation/contributor-guide/submit-changes.rst @@ -711,7 +711,7 @@ Taking Patch Review into Account You may get feedback on your submitted patches from other community members or from the automated patchtest service. If issues are identified in your patches then it is usually necessary to address these before the patches are -accepted into the project. In this case you should your commits according +accepted into the project. In this case you should revise your commits according to the feedback and submit an updated version to the relevant mailing list. In any case, never fix reported issues by fixing them in new commits