vzdump: drop overly scary & outdated warning about fleecing

[pve-docs.git] / local-lvm.adoc

diff --git a/local-lvm.adoc b/local-lvm.adoc
index 2489b9d140d83b7c036ccaf4762986a6a43568d1..b6009c8c0e66ac002fb71e329aace56c229a8d00 100644 (file)
--- 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:
@@ -33,7 +33,7 @@ VG:
   swap pve  -wi-ao---- 896.00m     
 ----
 
-root:: Formatted as `ext4`, and contains the operation system.
+root:: Formatted as `ext4`, and contains the operating system.
 
 swap:: Swap partition
 
@@ -64,7 +64,9 @@ Bootloader
 
 We install two boot loaders by default. The first partition contains
 the standard GRUB boot loader. The second partition is an **E**FI **S**ystem
-**P**artition (ESP), which makes it possible to boot on EFI systems.
+**P**artition (ESP), which makes it possible to boot on EFI systems and to
+apply xref:sysadmin_firmware_persistent[persistent firmware updates] from the
+user space.
 
 
 Creating a Volume Group
@@ -120,8 +122,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>