public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] local-zfs: correct language errors
Date: Tue, 13 Aug 2024 12:23:04 +0200	[thread overview]
Message-ID: <20240813102305.6-1-a.zeidler@proxmox.com> (raw)

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 local-zfs.adoc | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/local-zfs.adoc b/local-zfs.adoc
index 130f9d6..7ddf50a 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -442,7 +442,7 @@ recommend to:
 # zpool create -f -o ashift=12 <pool> <device> log <log-device>
 ----
 
-In above example a single `<device>` and a single `<log-device>` is used, but you
+In the example above, a single `<device>` and a single `<log-device>` is used, but you
 can also combine this with other RAID variants, as described in the
 xref:sysadmin_zfs_create_new_zpool_raid0[Create a new pool with RAID] section.
 
@@ -465,19 +465,19 @@ protection that you want to use for improving the overall performance of your
 pool.
 
 As the maximum size of a log device should be about half the size of the
-installed physical memory, it means that the ZIL will mostly likely only take up
+installed physical memory, it means that the ZIL will most likely only take up
 a relatively small part of the SSD, the remaining space can be used as cache.
 
 First you have to create two GPT partitions on the SSD with `parted` or `gdisk`.
 
-Then you're ready to add them to an pool:
+Then you're ready to add them to a pool:
 
 .Add both, a separate log device and a second-level cache, to an existing pool
 ----
 # zpool add -f <pool> log <device-part1> cache <device-part2>
 ----
 
-Just replay `<pool>`, `<device-part1>` and `<device-part2>` with the pool name
+Just replace `<pool>`, `<device-part1>` and `<device-part2>` with the pool name
 and the two `/dev/disk/by-id/` paths to the partitions.
 
 You can also add ZIL and cache separately.
@@ -527,8 +527,8 @@ process of the new disk has progressed.
 # proxmox-boot-tool init <new disk's ESP> [grub]
 ----
 
-NOTE: `ESP` stands for EFI System Partition, which is setup as partition #2 on
-bootable disks setup by the {pve} installer since version 5.4. For details, see
+NOTE: `ESP` stands for EFI System Partition, which is set up as partition #2 on
+bootable disks when using the {pve} installer since version 5.4. For details, see
 xref:sysboot_proxmox_boot_setup[Setting up a new partition for use as synced ESP].
 
 NOTE: Make sure to pass 'grub' as mode to `proxmox-boot-tool init` if
@@ -541,7 +541,7 @@ especially if Secure Boot is enabled!
 # grub-install <new disk>
 ----
 NOTE: Plain GRUB is only used on systems installed with {pve} 6.3 or earlier,
-which have not been manually migrated to using `proxmox-boot-tool` yet.
+which have not been manually migrated to use `proxmox-boot-tool` yet.
 
 
 Configure E-Mail Notification
-- 
2.39.2



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2024-08-13 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 10:23 Alexander Zeidler [this message]
2024-08-13 13:58 ` [pve-devel] applied: " Fiona Ebner

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=20240813102305.6-1-a.zeidler@proxmox.com \
    --to=a.zeidler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal