From 49efc489fc16e94b9ccbe2f8c5b9d878dd106fe7 Mon Sep 17 00:00:00 2001 From: Peter Eckersley Date: Tue, 1 Dec 2015 17:49:49 -0800 Subject: [PATCH] fixes --- README.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.rst b/README.rst index b124de7f8..be5f04671 100644 --- a/README.rst +++ b/README.rst @@ -50,10 +50,10 @@ In many cases, you can just run ``letsencrypt-auto`` or ``letsencrypt``, and the client will guide you through the process of obtaining and installing certs interactively. -You can also tell it exactly what you want it to do. For instance, if you -want to obtain a cert for ``thing.com``, ``www.thing.com``, and -``otherthing.net``, using the Apache plugin to both obtain and install the -certs, you could do this:: +You can also tell it exactly what you want it to do from the command line. +For instance, if you want to obtain a cert for ``thing.com``, +``www.thing.com``, and ``otherthing.net``, using the Apache plugin to both +obtain and install the certs, you could do this:: ./letsencrypt-auto --apache -d thing.com -d www.thing.com -d otherthing.net @@ -62,7 +62,7 @@ email and agreement to the Let's Encrypt Subscriber Agreement; you can automate those with ``--email`` and ``--agree-tos``) If you want to use a webserver that doesn't have full plugin support yet, you -can still use "standlone" or "webroot" plugins to obtain a certificate:: +can still use "standalone" or "webroot" plugins to obtain a certificate:: ./letsencrypt-auto certonly --standalone --email admin@thing.com -d thing.com -d www.thing.com -d otherthing.net