fix the file

deployment/README.md

@@ -115,11 +115,12 @@ If you want to host another pod on the same server, we will have to re-use the s
 
 > We assume you have already followed the above steps and have a single pod running already at this point
 
-1. Create a new directory for the new pod and copy the environment variables file from the previous pod for ease of editing
+1. Create a new directory for the new pod and download the environment variable file
     ```bash
     export PEARS_DIR_2=~/pears-pod-name-2 # replace pears-pod-name-2 with your new pod name
     mkdir -p ${PEARS_DIR_2}/data 
-    cp ~/pears-pod-name-1/.env ${PEARS_DIR_2}/.env
+    # You can also copy this file from your existing pod directory for ease of editing
+    wget https://raw.githubusercontent.com/PeARSearch/PeARS-federated/nvn/add-deploy-files/deployment/.env-template -O ${PEARS_DIR_2}/.env
     ```
 2. Change the environment details in the `.env` file:
     ```bash
@@ -157,7 +158,7 @@ If you want to host another pod on the same server, we will have to re-use the s
 
 4. To add another pod, you will have to first copy the `pears-federed` container definition to a new definition in the file with appropriate names as follows:
     ```
-    $ cat docker-compose.yaml
+    $ vim docker-compose.yaml
 
     version: '3.8'
 
@@ -181,7 +182,7 @@ If you want to host another pod on the same server, we will have to re-use the s
 
 5. Update `https-portal` pod to point to the new pod as well
     ```
-    $ cat docker-compose.yaml
+    $ vim docker-compose.yaml
 
     version: '3.8'