changed wiki refs, added some words

docs/ciphers.rst

@@ -131,7 +131,7 @@ The Let's Encrypt project may deviate from the Mozilla recommendations
 in the future if good cause is shown and we believe our users'
 priorities would be well-served by doing so. In general, please address
 relevant proposals for changing priorities to the Mozilla security
-team first, before asking the Let's Encrypt project to change
+team first, before asking the Let's Encrypt project or EFF to change
 Certbot's priorities. The Mozilla security team is likely to have more
 resources and expertise to bring to bear on evaluating reasons why its
 recommendations should be updated.
@@ -153,7 +153,7 @@ recommendations with sources of expert guidance on ciphersuites and other
 cryptographic parameters. We're grateful to everyone who contributed
 suggestions. The recommendations we received are available at
 
-https://github.com/letsencrypt/letsencrypt/wiki/Ciphersuite-guidance
+https://github.com/certbot/certbot/wiki/Ciphersuite-guidance
 
 Certbot users are welcome to review these authorities to
 better inform their own cryptographic parameter choices. We also
@@ -196,7 +196,7 @@ TODO
 The status of this feature is tracked as part of issue #1123 in our
 bug tracker.
 
-https://github.com/letsencrypt/letsencrypt/issues/1123
+https://github.com/certbot/certbot/issues/1123
 
 Prior to implementation of #1123, the client does not actually modify
 ciphersuites (this is intended to be implemented as a "configuration

docs/contributing.rst

@@ -20,8 +20,8 @@ once:
 
 .. code-block:: shell
 
-   git clone https://github.com/letsencrypt/letsencrypt
-   cd letsencrypt
+   git clone https://github.com/certbot/certbot
+   cd certbot
    ./letsencrypt-auto-source/letsencrypt-auto --os-packages-only
    ./tools/venv.sh
 
@@ -57,8 +57,8 @@ your pull request must have thorough unit test coverage, pass our
 `integration`_ tests, and be compliant with the :ref:`coding style
 <coding-style>`.
 
-.. _github issue tracker: https://github.com/letsencrypt/letsencrypt/issues
-.. _Good Volunteer Task: https://github.com/letsencrypt/letsencrypt/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+Volunteer+Task%22
+.. _github issue tracker: https://github.com/certbot/certbot/issues
+.. _Good Volunteer Task: https://github.com/certbot/certbot/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+Volunteer+Task%22
 
 Testing
 -------
@@ -175,8 +175,8 @@ Configurators may implement just one of those).
 There are also `~certbot.interfaces.IDisplay` plugins,
 which implement bindings to alternative UI libraries.
 
-.. _interfaces.py: https://github.com/letsencrypt/letsencrypt/blob/master/certbot/interfaces.py
-.. _plugins/common.py: https://github.com/letsencrypt/letsencrypt/blob/master/letsencrypt/plugins/common.py#L34
+.. _interfaces.py: https://github.com/certbot/certbot/blob/master/certbot/interfaces.py
+.. _plugins/common.py: https://github.com/certbot/certbot/blob/master/certbot/plugins/common.py#L34
 
 
 Authenticators
@@ -323,7 +323,7 @@ Steps:
    See `Known Issues`_. If it's not a known issue, fix any errors.
 
 .. _Known Issues:
-  https://github.com/letsencrypt/letsencrypt/wiki/Known-issues
+  https://github.com/certbot/certbot/wiki/Known-issues
 
 Updating the documentation
 ==========================

docs/packaging.rst

@@ -3,4 +3,4 @@ Packaging Guide
 ===============
 
 Documentation can be found at
-https://github.com/letsencrypt/letsencrypt/wiki/Packaging.
+https://github.com/certbot/certbot/wiki/Packaging.

docs/using.rst

@@ -194,7 +194,7 @@ Third-party plugins
 -------------------
 
 These plugins are listed at
-https://github.com/letsencrypt/letsencrypt/wiki/Plugins. If you're
+https://github.com/certbot/certbot/wiki/Plugins. If you're
 interested, you can also :ref:`write your own plugin <dev-plugin>`.
 
 Renewal
@@ -362,11 +362,11 @@ Getting help
 If you're having problems you can chat with us on `IRC (#certbot @
 OFTC) <https://webchat.oftc.net?channels=%23certbot>`_ or at
 `IRC (#letsencrypt @ freenode) <https://webchat.freenode.net?channels=%23letsencrypt>`_
-or get support on our `forums <https://community.letsencrypt.org>`_.
+or get support on the Let's Encrypt `forums <https://community.letsencrypt.org>`_.
 
 If you find a bug in the software, please do report it in our `issue
 tracker
-<https://github.com/letsencrypt/letsencrypt/issues>`_. Remember to
+<https://github.com/certbot/certbot/issues>`_. Remember to
 give us as much information as possible:
 
 - copy and paste exact command line used and the output (though mind
@@ -391,7 +391,7 @@ plugins cannot reach it from inside the Docker container.
 
 You should definitely read the :ref:`where-certs` section, in order to
 know how to manage the certs
-manually. https://github.com/letsencrypt/letsencrypt/wiki/Ciphersuite-guidance
+manually. https://github.com/certbot/certbot/wiki/Ciphersuite-guidance
 provides some information about recommended ciphersuites. If none of
 these make much sense to you, you should definitely use the
 certbot-auto_ method, which enables you to use installer plugins
@@ -526,7 +526,7 @@ whole process is described in the :doc:`contributing`.
 Comparison of different methods
 -------------------------------
 
-Unless you have a very specific requirements, we kindly ask you to use
+Unless you have a very specific requirements, we kindly suggest that you use
 the certbot-auto_ method. It's the fastest, the most thoroughly
 tested and the most reliable way of getting our software and the free
 SSL certificates!