summaryrefslogtreecommitdiff
path: root/pages/docs
diff options
context:
space:
mode:
authorkwadronaut <kwadronaut@leap.se>2016-04-05 21:11:43 +0200
committerkwadronaut <kwadronaut@leap.se>2016-04-05 21:11:43 +0200
commit1e8143db7372b14bafbeaababe80fb50aa3409b0 (patch)
tree28da2edb243dda6c0b15ddee5ddf47c4f9daba46 /pages/docs
parent155d92f9173dc1d1008009b4b605df968e2e9550 (diff)
update LetsEncrypt doc in keys-certs
Diffstat (limited to 'pages/docs')
-rw-r--r--pages/docs/platform/guide/keys-and-certificates.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/pages/docs/platform/guide/keys-and-certificates.md b/pages/docs/platform/guide/keys-and-certificates.md
index 7449905..a6862a6 100644
--- a/pages/docs/platform/guide/keys-and-certificates.md
+++ b/pages/docs/platform/guide/keys-and-certificates.md
@@ -87,7 +87,7 @@ All keys matching 'userx/*_ssh.pub' will be usable.
Removing sysadmin access
--------------------------------
-Suppose you want to remove `userx` from having any further ssh access to the servers. Do this:
+Suppose you want to remove `userx` from having any further SSH access to the servers. Do this:
rm -r users/userx
leap deploy
@@ -210,11 +210,11 @@ To see details about the keys and certs you can use `leap inspect` like so:
$ leap inspect files/ca/ca.crt
-Let's encrypt certificate
+Let's Encrypt certificate
=========================
-LEAP plans to integrate [Let's encrypt](https://letsencrypt.org/) support to it will be even easier to recieve SSL certificates that are accepted by all browsers.
-Until we achieved this, here's a guide how to do this manually.
+LEAP plans to integrate [Let's Encrypt](https://letsencrypt.org/) support, so it will be even easier to receive X.509 certificates that are accepted by all browsers.
+Until we achieve this, here's a guide how to do this manually.
Install the official acme client
--------------------------------
@@ -238,7 +238,7 @@ Fetch the certs
This will put the certs and keys into `/etc/letsencrypt/live/DOMAIN/`.
-Now, go to your workstation's provider configuration directory and copy the newly create files from the server to your local config. You will override existing files so please make a backup before proceeding, or use a version control system to track changes.
+Now, go to your workstation's provider configuration directory and copy the newly created files from the server to your local config. You will override existing files so please make a backup before proceeding, or use a version control system to track changes.
workstation$ cd PATH_TO_PROVIDER_CONFIG