Skip to content

Commit 317e96a

Browse files
committed
More improvements to Getting Started.
1 parent 76e7d00 commit 317e96a

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

howitworks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ redirect_from: "/howitworks"
77
---
88

99
To enable HTTPS on your website, you need to get a certificate (a type of file)
10-
from a certificate authority. Let's Encrypt is a certificate authority. Like all
11-
certificate authorities, it verifies that you own a given domain name before issuing a
12-
certificate to you. It does so by communicating with software that uses
10+
from a Certificate Authority (CA). Let's Encrypt is a CA. In order to get a
11+
certificate for your website's domain from Let's Encrypt, you have to demonstrate
12+
control over the domain. With Let's Encrypt, you do this using software that uses
1313
the [ACME protocol](https://ietf-wg-acme.github.io/acme/), which typically runs
1414
on your web host.
1515

@@ -59,7 +59,7 @@ If your hosting provider doesn't want to integrate Let's Encrypt, but does
5959
support uploading custom certificates, you can install Certbot on your own
6060
computer and use it in [manual mode](https://certbot.eff.org/docs/using.html#manual).
6161
In manual mode, you upload a specific file to your website to prove your
62-
ownership. Certbot will then retrieve a certificate that you can upload to your
62+
control. Certbot will then retrieve a certificate that you can upload to your
6363
hosting provider. We don't recommend this option because it is time-consuming
6464
and you will need to repeat it several times per year as your certificate
6565
expires. For most people it is better to request Let's Encrypt support from your

0 commit comments

Comments
 (0)