fix(docs): update certbot-hook links

README.md

@@ -183,7 +183,7 @@ While there are certainly many ways to get started hacking desec-stack, here is
 
        mkdir -p ~/bin
        cd ~/bin
-       curl https://raw.githubusercontent.com/desec-utils/certbot-hook/master/hook.sh > desec_certbot_hook.sh
+       curl https://raw.githubusercontent.com/desec-io/desec-certbot-hook/master/hook.sh > desec_certbot_hook.sh
        touch .dedynauth; chmod 600 .dedynauth
        echo DEDYN_TOKEN=${TOKEN} >> .dedynauth
        echo DEDYN_NAME=${DOMAIN} >> .dedynauth

docs/dyndns/lets-encrypt.rst

@@ -24,8 +24,8 @@ steps.
    the owner/permissions of the file (``chown``/``chmod``), so that it is only
    readable by your certbot user (usually ``root``). ::
 
-     wget https://raw.githubusercontent.com/desec-io/certbot-hook/master/hook.sh
-     wget https://raw.githubusercontent.com/desec-io/certbot-hook/master/.dedynauth
+     wget https://raw.githubusercontent.com/desec-io/desec-certbot-hook/master/hook.sh
+     wget https://raw.githubusercontent.com/desec-io/desec-certbot-hook/master/.dedynauth
 
 #. **Get a token.** You need to configure an API token so that certbot can use
    it to authenticate its requests towards the deSEC API. The easiest way to
@@ -66,8 +66,8 @@ steps.
    ``-d "YOURDOMAINNAME.dedyn.io" -d "www.YOURDOMAINNAME.dedyn.io"``.
 
    If you would like to help improve this hook script, please check out our
-   open issues at `<https://github.com/desec-utils/certbot-hook/issues>`_. We'd
-   highly appreciate your help!
+   open issues at `<https://github.com/desec-io/desec-certbot-hook/issues>`_.
+   We'd highly appreciate your help!
 
 
 Other ACME clients