All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 1/2] sphinx-lint: superfluous backtick in front of role
Date: Fri, 23 May 2025 21:49:01 -0400	[thread overview]
Message-ID: <20250524014902.35467-1-twoerner@gmail.com> (raw)

Fix all instances of backtick-before-role as reported by 'make sphinx-lint'.

Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 documentation/dev-manual/sbom.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/dev-manual/sbom.rst b/documentation/dev-manual/sbom.rst
index eba07b783272..e6806ce92997 100644
--- a/documentation/dev-manual/sbom.rst
+++ b/documentation/dev-manual/sbom.rst
@@ -25,14 +25,14 @@ users can read in standardized format.
 assessments, as all the components used in the Software Supply Chain are listed.
 
 The OpenEmbedded build system doesn't generate such information by default,
-though the `:term:`Poky` reference distribution has it enabled out of the box.
+though the :term:`Poky` reference distribution has it enabled out of the box.
 
 To enable it, inherit the :ref:`ref-classes-create-spdx` class from a
 configuration file::
 
    INHERIT += "create-spdx"
 
-In the `:term:`Poky` reference distribution, :term:`SPDX` generation does
+In the :term:`Poky` reference distribution, :term:`SPDX` generation does
 consume some build time resources and thus if needed it can be disabled from a
 :term:`configuration file`::
 
-- 
2.44.0.501.g19981daefd7c



             reply	other threads:[~2025-05-24  1:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-24  1:49 Trevor Woerner [this message]
2025-05-24  1:49 ` [PATCH 2/2] sphinx-lint: unbalanced inline literal markup Trevor Woerner
2025-05-26  7:21   ` [docs] " Antonin Godard
2025-05-26  8:04 ` [docs] [PATCH 1/2] sphinx-lint: superfluous backtick in front of role Quentin Schulz
2025-05-27  6:33 ` Antonin Godard

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=20250524014902.35467-1-twoerner@gmail.com \
    --to=twoerner@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.