diff mbox series

contributor-guide: fix type "maintainance" to "maintenance"

Message ID 3b6ae4f4-b7c8-e196-ccf2-eba99097d5af@crashcourse.ca
State Under Review
Headers show
Series contributor-guide: fix type "maintainance" to "maintenance" | expand

Commit Message

Robert P. J. Day May 19, 2026, 12:23 p.m. UTC 
Correct "maintainance" typo in recipe-style-guide.rst.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

  sorry, forgot '[PATCH]' prefix in earlier submission. *sigh*.
diff mbox series

Patch

diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
index d0cb65295..79bf7c79b 100644
--- a/documentation/contributor-guide/recipe-style-guide.rst
+++ b/documentation/contributor-guide/recipe-style-guide.rst
@@ -315,7 +315,7 @@  following status strings:
    No determination has been made yet, or patch has not yet been submitted to
    upstream.

-   Keep in mind that every patch submitted upstream reduces the maintainance
+   Keep in mind that every patch submitted upstream reduces the maintenance
    burden in OpenEmbedded and Yocto Project in the long run, so this patch
    status should only be used in exceptional cases if there are genuine
    obstacles to submitting a patch upstream; the reason for that should be
@@ -346,7 +346,7 @@  following status strings:
    The patch is not appropriate for upstream, include a brief reason on the
    same line enclosed with ``[]``. In the past, there were several different
    reasons not to submit patches upstream, but we have to consider that every
-   non-upstreamed patch means a maintainance burden for recipe maintainers.
+   non-upstreamed patch means a maintenance burden for recipe maintainers.
    Currently, the only reasons to mark patches as inappropriate for upstream
    submission are: