move github refs back to LE

docs/api/cb_util.rst

@@ -1,5 +0,0 @@
-:mod:`certbot.cb_util`
---------------------------
-
-.. automodule:: certbot.cb_util
-   :members:

docs/api/le_util.rst

@@ -0,0 +1,5 @@
+:mod:`certbot.le_util`
+--------------------------
+
+.. automodule:: certbot.le_util
+   :members:

docs/ciphers.rst

@@ -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/certbot/certbot/wiki/Ciphersuite-guidance
+https://github.com/letsencrypt/letsencrypt/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/certbot/certbot/issues/1123
+https://github.com/letsencrypt/letsencrypt/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

@@ -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/certbot/certbot/issues
-.. _Good Volunteer Task: https://github.com/certbot/certbot/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+Volunteer+Task%22
+.. _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
 
 Testing
 -------
@@ -146,7 +146,7 @@ encouraged) make sure to install prerequisites as listed in
 ``certbot-nginx/tests/boulder-integration.sh`` and rerun
 the integration tests suite.
 
-.. _Boulder: https://github.com/certbot/boulder
+.. _Boulder: https://github.com/letsencrypt/boulder
 .. _Go: https://golang.org
 
 
@@ -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/certbot/certbot/blob/master/certbot/interfaces.py
-.. _plugins/common.py: https://github.com/certbot/certbot/blob/master/certbot/plugins/common.py#L34
+.. _interfaces.py: https://github.com/letsencrypt/letsencrypt/blob/master/letsencrypt/interfaces.py
+.. _plugins/common.py: https://github.com/letsencrypt/letsencrypt/blob/master/letsencrypt/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/certbot/certbot/wiki/Known-issues
+  https://github.com/letsencrypt/letsencrypt/wiki/Known-issues
 
 Updating the documentation
 ==========================

docs/using.rst

@@ -93,10 +93,10 @@ s3front_    Y    Y    Integration with Amazon CloudFront distribution of S3 buck
 gandi_      Y    Y    Integration with Gandi's hosting products and API
 =========== ==== ==== ===============================================================
 
-.. _plesk: https://github.com/plesk/certbot-plesk
-.. _haproxy: https://code.greenhost.net/open/certbot-haproxy
-.. _s3front: https://github.com/dlapiduz/certbot-s3front
-.. _gandi: https://github.com/Gandi/certbot-gandi
+.. _plesk: https://github.com/plesk/letsencrypt-plesk
+.. _haproxy: https://code.greenhost.net/open/letsencrypt-haproxy
+.. _s3front: https://github.com/dlapiduz/letsencrypt-s3front
+.. _gandi: https://github.com/Gandi/letsencrypt-gandi
 
 Future plugins for IMAP servers, SMTP servers, IRC servers, etc, are likely to
 be installers but not authenticators.
@@ -194,7 +194,7 @@ Third-party plugins
 -------------------
 
 These plugins are listed at
-https://github.com/certbot/certbot/wiki/Plugins. If you're
+https://github.com/letsencrypt/letsencrypt/wiki/Plugins. If you're
 interested, you can also :ref:`write your own plugin <dev-plugin>`.
 
 Renewal
@@ -365,7 +365,7 @@ get support on our `forums <https://community.certbot.org>`_.
 
 If you find a bug in the software, please do report it in our `issue
 tracker
-<https://github.com/certbot/certbot/issues>`_. Remember to
+<https://github.com/letsencrypt/letsencrypt/issues>`_. Remember to
 give us as much information as possible:
 
 - copy and paste exact command line used and the output (though mind
@@ -390,7 +390,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/certbot/certbot/wiki/Ciphersuite-guidance
+manually. https://github.com/letsencrypt/letsencrypt/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