diff --git a/.dev-tools/install-nginx-4.sh b/.dev-tools/install-nginx-4.sh
index d203b9946..cf6319df2 100755
--- a/.dev-tools/install-nginx-4.sh
+++ b/.dev-tools/install-nginx-4.sh
@@ -81,7 +81,8 @@ sudo rm -rfv /etc/nginx/mybots.d/
 sudo rm -rfv /etc/nginx/myconf.d/
 sudo rm /etc/nginx/conf.d/*.conf
 sudo rm /etc/nginx/bots.d/*.conf
-sudo rm /etc/nginx/sites-available/default
+sudo rm /etc/nginx/sites-available/*
+sudo rm /etc/nginx/sites-enabled/*
 sudo rm /etc/nginx/nginx.conf
 ls -la /etc/nginx/
 sudo cp ${TRAVIS_BUILD_DIR}/.dev-tools/test1_conf_backup_nginxconf/nginx13.conf /etc/nginx/nginx.conf
@@ -188,7 +189,7 @@ printf "\n"
 echo "${bold}${yellow}----------------------------------------------------"
 echo "${bold}${yellow}Copy older globalblacklist.conf file to force update"
 echo "${bold}${yellow}----------------------------------------------------"
-sudo cp ${TRAVIS_BUILD_DIR}/.dev-tools/globalblacklist-dummy.conf /etc/nginx/myconf.d/globalblacklist.conf
+sudo cp ${TRAVIS_BUILD_DIR}/.dev-tools/globalblacklist-dummy.conf /etc/nginx/conf.d/globalblacklist.conf
 }
 
 forceUpdateTest2 () {
@@ -216,7 +217,7 @@ echo "${bold}${yellow}----------------------------------------------------------
 echo "${bold}${yellow}Make sure we test with latest generated globalblacklist.conf"
 echo "${bold}${yellow}------------------------------------------------------------"
 printf "\n"
-sudo cp ${TRAVIS_BUILD_DIR}/conf.d/globalblacklist.conf /etc/nginx/myconf.d/globalblacklist.conf
+sudo cp ${TRAVIS_BUILD_DIR}/conf.d/globalblacklist.conf /etc/nginx/conf.d/globalblacklist.conf
 }
 
 backupConfFiles () {
@@ -233,7 +234,6 @@ sudo cp /etc/nginx/nginx.conf ${TRAVIS_BUILD_DIR}/.dev-tools/test4_conf_files/ng
 
 
 installNginxMainstream
-cleanupNginx1
 checkDirectories
 activateVHost
 getinstallngxblocker
diff --git a/README.md b/README.md
index 06dfd8ea2..f89a95010 100755
--- a/README.md
+++ b/README.md
@@ -363,18 +363,23 @@ The Nginx Ultimate Bot Blocker is now WORKING and PROTECTING your web sites !!!
 
 <img src="https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/blob/master/.assets/nginx-ultimate-bad-bot-blocker-testing-instructions.jpg"/>
 
-**NOTE to Cloudflare Users !!!**
+### NOTE to Cloudflare Users !!!
 
 If you are a Cloudflare user who is using the Cloudflare CDN / Cacheing System you will see the following behavior when testing.
 
 The First test of a Bad User Agent will give you:
 - curl: (56) TCP connection reset by peer
+
 The Second test will give you:
 - curl: 520 Origin Error
 
 This is by design. The CDN is doing its work, meaning, the first response from your server said to the bot, "go away" by issuing it `444` or `443` responses.
+
 Cloudflare cache's that response and hence the second test gets served a `520 Origin Error` origin error message.
-While testing the blocker, disable the CDN / cacheing system and once you are happy with your tests, re-enable the CDN/Cache on your live environment as you do want the bots to get that response from Cloudflare. Most other CDN systems will probably show the same behavior so always disable a CDN during testing to rule out anything that will interfere with your testing. Always make sure to re-enable the CDN when done testing !!
+
+While testing the blocker, disable the CDN / cacheing system and once you are happy with your tests, re-enable the CDN/Cache on your live environment as you do want the bots to get that response from Cloudflare. 
+
+Most other CDN systems will probably show the same behavior so always disable a CDN during testing to rule out anything that will interfere with your testing. Always make sure to re-enable the CDN when done testing !!
 
 ************************************************
 <img src="https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/blob/master/.assets/step-11.png"/>