devdocs/deploy.md

@@ -27,8 +27,8 @@ Make sure main.js in client devmode is set to false (should just keep it that wa
 ### run build-release.bat
 check for errors
 
-## UPLOAD TEST to ayanova.com/download/next folder where it will be staged before officially being released and moved to parent download folder
-
+## UPLOAD INSTALLERS TO NEXT FOLDER
+UPLOAD releases to ayanova.com/download/next folder where it will be staged before officially being released and moved to parent download folder
 
 ### Test install to devops server
 ### Test install to windows server 
@@ -93,7 +93,7 @@ From the previous folder:  cp ../* . -p
 root@ubuntu-s-1vcpu-1gb-amd-sfo3-01:/var/www/html/ayanova.com/download# rm *
   (note: will not remove folders just files by default so ok to use)
 
-### upload 4 installer packages found in C:\data\code\raven\dist\installers
+### COPY INSTALLERS FROM NEXT FOLDER the 4 installer packages found in `ayanova.com/download/next`
 - Follow path and folder and url rules in case 4053 https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/4053
 - And also v8-migrate.exe if applicable
 
@@ -241,7 +241,7 @@ https://www.ayanova.com/download/migrate136.7z
     - If 502 BAD GATEWAY then AyaNova server is not up so the NGINX config bombs because it's proxying to it.
       - Actually, it just happened and what needs to be done is AyaNova container needs to be running BEFORE nginx container or it seems to get stuck
     execute .\restartnginx.sh
-    - Check logs with  sudo docker logs [containerID] to find out what happened
+    - Check logs with  sudo docker logs (containerID) to find out what happened
     - Or in some cases (once) Digital Ocean fucked up something
 
 - ERASE DB, FETCH LICENSE, GENERATE DATA