diff options
author | Piotr Kasprzyk <ciri@ciri.pl> | 2017-03-18 00:11:52 +0300 |
---|---|---|
committer | Peter Eckersley <pde@users.noreply.github.com> | 2017-03-18 00:11:52 +0300 |
commit | fd789b4e4b9f58970abf10fed399e4e786ba3bb4 (patch) | |
tree | d562d38dfee62decadb355e33581617c789684f8 /docs | |
parent | b23a1377e04a7f53269bb36e008a3cf495d2853f (diff) |
Fix choose, remove spaces (#4364)
Diffstat (limited to 'docs')
-rw-r--r-- | docs/using.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/using.rst b/docs/using.rst index 7c17796e7..549a3479c 100644 --- a/docs/using.rst +++ b/docs/using.rst @@ -175,15 +175,15 @@ the UI, you can use the plugin to obtain a cert by specifying to copy and paste commands into another terminal session, which may be on a different computer. -The manual plugin can use either the ``http`` or the ``dns`` challenge. You -can use the ``--preferred-challenges`` option to chose the challenge of your +The manual plugin can use either the ``http`` or the ``dns`` challenge. You +can use the ``--preferred-challenges`` option to choose the challenge of your preference. -The ``http`` challenge will ask you to place a file with a specific name and -specific content in the ``/.well-known/acme-challenge/`` directory directly -in the top-level directory (“web root”) containing the files served by your +The ``http`` challenge will ask you to place a file with a specific name and +specific content in the ``/.well-known/acme-challenge/`` directory directly +in the top-level directory (“web root”) containing the files served by your webserver. In essence it's the same as the webroot_ plugin, but not automated. -When using the ``dns`` plugin, ``certbot`` will ask you to place a TXT DNS -record with specific contents under the domain name consisting of the hostname +When using the ``dns`` plugin, ``certbot`` will ask you to place a TXT DNS +record with specific contents under the domain name consisting of the hostname for which you want a certificate issued, prepended by ``_acme-challenge``. For example, for the domain ``example.com``, a zone file entry would look like: |