diff --git a/_posts/2021-01-06-how-to-update-to-cis-13.adoc b/_posts/2021-01-06-how-to-update-to-cis-13.adoc
index cf0af9905..b266d782d 100644
--- a/_posts/2021-01-06-how-to-update-to-cis-13.adoc
+++ b/_posts/2021-01-06-how-to-update-to-cis-13.adoc
@@ -210,7 +210,7 @@ To help us achieve CIS 1.3 compliance, we've also created the `vpc-app-network-a
 
 If you are already using the `vpc-app-network-acl` or `vpc-mgmt-network-acl` modules, you need to update the
 source URL from the https://github.com/gruntwork-io/terraform-aws-vpc[`terraform-aws-vpc` module] (previously known
-as `module-vpc`). To make sure you won't delete your existing Network ACL rules, you need to follow our https://github.com/gruntwork-io/cis-infrastructure-modules-acme/blob/migration-nacl/networking/vpc-app/migration-guides/migrating_to_cis_v13.md[migration guide] that uses `terragrunt state mv` to update the state.
+as `module-vpc`). To make sure you won't delete your existing Network ACL rules, you need to follow our https://github.com/gruntwork-io/cis-infrastructure-modules-acme/blob/master/networking/vpc-app/migration-guides/migrating_to_cis_v13.md[migration guide] that uses `terragrunt state mv` to update the state.
 
 The new required arguments are `allow_administrative_remote_access_cidrs`, for your office CIDRs, `allow_administrative_remote_access_cidrs_private_app_subnets` and `allow_administrative_remote_access_cidrs_private_persistence_subnets`, for the private subnets, with the CIDRs of the VPC or specific subnets within that VPC.