From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v3 4/5] installation: zfs-options: improve & align wording with pmg-docs
Date: Thu, 21 Mar 2024 16:29:30 +0100 [thread overview]
Message-ID: <20240321152941.1971509-5-c.heiss@proxmox.com> (raw)
In-Reply-To: <20240321152941.1971509-1-c.heiss@proxmox.com>
These changes are the result of basically "diffing" both documentations,
choosing the better prased/sounding sections. Some wording were also
slightly changed as necessary to further improve them.
The equivalent changes will be done for pmg-docs too, to ensure they are
really the same in the end.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* none
Changes v2 -> v3:
* none
pve-installation.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index eaa800f..f4a898b 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -294,10 +294,10 @@ lvmthin snapshots).
[[advanced_zfs_options]]
Advanced ZFS Configuration Options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The installer creates the ZFS pool `rpool`. No swap space is created but you can
-reserve some unpartitioned space on the install disks for swap. You can also
-create a swap zvol after the installation, although this can lead to problems.
-(see <<zfs_swap,ZFS swap notes>>).
+The installer creates the ZFS pool `rpool`, if ZFS is used. No swap space is
+created but you can reserve some unpartitioned space on the install disks for
+swap. You can also create a swap zvol after the installation, although this can
+lead to problems (see xref:zfs_swap[ZFS swap notes]).
`ashift`::
--
2.43.1
next prev parent reply other threads:[~2024-03-21 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:29 [pve-devel] [PATCH docs v3 0/5] improve & unify installation(-related) documentation Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 1/5] package-repos: improve wording partly based on pmg-docs Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 2/5] installation: iso: improve & align wording with pmg-docs Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 3/5] installation: lvm-options: " Christoph Heiss
2024-03-21 15:29 ` Christoph Heiss [this message]
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 5/5] installation: iso: reflow location and password dialog screenshots Christoph Heiss
2024-03-22 10:34 ` [pve-devel] applied-series: [PATCH docs v3 0/5] improve & unify installation(-related) documentation 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=20240321152941.1971509-5-c.heiss@proxmox.com \
--to=c.heiss@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