From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 4/4] docs: various small grammar fixes
Date: Sat, 11 Apr 2026 20:50:36 +0800 [thread overview]
Message-ID: <20260411125036.778122-5-k.chai@proxmox.com> (raw)
In-Reply-To: <20260411125036.778122-1-k.chai@proxmox.com>
Small grammar fixes spotted during a proofreading pass of the
Ceph-related chapters:
* hyper-converged-infrastructure: drop stray article in "a both
self-healing..." and split "Checkout" into "Check out".
* pve-package-repos: "an selected update" -> "a selected update".
* pve-storage-rbd: "is recommend" -> "is recommended".
Signed-off-by: Kefu Chai <k.chai@proxmox.com>
---
hyper-converged-infrastructure.adoc | 4 ++--
pve-package-repos.adoc | 2 +-
pve-storage-rbd.adoc | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/hyper-converged-infrastructure.adoc b/hyper-converged-infrastructure.adoc
index 4616392..cc6199c 100644
--- a/hyper-converged-infrastructure.adoc
+++ b/hyper-converged-infrastructure.adoc
@@ -48,8 +48,8 @@ Hyper-Converged Infrastructure: Storage
infrastructure. You can, for example, deploy and manage the following two
storage technologies by using the web interface only:
-- *Ceph*: a both self-healing and self-managing shared, reliable and highly
- scalable storage system. Checkout
+- *Ceph*: a self-healing and self-managing shared, reliable and highly
+ scalable storage system. Check out
xref:chapter_pveceph[how to manage Ceph services on {pve} nodes]
- *ZFS*: a combined file system and logical volume manager with extensive
diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc
index a2882a8..2091ff6 100644
--- a/pve-package-repos.adoc
+++ b/pve-package-repos.adoc
@@ -10,7 +10,7 @@ package management tool like any other Debian-based system.
{pve} automatically checks for package updates on a daily basis. The `root@pam`
user is notified via email about available updates. From the GUI, the
-'Changelog' button can be used to see more details about an selected update.
+'Changelog' button can be used to see more details about a selected update.
Repositories in {pve}
~~~~~~~~~~~~~~~~~~~~~
diff --git a/pve-storage-rbd.adoc b/pve-storage-rbd.adoc
index 5fe558a..9a52974 100644
--- a/pve-storage-rbd.adoc
+++ b/pve-storage-rbd.adoc
@@ -102,7 +102,7 @@ The keyring will be stored at
# /etc/pve/priv/ceph/<STORAGE_ID>.keyring
----
-TIP: Creating a keyring with only the needed capabilities is recommend when
+TIP: Creating a keyring with only the needed capabilities is recommended when
connecting to an external cluster. For further information on Ceph user
management, see the Ceph docs.footnoteref:[cephusermgmt,{cephdocs-url}/rados/operations/user-management/[Ceph User Management]]
--
2.47.3
prev parent reply other threads:[~2026-04-11 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 12:50 [PATCH docs 0/4] ceph: audit of Ceph-related chapters Kefu Chai
2026-04-11 12:50 ` [PATCH docs 1/4] pveceph: fix Ceph Manager abbreviation Kefu Chai
2026-04-11 12:50 ` [PATCH docs 2/4] pve-storage-cephfs: describe CephFS, not RBD, in external cluster setup Kefu Chai
2026-04-11 12:50 ` [PATCH docs 3/4] pveceph: various small language fixes Kefu Chai
2026-04-11 12:50 ` Kefu Chai [this message]
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=20260411125036.778122-5-k.chai@proxmox.com \
--to=k.chai@proxmox.com \
--cc=pve-devel@lists.proxmox.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