diff --git a/website/source/_daily_emails/2022-09-10.md b/website/source/_daily_emails/2022-09-10.md
index 5c6b7d22..ed55a9a1 100644
--- a/website/source/_daily_emails/2022-09-10.md
+++ b/website/source/_daily_emails/2022-09-10.md
@@ -7,9 +7,9 @@ tags: ["ansible"]
 
 Once you have a deployment that's run using Ansible, rather than running it manually, it's easy to automate it as part of a continuous integration pipeline and have your changes pushed automatically by tools like GitHub Actions and GitLab CI.
 
-You'll need to configure SSH by adding a known hosts file and a private key to allow the tool to connect to your server, but after that, it's just running the same Ansible commands.
+You'll need to configure SSH by adding a known hosts file and a private key so the tool can connect to your server, but after that, it's just running the same Ansible commands.
 
-If you're using Ansistrano or using other roles, you can install dependencies by running `ansible-galaxy`, and use `ansible-vault` to decrypt and use any encrypted variables - securely storing the Vault password an environment variables within your pipeline.
+If you're using Ansistrano or other roles, you can install dependencies by using `ansible-galaxy`, and `ansible-vault` to decrypt and use any encrypted variables - securely storing the Vault password and any other secrets as environment variables within your pipeline.
 
 Here's an example using GitHub Actions:
 
@@ -33,6 +33,6 @@ Here's an example using GitHub Actions:
   run: rm .vault-pass.txt
 ```
 
-Prior to these steps, I've added the SSH key and determined which inventory file to use by the updated branch. The Vault password is exported and removed once it has been used.
+Before these steps, I've added the SSH key and determined which inventory file to use by the updated branch. The Vault password is exported and then removed once it has been used.
 
-Automated tests and other code quality checks can be run in another job, ensuring that the deployment only happens if those checks pass, but assuming that all is good, the playbook will be run and the changes will be deployed automatically.
+Automated tests and other code quality checks can be run in prior job, ensuring that the deployment only happens if those checks pass, but assuming that all is good, the playbook will be run and the changes will be deployed automatically.