Update continuous-deployment.md

Co-authored-by: Akash Askoolum <[email protected]>

continuous-deployment.md

@@ -5,7 +5,7 @@ Continuous Deployment (CD) is a software release process where verified changes
 
 You should have continuous deployment set up for your repository, with the following behaviours configured if applicable:
 * Automatically deploying changes to the `main` branch to production
-* Regularly redeploying the application on a schedule
+* Using an AMIgo AMI and regularly redeploying the application on a schedule
 * Restricting deployments if and when required
 
 You should already have [continuous integration](continuous-integration.md) configured in order to set up continuous deployment.

continuous-integration.md

@@ -4,6 +4,8 @@ Continuous Integration
 Continuous Integration (CI) is a practice where developers frequently push their code into a shared repository. 
 Automated builds and checks run on each check-in, allowing teams to detect problems early.
 
+## Tasks
+
 You should have continuous integration set up in your repository running the following tasks where relevant:
 * Running unit and integration tests
 * Building your application
@@ -16,7 +18,7 @@ You should have continuous integration set up in your repository running the fol
 * Use TeamCity to run continuous integration tasks
 * If possible, have a centralised script in the repository named `scripts/ci`  
     - This adheres to GitHub's [Scripts To Rule Them All pattern](https://github.com/github/scripts-to-rule-them-all)
-* For public repositories, you can use [GitHub Actions](https://docs.github.com/en/actions) for some above tasks, but we are yet to develop a safe way of uploading artifacts to RiffRaff through it
+* You can use [GitHub Actions](https://docs.github.com/en/actions) for most above tasks, however there is not currently a departmental best practice for uploading artifacts to RiffRaff through it.
 
 ## Publishing artifacts