From 95212b3f84b1d76dae0551e95bbc6a4b166eb48a 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: 640b2a85f4ca822ccd3eb7fc539457606cba9404) 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 d0026f9e3c..43c5abe20e 100644 --- a/documentation/contributor-guide/submit-changes.rst +++ b/documentation/contributor-guide/submit-changes.rst @@ -752,7 +752,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