Update Moving to production section with new server/cmds

README.md

@@ -78,14 +78,24 @@ If a DAG corresponds with another repo, be sure to add a [tag](https://airflow.a
 
 ### Moving to production
 
-Never commit directly to the `production` branch. Commit your changes to a development branch, push the branch to Github, and open a pull request against `production`. Once your PR is reviwed and approved, merge the branch to `production`.
+Never commit directly to the `production` branch. Commit your changes to a development branch, push the branch to Github, and open a pull request against `production`. Once your PR is reviewed and approved, merge the branch to `production`.
 
 Once merged, you will need to connect to our production Airflow host on the COA network, then pull down your changes from Github. Airflow will automatically load any DAG changes within five minutes. Activate your DAG through the Airflow web interface at `https://airflow.austinmobility.io/`.
 
 ```shell
-# atd-data03
-$ cd /usr/airflow/atd-airflow
-$ sudo git pull
+# dts-int-data-p01
+
+# become the superuser
+su -;
+
+# enter into the production airflow directory
+cd /srv/atd-airflow;
+
+# pull the changes
+git pull;
+
+# return to user-land
+exit;
 ```
 
 The production Airflow deployment uses a second Docker compose file which provides haproxy configuration overrides. To start the production docker compose stack use you must load both files in order: