various minor cleanups

diff --git a/local-zfs.adoc b/local-zfs.adoc
index fab009336b9b1bfb9667564505b0c88e07288456..370bbc5c5327fe367b0f389457bc60d24948de37 100644 (file)
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -158,7 +158,7 @@ GRUB boot loader there. If you use a redundant RAID setup, it installs
 the boot loader on all disk required for booting. So you can boot
 even if some disks fail.
 
-NOTE: It is not possible to use ZFS as root partition with UEFI
+NOTE: It is not possible to use ZFS as root file system with UEFI
 boot.
 
 
@@ -242,7 +242,7 @@ As `<device>` it is possible to use more devices, like it's shown in
 If you have an pool without cache and log. First partition the SSD in
 2 partition with `parted` or `gdisk`
 
-IMPORTANT: Always use GPT partition tables (gdisk or parted).
+IMPORTANT: Always use GPT partition tables.
 
 The maximum size of a log device should be about half the size of
 physical memory, so this is usually quite small. The rest of the SSD

diff --git a/pve-firewall.adoc b/pve-firewall.adoc
index 5c8587748a06b9c3a54f850042a5919a77127320..19d9766e8a8e0cf918e79e7397553c0789f26176 100644 (file)
--- a/pve-firewall.adoc
+++ b/pve-firewall.adoc
@@ -67,8 +67,8 @@ file system. So those files are automatically distributed to all
 cluster nodes, and the `pve-firewall` service updates the underlying
 `iptables` rules automatically on changes.
 
-You can configure anything using the GUI (i.e. Datacenter -> Firewall,
-or on a Node -> Firewall), or you can edit the configuration files
+You can configure anything using the GUI (i.e. *Datacenter* -> *Firewall*,
+or on a *Node* -> *Firewall*), or you can edit the configuration files
 directly using your preferred editor.
 
 Firewall configuration files contains sections of key-value
@@ -362,7 +362,7 @@ with a source IP not matching its interface's corresponding ipfilter set will
 be dropped.
 
 For containers with configured IP addresses these sets, if they exist (or are
-activated via the general `IP Filter` option in the VM's firewall's 'options'
+activated via the general `IP Filter` option in the VM's firewall's *options*
 tab), implicitly contain the associated IP addresses.
 
 For both virtual machines and containers they also implicitly contain the

diff --git a/pvecm.adoc b/pvecm.adoc
index d31e5bf722c873ce7a854f2fa2c1fb20406b909a..84a52c58ad6fbef5652e09370a042f61c4f4d0b1 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -31,8 +31,8 @@ communication, and such clusters can consist of up to 32 physical nodes
 
 `pvecm` can be used to create a new cluster, join nodes to a cluster,
 leave the cluster, get status information and do various other cluster
-related tasks. The Proxmox Cluster file system (pmxcfs) is used to
-transparently distribute the cluster configuration to all cluster
+related tasks. The **P**rox**m**o**x** **C**luster **F**ile **S**ystem (``pmxcfs'')
+is used to transparently distribute the cluster configuration to all cluster
 nodes.
 
 Grouping nodes into a cluster has the following advantages: