AWS vpc documentation change
Summary
Changed step numbering format from periods to colons (e.g., 'Step 1.' to 'Step 1:') throughout the document
Security assessment
Changes are purely formatting adjustments to step numbering syntax, with no security-related content modifications
Diff
diff --git a/vpc/latest/userguide/create-network-acl.md b/vpc/latest/userguide/create-network-acl.md index e8136634e..904bc16b7 100644 --- a/vpc/latest/userguide/create-network-acl.md +++ b/vpc/latest/userguide/create-network-acl.md @@ -5 +5 @@ -Step 1. Create a network ACLStep 2. Add rulesStep 3. Associate a subnet with a network ACL(Optional) Manage network ACLs using Firewall Manager +Step 1: Create a network ACLStep 2: Add rulesStep 3: Associate a subnet with a network ACL(Optional) Manage network ACLs using Firewall Manager @@ -13 +13 @@ The following tasks show you how to create a network ACL, add rules to the netwo - * Step 1. Create a network ACL + * Step 1: Create a network ACL @@ -15 +15 @@ The following tasks show you how to create a network ACL, add rules to the netwo - * Step 2. Add rules + * Step 2: Add rules @@ -17 +17 @@ The following tasks show you how to create a network ACL, add rules to the netwo - * Step 3. Associate a subnet with a network ACL + * Step 3: Associate a subnet with a network ACL @@ -24 +24 @@ The following tasks show you how to create a network ACL, add rules to the netwo -## Step 1. Create a network ACL +## Step 1: Create a network ACL @@ -56 +56 @@ You can create a custom network ACL for your VPC. The initial rules for a custom -## Step 2. Add rules +## Step 2: Add rules @@ -126 +126 @@ To use a protocol that's not listed, choose **Custom Protocol** for the type and -## Step 3. Associate a subnet with a network ACL +## Step 3: Associate a subnet with a network ACL