diff --git a/tools/creating-new-drutopia-site.md b/tools/creating-new-drutopia-site.md
index 915c867..08ae06f 100644
--- a/tools/creating-new-drutopia-site.md
+++ b/tools/creating-new-drutopia-site.md
@@ -63,7 +63,7 @@ In order to get a configuration that has the proper site key, it is easiest to f
 
 If you are creating a specialized build of Drutopia, you will have to add that to the host vars, and build that prior to deploying the site. `ahoy vars-edit` and `ahoy deploy-build <build_target>` are used for this. Note that new builds should be added ONLY as absolutely required. Configuration, and themes should be leveraged as much as possible prior to resorting to a new build. If additional/different modules are required, a new build is required - do *NOT* add them to build_source except when they are known to be required for *ALL* Drutopia basic sites.
 
-Create a new site (member entry) per instructions in Drutopia hosting. The simplest method is to use `ahoy new-site <member-slug>` and follow it's output to get started. Then use `ahoy deploy-site <member-instance>` to deploy one.
+Create a new site (member entry) per instructions in Drutopia hosting. The simplest method is to use `ahoy new-site <member-slug>` and follow it's output to get started. Then use `ahoy deploy-site <member-instance>` to deploy one. Because the install using `drush site-install` that would be run when `drupal_install: true` is set in the site settings in Drutopia hosting, it is currently recommended to set this to false and use the UI installer or run `php docroot/core/scripts/drupal quick-start drutopia --no-interaction` when ssh'd into the server.
 
 ### Configure drush aliases
 
@@ -107,7 +107,7 @@ While in `web/sites/default/settings.php` also prevent site administrators being
 $conf['allow_authorize_operations'] = FALSE;
 ```
 
-(All this should be updated to use a distribution-wide settings.php when we have that.)
+(All this should be updated to use a distribution-wide settings.php when we have that. Until the, use `git add -f web/sites/default/settings.php` to include this in your repo)
 
 Once you also have a working Drush installation and a live instance, you can then aquire and export the initial configuration with: