From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-docs v2] fix some typos
Date: Thu, 14 Nov 2024 11:03:36 +0100 [thread overview]
Message-ID: <20241114100336.101411-1-m.sandoval@proxmox.com> (raw)
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
Differences from v1:
- Remove fixes on automatically generated documentation (pmg.conf.5-opts.adoc).
pmgconfig.adoc | 2 +-
system-booting.adoc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/pmgconfig.adoc b/pmgconfig.adoc
index a9377c5..0342b97 100644
--- a/pmgconfig.adoc
+++ b/pmgconfig.adoc
@@ -1101,7 +1101,7 @@ WebAuthn Configuration
//[thumbnail="screenshot/gui-datacenter-webauthn-edit.png"]//TODO
-To allow users to use 'WebAuthn' authentication, it is necessaary to use a valid
+To allow users to use 'WebAuthn' authentication, it is necessary to use a valid
domain with a valid SSL certificate, otherwise some browsers may warn or refuse
to authenticate altogether.
diff --git a/system-booting.adoc b/system-booting.adoc
index af5b767..e8ac76e 100644
--- a/system-booting.adoc
+++ b/system-booting.adoc
@@ -356,7 +356,7 @@ To remove any pinned version configuration use the `unpin` subcommand:
While `unpin` has a `--next-boot` option as well, it is used to clear a pinned
version set with `--next-boot`. As that happens already automatically on boot,
-invonking it manually is of little use.
+invoking it manually is of little use.
After setting, or clearing pinned versions you also need to synchronize the
content and configuration on the ESPs by running the `refresh` subcommand.
--
2.39.5
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
reply other threads:[~2024-11-14 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241114100336.101411-1-m.sandoval@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pmg-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