clarify docs

README.md

@@ -22,7 +22,7 @@ A collection of one-click buttons and scripts for deploying code-server to vario
   - VMs can support many workloads, such as running Docker or Kubernetes clusters
   - [👀 Docs for the VM install script](deploy-vm/)
 - Deployed containers do not persist, and are often rebuilt
-  - Containers can shut down when you are not using it, saving you money
+  - Containers can shut down when you are not using them, saving you money
   - All software and dependencies need to be defined in the `Dockerfile` or install script so they aren't destroyed on a rebuild. This is great if you want to have a new, clean environment every time you code
   - Storage may not be redundant. You may have to use [rclone](https://rclone.org/) to store your filesystem on a cloud service, for info:
 - [📄 Docs for code-server-deploy-container](deploy-container/)

deploy-container/entrypoint.sh

@@ -1,6 +1,5 @@
 #!/bin/bash
 
-# Allow user to aupply a start dir, default to /home/coder/project
 START_DIR=/home/coder/project
 
 # add rclone config and start rclone, if supplied
@@ -24,7 +23,7 @@ else
     chmod +x push_remote.sh pull_remote.sh
 
     if rclone ls $RCLONE_REMOTE_PATH; then
-        # grab the files from the remote instead
+        # grab the files from the remote instead of re-cloning the git repo
         echo "Pulling existing files from remote..."
         /home/coder/pull_remote.sh&
     else