From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: "Clark Williams" <williams@redhat.com>, "John Kacur" <jkacur@redhat.com>
Cc: "John B. Wyatt IV" <jwyatt@redhat.com>,
linux-rt-users@vger.kernel.org,
kernel-rts-sst <kernel-rts-sst@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: [PATCH] tuna: Proofreading fixes
Date: Thu, 4 Sep 2025 10:21:31 -0400 [thread overview]
Message-ID: <20250904142134.41426-1-jwyatt@redhat.com> (raw)
Fix some small proofreading errors.
Signed-off-by: John B. Wyatt IV <jwyatt@redhat.com>
Signed-off-by: John B. Wyatt IV <sageofredondo@gmail.com>
---
etc/tuna/example.conf | 2 +-
tuna/gui/profileview.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/etc/tuna/example.conf b/etc/tuna/example.conf
index 7bb293e..0d3353f 100644
--- a/etc/tuna/example.conf
+++ b/etc/tuna/example.conf
@@ -55,5 +55,5 @@ net.core = core
#special section for this file description
[fileDescription]
-text = This file contain some features for tunning kernel params.Mainly this is example file for demonstrate tuna new features. Params are set as default or most uses value
+text = This file contains some features for tuning kernel params. Mainly this is an example file for demonstrating Tuna's new features. Params are set as default or the most used value.
diff --git a/tuna/gui/profileview.py b/tuna/gui/profileview.py
index 7570bc0..e5022b8 100644
--- a/tuna/gui/profileview.py
+++ b/tuna/gui/profileview.py
@@ -104,7 +104,7 @@ class profileview:
"%s\n\n%s\n%s" % \
(_("Config file was changed!"),
_("All changes will be lost"),
- _("Realy continue?"),))
+ _("Really continue?"),))
ret = dialog.run()
dialog.destroy()
if ret == Gtk.ResponseType.NO:
--
2.51.0
next reply other threads:[~2025-09-04 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 14:21 John B. Wyatt IV [this message]
2025-09-18 18:18 ` [PATCH] tuna: Proofreading fixes John Kacur
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=20250904142134.41426-1-jwyatt@redhat.com \
--to=jwyatt@redhat.com \
--cc=jkacur@redhat.com \
--cc=kernel-rts-sst@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=sageofredondo@gmail.com \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).