From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH] README.md: run codespell
Date: Wed, 27 Nov 2024 13:58:56 -0800 [thread overview]
Message-ID: <20241127215856.3375552-1-mcgrof@kernel.org> (raw)
Minor spelling fixes.
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index e610d91460fa..4d9be800c982 100644
--- a/README.md
+++ b/README.md
@@ -249,7 +249,7 @@ Below is kdevops' recommended documentation reading.
# kdevops kernel-ci support
-kdevops supports its own kernel continous integration support, so to allow
+kdevops supports its own kernel continuous integration support, so to allow
Linux developers and Linux distributions to keep track of issues present in
any of supported kdevops workflows and be able to tell when new regressions
are detected. Note though that kernel-ci for kdevops is only implemented on
@@ -348,7 +348,7 @@ Below are sections which get into technical details of how kdevops works.
* [Linux distribution support](docs/linux-distro-support.md)
* [Overriding all Ansible role options with one file](docs/ansible-override.md)
* [kdevops Vagrant support](docs/kdevops-vagrant.md)
- * [kdevops terraform suppor - cloud setup with kdevops](docs/kdevops-terraform.md)
+ * [kdevops terraform support - cloud setup with kdevops](docs/kdevops-terraform.md)
* [kdevops local Ansible roles](docs/ansible-roles.md)
* [Tutorial on building your own custom Vagrant boxes](docs/custom-vagrant-boxes.md)
--
2.45.2
reply other threads:[~2024-11-27 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241127215856.3375552-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
/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