From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs; pmg-docs 0/6] Fix consistency of some words
Date: Mon, 3 Jul 2023 14:04:30 +0200 [thread overview]
Message-ID: <20230703120436.74646-1-n.ullreich@proxmox.com> (raw)
In the docs for pve, pmg, and pbs, the consistency and grammatical
correctness of some common words was not always good.
I fixed the words:
* USB flash drive
* command line/command-line/commandline
* motherboard/mainboard/main board
* passhrough/pass-through
Really, these are just some quick ones I found that (imo) were easy and
necessary to fix, and, if possible, this should be automated somehow.
Dietmar and I talked about this off-list and brainstormed some ideas,
but nothing concrete so far.
I also added some tables in our internal writing style guide, perhaps
this should be made public? For those, that are interested in writing
docs for pve/pbs/pmg?
----
changes from v1:
* the patches for proxmox-backup/docs have been applied
* fixed spelling mistakes in the commit messages
Noel Ullreich (4):
Consistency of passthrough/pass-through
Consistency: change mainboard to motherboard
Consistency of USB flash drive spelling
Fix spelling of command line/command-line
certificate-management.adoc | 2 +-
ha-manager.adoc | 10 +++++-----
index.adoc | 2 +-
pct.adoc | 10 +++++-----
pve-admin-guide.adoc | 4 ++--
pve-faq.adoc | 2 +-
pve-firewall.adoc | 2 +-
pve-installation-media.adoc | 2 +-
pve-intro.adoc | 6 +++---
pve-storage-lvmthin.adoc | 2 +-
pve-storage-pbs.adoc | 2 +-
pve-system-requirements.adoc | 2 +-
pveceph.adoc | 6 +++---
pvecm.adoc | 4 ++--
pvesm.adoc | 4 ++--
pvesr.adoc | 6 +++---
pveum.adoc | 10 +++++-----
qm-pci-passthrough.adoc | 2 +-
qm.adoc | 10 +++++-----
qm.conf.5-opts.adoc | 10 +++++-----
vzdump.adoc | 2 +-
21 files changed, 50 insertions(+), 50 deletions(-)
Noel Ullreich (2):
consistenct of USB flash drive spelling
Fixed spelling of command line/command-line
pmg-admin-guide.adoc | 4 ++--
pmg-administration.adoc | 2 +-
pmg-installation-media.adoc | 2 +-
pmg-intro.adoc | 4 ++--
pmg-ssl-certificate.adoc | 6 +++---
pmgbackup.adoc | 4 ++--
pmgcm.adoc | 6 +++---
pmgconfig.adoc | 4 ++--
pmgperf.adoc | 2 +-
9 files changed, 17 insertions(+), 17 deletions(-)
--
2.39.2
next reply other threads:[~2023-07-03 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:04 Noel Ullreich [this message]
2023-07-03 12:04 ` [pve-devel] [PATCH pve-docs v2 1/4] Consistency of passthrough/pass-through Noel Ullreich
2023-07-03 12:04 ` [pve-devel] [PATCH pve-docs v2 2/4] Consistency: change mainboard to motherboard Noel Ullreich
2023-07-03 12:04 ` [pve-devel] [PATCH pve-docs v2 3/4] Consistency of USB flash drive spelling Noel Ullreich
2023-07-03 12:04 ` [pve-devel] [PATCH pve-docs v2 4/4] Fix spelling of command line/command-line Noel Ullreich
2023-07-03 12:04 ` [pve-devel] [PATCH pmg-docs v2 1/2] Consistency of USB flash drive spelling Noel Ullreich
2023-07-03 12:04 ` [pve-devel] [PATCH pmg-docs v2 2/2] Fix spelling of command line/command-line Noel Ullreich
2023-11-17 9:58 ` [pve-devel] applied: [PATCH pve-docs; pmg-docs 0/6] Fix consistency of some words Thomas Lamprecht
2024-01-22 17:56 ` Stoiko Ivanov
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=20230703120436.74646-1-n.ullreich@proxmox.com \
--to=n.ullreich@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