permacomputing

commit 107fe4ea20f261f93d70b6d6cb413edb6940a21f
parent cd1dd553f56c8388a3312c008cfc9c6bc37502ba
Author: decentral1se <decentral1se@web>
Date:   Sun, 29 Sep 2024 09:09:48 +0200

typo, wording

Diffstat:
M
eik.mdwn
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -14,7 +14,7 @@ However when authentication is required we force `https` like this:
         return 301 https://$http_host$request_uri;
     }
 
-We use `acme.sh` for handling certs, however expanding certs with new domain is still not supported. The workaround is to recreate a whole new cert with all the domains. For instance, as root:
+We use `acme.sh` for handling certs, however expanding certs with a new domain is still not supported. The workaround is to recreate a whole new cert with all the domains. For instance, as root:
 
     acme.sh --issue --nginx \
      -d eik.permacomputing.net \
@@ -33,7 +33,7 @@ acme.sh --install-cert \
     --fullchain-file /etc/nginx/certs/cert.pem \
     --reloadcmd "systemctl force-reload nginx"
 
-Our `acme.sh` makes use of letsencrypt CA servers, as the default one from ZeroSSL keeps on being fussy. The setting was changes like this:
+Our `acme.sh` makes use of letsencrypt CA servers, as the default one from ZeroSSL keeps on being fussy. The setting was changed like this:
 
     acme.sh --set-default-ca --server letsencrypt