From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@pve.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/3] Fix typos and wording
Date: Wed, 15 Jul 2020 16:26:06 +0200 [thread overview]
Message-ID: <20200715142606.25492-1-d.whyte@proxmox.com> (raw)
Update some lines to fix spelling and grammatical errors
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
certificate-management.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/certificate-management.adoc b/certificate-management.adoc
index ce9081d..00633a1 100644
--- a/certificate-management.adoc
+++ b/certificate-management.adoc
@@ -104,12 +104,12 @@ the {pve} cluster under your operation, are the real owner of a domain. This is
the basis building block for automatic certificate management.
The ACME protocol specifies different types of challenges, for example the
-`http-01` where a webserver provides a file with a certain value to proof that
+`http-01` where a webserver provides a file with a certain value to prove that
it controls a domain. Sometimes this isn't possible, either because of
technical limitations or if the address a domain points to is not reachable
-from the public internet. For such cases one could use the `dns-01` challenge.
-That challenge provides also a certain value, but not over a text file, but
-through a DNS record on the authority name server of the domain.
+from the public internet. For such cases, one could use the `dns-01` challenge.
+This challenge also provides a certain value, but through a DNS record on the
+authority name server of the domain, rather than over a text file.
[thumbnail="screenshot/gui-datacenter-acme-overview.png"]
--
2.20.1
next reply other threads:[~2020-07-15 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 14:26 Dylan Whyte [this message]
2020-07-15 15:16 ` Oguz Bektas
2020-07-15 16:46 ` Thomas Lamprecht
2020-07-15 16:48 ` [pve-devel] applied: " 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=20200715142606.25492-1-d.whyte@proxmox.com \
--to=d.whyte@proxmox.com \
--cc=pve-devel@pve.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