add link to cht core repo, add steps to delete vols and snaps per fee…

…dback

content/en/contribute/code/core/deploy-on-eks.md

@@ -212,7 +212,7 @@ And then follow these steps:
        }
    ]
    ```
-5. Switch to the production cluster and then find the `subPath` of the deployment you made the snapshot from. The `COUCH-DB-NAME` is usually `cht-couchdb`. But, it can sometimes be `cht-couchdb-1` (check `./troubleshooting/list-deployments <your-namespace>` if you still don't know).  Including the `use-context`, the two calls are: 
+5. Switch to the production cluster and then find the `subPath` of the deployment you made the snapshot from. The `COUCH-DB-NAME` is usually `cht-couchdb`. But, it can sometimes be `cht-couchdb-1` (check `./troubleshooting/list-deployments <your-namespace>` if you still don't know).  Including the `use-context`, the two calls are below.  Note that `troubleshooting` directory is in the [CHT Core repo](https://github.com/medic/cht-core/tree/master/scripts/deploy/troubleshooting): 
 
    ```shell
    kubectl config use-context arn:aws:eks:eu-west-2:720541322708:cluster/prod-cht-eks
@@ -246,7 +246,18 @@ And then follow these steps:
 
 8. Login using the `user` and `password` set above, which should match the production instance.
 
+9. When you're done with this deployment, you can delete it with helm:
 
+   ```shell
+   helm delete USERNAME-dev --namespace USERNAME-dev
+   ```
+
+10. Now that no resources are using the volume, you should delete it.  If you created a snapshot, you should delete that as well.  Be sure to replace `vol-f9dsa0f9sad09f0dsa` and `snap-432490821280432092` with your actual IDs. You only need to delete the snapshot if you created it above, **do no delete snapshots you did not create**:
+
+   ```shell
+   aws ec2 delete-volume --region eu-west-2 --volume-id vol-f9dsa0f9sad09f0dsa
+   aws ec2 delete-snapshot --snapshot-id snap-432490821280432092
+   ```
 
 ## References and Debugging