From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 3/9] local-btrfs: unify casing for btrfs
Date: Mon, 4 Mar 2024 14:22:10 +0100 [thread overview]
Message-ID: <20240304132221.901327-4-c.heiss@proxmox.com> (raw)
In-Reply-To: <20240304132221.901327-1-c.heiss@proxmox.com>
It's mostly spelled BTRFS anyway in our documentation (and also the
official casing AFAICS), so align a few instances where it spelled
lowercase.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
local-btrfs.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/local-btrfs.adoc b/local-btrfs.adoc
index b04d0a3..3512131 100644
--- a/local-btrfs.adoc
+++ b/local-btrfs.adoc
@@ -69,10 +69,10 @@ btrfs: local-btrfs
content iso,vztmpl,backup,images,rootdir
----
-This explicitly disables the default `local` storage in favor of a btrfs
+This explicitly disables the default `local` storage in favor of a BTRFS
specific storage entry on the additional subvolume.
-The `btrfs` command is used to configure and manage the btrfs file system,
+The `btrfs` command is used to configure and manage the BTRFS file system,
After the installation, the following command lists all additional subvolumes:
----
@@ -156,7 +156,7 @@ pvesm add btrfs my-storage --path /my-storage
Creating a subvolume
^^^^^^^^^^^^^^^^^^^^
-Creating a subvolume links it to a path in the btrfs file system, where it will
+Creating a subvolume links it to a path in the BTRFS file system, where it will
appear as a regular directory.
----
@@ -218,7 +218,7 @@ This change will take effect after rebooting.
Checking Space Usage
^^^^^^^^^^^^^^^^^^^^
-The classic `df` tool may output confusing values for some btrfs setups.
+The classic `df` tool may output confusing values for some BTRFS setups.
For a better estimate use the `btrfs filesystem usage /PATH` command, for example:
----
--
2.43.0
next prev parent reply other threads:[~2024-03-04 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:22 [pve-devel] [PATCH docs 0/9] improve & unify installation(-related) documentation Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 1/9] gitignore: add package build outputs Christoph Heiss
2024-03-06 17:16 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 2/9] asciidoc: introduce `pricing-url` variable, much like pmg-docs Christoph Heiss
2024-03-06 17:16 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` Christoph Heiss [this message]
2024-03-06 17:19 ` [pve-devel] applied: [PATCH docs 3/9] local-btrfs: unify casing for btrfs Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 4/9] getting-help: forum: align wording with pmg-docs Christoph Heiss
2024-03-06 17:19 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 5/9] package-repos: " Christoph Heiss
2024-03-05 8:28 ` Gabriel Goller
2024-03-05 12:00 ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 6/9] installation: iso: improve & " Christoph Heiss
2024-03-05 8:38 ` Gabriel Goller
2024-03-05 12:05 ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 7/9] installation: lvm-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 8/9] installation: zfs-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 9/9] installation: iso: reflow location and password dialog screenshots Christoph Heiss
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=20240304132221.901327-4-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