Yocto Project Documentation
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 4/4] toaster-manual: spell the json code-block language in lower case
Date: Sun, 30 Aug 2026 22:12:55 -0400	[thread overview]
Message-ID: <20260831021255.4064163-4-twoerner@gmail.com> (raw)
In-Reply-To: <20260831021255.4064163-1-twoerner@gmail.com>

Pygments resolves either spelling, so nothing renders differently. Every
other block in the documentation uses the lower-case form.

AI-Generated: codex/claude opus 5 (xhigh)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 documentation/toaster-manual/reference.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/documentation/toaster-manual/reference.rst b/documentation/toaster-manual/reference.rst
index 3050b5d0f55c..bc065a446a1c 100644
--- a/documentation/toaster-manual/reference.rst
+++ b/documentation/toaster-manual/reference.rst
@@ -408,7 +408,7 @@ itemizes all builds in progress. This file includes the time in seconds since
 each respective build started as well as the progress of the cloning, parsing,
 and task execution. Here is sample output for a build in progress:
 
-.. code-block:: JSON
+.. code-block:: json
 
    {"count": 1,
     "building": [
@@ -442,7 +442,7 @@ Be sure to provide values for host and port. The output is a JSON file that
 itemizes all complete builds, and includes build summary information. Here
 is sample output for a completed build:
 
-.. code-block:: JSON
+.. code-block:: json
 
    {"count": 1,
     "builds": [
@@ -481,7 +481,7 @@ The output is a JSON file that itemizes the specific build and includes
 build summary information. Here is sample output for a specific
 build:
 
-.. code-block:: JSON
+.. code-block:: json
 
    {"build":
       {"distro": "poky",
-- 
2.50.0.173.g8b6f19ccfc3a



  parent reply	other threads:[~2026-08-31  2:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  2:12 [PATCH 1/4] ref-manual: drop the full stop from the QB_SMP example Trevor Woerner
2026-08-31  2:12 ` [PATCH 2/4] ref-manual: fix a typo in the QB_SMP description Trevor Woerner
2026-08-31  2:12 ` [PATCH 3/4] dev-manual: quote the values in two recipe examples Trevor Woerner
2026-08-31  2:12 ` Trevor Woerner [this message]
2026-09-07  8:30 ` [PATCH 1/4] ref-manual: drop the full stop from the QB_SMP example 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=20260831021255.4064163-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox