public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 5/9] local-lvm: typo fix/better phrasing
Date: Fri, 18 Nov 2022 12:09:45 +0100	[thread overview]
Message-ID: <20221118110949.59298-5-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20221118110949.59298-1-m.heiserer@proxmox.com>

Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
 local-lvm.adoc | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/local-lvm.adoc b/local-lvm.adoc
index 6abdee8..8092bb8 100644
--- a/local-lvm.adoc
+++ b/local-lvm.adoc
@@ -7,7 +7,7 @@ endif::wiki[]
 
 Most people install {pve} directly on a local disk. The {pve}
 installation CD offers several options for local disk management, and
-the current default setup uses LVM. The installer let you select a
+the current default setup uses LVM. The installer lets you select a
 single disk for such setup, and uses that disk as physical volume for
 the **V**olume **G**roup (VG) `pve`. The following output is from a
 test installation using a small 8GB disk:
@@ -120,8 +120,7 @@ To make it always accessible add the following line in `/etc/fstab`.
 Resizing the thin pool
 ~~~~~~~~~~~~~~~~~~~~~~
 
-Resize the LV and the metadata pool can be achieved with the following
-command.
+Resize the LV and the metadata pool with the following command:
 
  # lvresize --size +<size[\M,G,T]> --poolmetadatasize +<size[\M,G]> <VG>/<LVThin_pool>
 
-- 
2.30.2





  parent reply	other threads:[~2022-11-18 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 11:09 [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 2/9] package-repos: fix typos Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 3/9] network: fix typo Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 4/9] network: fix dead link Matthias Heiserer
2022-11-18 11:09 ` Matthias Heiserer [this message]
2022-11-18 11:09 ` [pve-devel] [PATCH docs 6/9] local-zfs Remove SSD suggestion as it's outdated Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 7/9] local-zfs: rephrase ZFS RAID description Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 8/9] local-zfs: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 9/9] Update ExtJS version Matthias Heiserer
2022-11-18 12:03 ` [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Thomas Lamprecht
2022-11-18 12:04 ` [pve-devel] applied-series: " Thomas Lamprecht

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=20221118110949.59298-5-m.heiserer@proxmox.com \
    --to=m.heiserer@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