corrections in add-user instructions

doc/deploying-a-server.md

@@ -21,9 +21,10 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
 * For each site you want to deploy on the server, e.g. example.com, do the following:
   * Does example.com already exist as a domain name?
     * If yes, then find out to what extent it's currently in use (and needs to be migrated with care). There are a few options:
-      * Transfer the domain into your DNR account.
+      * Transfer the domain into your DNR account
       * Set up DNS hosting for it and ask the owner to set authoritative DNS to the DNS servers you control
-      * Ask the user to keep DNR and DNS control where it is currently, but to switch DNS when it's ready at the new server
+      * Ask the user to keep DNR and DNS control where it is currently, but to switch DNS when it's ready at the new server, and every time
+        you add or remove an IP address (not a good idea, unless the user insists that they prefer this option)
       * In any case, you will probably need access to the hostmaster@example.com email address, for the StartSSL process *before*
         the final DNS switch. You could also ask them to tell you the verification code that arrives there, but that has to be done
         in real time, immediately when you click 'verify' in the StartSSL UI. If they forward the email the next day, then the token
@@ -36,9 +37,8 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
     (from StartSSL or elswhere) for example.com and concatenate the certificate
     and its unencrypted private key into `indiehosters/user-data/example.com/tls.pem`
   * Make sure the TLS certificate is valid (use `scripts/check-cert.sh` for this).
-  * Now run `deploy/add-site.sh k3 example.com https://github.com/someone/example.com.git` again. It will make sure the server is in the
-    correct state, and scp the user data and the
+  * Now run `deploy/add-site.sh k3 example.com ../hoster-data/TLS/example.com.pem https://github.com/someone/example.com.git root`.
+    It will make sure the server is in the correct state, and git pull and scp the user data and the
     approved cert into place, start a container running the image requested, update haproxy config, and restart the haproxy container.
-  * Test the site using your /etc/hosts. If you did not import data, there should be some default message there.
-  * Switch DNS and note down the current DNS situation (or if you're hosting
-    a subdomain of another domain, update whichever is the zone file you edited).
+  * Test the site using your /etc/hosts. You should see the data from the git repo on both http and https.
+  * Switch DNS and monitoring.