pbs: fix password and encryption key file location

[pve-docs.git] / certificate-management.adoc

diff --git a/certificate-management.adoc b/certificate-management.adoc
index a130550731ff801a2a0febd25994a58db81e3df5..00633a104b82c316b388f111ca693e15d0e8621d 100644 (file)
--- 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"]
 
@@ -185,7 +185,7 @@ https://github.com/acmesh-official/acme.sh/wiki/dnsapi#how-to-use-dns-api[How to
 wiki for more detailed information about getting API credentials for your
 provider.
 
-As there are so many API endpoints {pve} autogenerates the formular for the
+As there are so many API endpoints {pve} autogenerates the form for the
 credentials, but not all providers are annotated yet. For those you will see a
 bigger text area, simply copy all the credentials `KEY`=`VALUE` pairs in there.