public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: [kirkstone][PATCH 5/8] dev-manual: packages: fix capitalization
Date: Thu, 14 Mar 2024 10:13:55 +0100	[thread overview]
Message-ID: <20240314091358.84025-6-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240314091358.84025-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

Using "PR service" instead of "PR Service", like in the other
two instances in this document.

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
---
 documentation/dev-manual/packages.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/dev-manual/packages.rst b/documentation/dev-manual/packages.rst
index a6e6af0de7..e5028fffdc 100644
--- a/documentation/dev-manual/packages.rst
+++ b/documentation/dev-manual/packages.rst
@@ -206,7 +206,7 @@ history, see the
    part of the shared state (sstate) packages. If you maintain an sstate
    feed, it's expected that either all your building systems that
    contribute to the sstate feed use a shared PR service, or you do not
-   run a PR Service on any of your building systems.
+   run a PR service on any of your building systems.
 
    That's because if you had multiple machines sharing a PR service but
    not their sstate feed, you could end up with "diverging" hashes for
-- 
2.34.1



  parent reply	other threads:[~2024-03-14  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  9:13 [kirkstone][PATCH 0/8] documentation backports michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 1/8] ref-manual: tasks: do_cleanall: recommend using '-f' instead michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 2/8] ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a shared sstate michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 3/8] ref-manual: variables: correct sdk installation default path michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 4/8] ref-manual: variables: adding multiple groups in GROUPADD_PARAM michael.opdenacker
2024-03-14  9:13 ` michael.opdenacker [this message]
2024-03-14  9:13 ` [kirkstone][PATCH 6/8] manuals: replace hyphens with em dashes michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 7/8] contributor-guide: add notes for tests michael.opdenacker
2024-03-14  9:13 ` [kirkstone][PATCH 8/8] manuals: document VIRTUAL-RUNTIME variables michael.opdenacker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240314091358.84025-6-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox