From 1500c79cd62f0696e153f0d03676a83b5a9a2d2b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Mat=C3=ADas=20Kungfoo=20de=20la=20C=C3=A1mara=20Beo?= =?UTF-8?q?vide?= Date: Thu, 21 Dec 2023 13:23:04 -0300 Subject: [PATCH] Update docs/user-guide/playbooks/VPN-with-no-LandingZone.md Co-authored-by: Diego OJeda (BinBash) <38356409+diego-ojeda-binbash@users.noreply.github.com> --- docs/user-guide/playbooks/VPN-with-no-LandingZone.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/playbooks/VPN-with-no-LandingZone.md b/docs/user-guide/playbooks/VPN-with-no-LandingZone.md index 91a0dfe8..03ad45ae 100644 --- a/docs/user-guide/playbooks/VPN-with-no-LandingZone.md +++ b/docs/user-guide/playbooks/VPN-with-no-LandingZone.md @@ -338,7 +338,7 @@ to add SSM access. In `locals.tf` file check the variable `multiple_instances`. There the EC2 instances are defined, by default there are four. -Remember set the subnets in which the instances will be created. +Remember to set the subnets in which the instances will be created. Finally, apply the layer: