DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: distrokit@pengutronix.de
Subject: [DistroKit] [PATCH 1/3] arch: fastboot: testing: fix typos
Date: Fri, 25 Aug 2023 12:15:57 +0200	[thread overview]
Message-ID: <20230825101559.29166-1-jbe@pengutronix.de> (raw)

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
---
 doc/testing.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/testing.rst b/doc/testing.rst
index afa1be8..83bdb71 100644
--- a/doc/testing.rst
+++ b/doc/testing.rst
@@ -5,19 +5,19 @@ Sometimes a quick test should be done: a new kernel feature or a tool
 should be tested on a real target.
 
 If the target suports USB OTG (or peripheral mode) or network, 'fastboot'
-can be an easy to use solution.
+can be an easy-to-use solution.
 
 'fastboot' support
 ------------------
 
 For a fast development or testing cycle you can use 'fastboot' via
-USB or networt to transfer the required parts to the target system.
+USB or network to transfer the required parts to the target system.
 
 Here we want to run a Linux kernel and a corresponding root filesystem,
-without writing target system local memories againg and again for each
+without writing target system local memories again and again for each
 development or test cycle.
 
-In this text, we transfer the required files to the target system
+In this test, we transfer the required files to the target system
 which only needs to run a 'fastboot' capable bootloader.
 
 Since we want to use an initramfs as the kernel's root filesystem, we
@@ -76,7 +76,7 @@ And we want run the downloaded files, so we need:
 BSP
 ---
 
-Create a initramf of the root filesystem:
+Create an initramf of the root filesystem:
 
 - PTXCONF_IMAGE_ROOT_CPIO = y
 
@@ -100,7 +100,7 @@ Some BPS settings do not make sense regarding used in an initramfs instead
 of a persistent target system local memory. For development or testing some
 settings should be changed, to reduce the file sizes and boot time.
 
-The Linux kernel will be transfered separately, so it makes less sense to
+The Linux kernel will be transferred separately, so it makes less sense to
 have it in the root filesystem as well. This will reduce the size of the
 initramfs.
 
@@ -128,7 +128,7 @@ size hits some threshold. In this case, there are some additional requirements
 to the size of the file itself: its size must be a multiple of 4 kiB.
 
 Note: if this additional requirement isn't met, the error message is
-      missleading and states about an 'invalid value' after the first
+      misleading and states about an 'invalid value' after the first
       transfer.
 
 Most of the time the initramfs file hits the threshold. Thus, it must
-- 
2.30.2




             reply	other threads:[~2023-08-25 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 10:15 Juergen Borleis [this message]
2023-08-25 10:15 ` [DistroKit] [PATCH 2/3] v7a: barebox: enable loading kernel, dtb and initrd via fastboot Juergen Borleis
2023-08-25 10:48   ` Robert Schwebel
2023-08-25 10:15 ` [DistroKit] [PATCH 3/3] doc: RIoT: mention the 'fastboot' capabilities Juergen Borleis
2023-08-25 10:54   ` Robert Schwebel
2023-08-25 10:49 ` [DistroKit] [PATCH 1/3] arch: fastboot: testing: fix typos Robert Schwebel

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=20230825101559.29166-1-jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    /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