diff --git a/README.md b/README.md
index 6f269f7..33c6d53 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ This is the general workflow for provisioning and deploying a new images. Reason
 6. Click "Queue plan" in the top right corner, and confirm once the workflow reaches the "Plan Finished" state.
 7. Repeat steps 5-6 for each workspace once the new configuration has been rolled out across the entire fleet.
 
-## Infrastructure Modification Worflow
+## Infrastructure Modification Workflow
 
 The `instances` directory contains the Terraform configuration. You would want to make changes to Terraform to modify the infrastructure layout or hardware (e.g. new autoscaling groups, larger or more EC2 instances, etc). Our Terraform configuration currently manages all Permanent AMIs, EC2 instances, Autoscaling Groups, Launch Configurations, and Target Groups for the Load Balacers. Terraform does NOT manage: the Load Balancer itself, S3 buckets, SQS queues, VPCs, Security Groups, subnets, IAM, etc. To make changes to the infrastructure, push your changes to a branch, open a PR, and get a code review. Once the PR is merged, the change (depending on the directory they are in), should queue a `terraform plan` job our [Terraform Cloud organization](https://app.terraform.io/app/PermanentOrg/workspaces). Review the plan, and approve the changes if they look good. Terraform will then roll-out the new infrastructure.