diff --git a/en/aws/ec2/default-vpc-in-use.md b/en/aws/ec2/default-vpc-in-use.md
index d6725c567..675c532ab 100644
--- a/en/aws/ec2/default-vpc-in-use.md
+++ b/en/aws/ec2/default-vpc-in-use.md
@@ -15,7 +15,7 @@
 | **Recommended Action** | Move resources from the default VPC to a new VPC created for that application or resource group. |
 
 ## Detailed Remediation Steps
-1. Log into the AWS Management Console.
+1. Log in to the AWS Management Console.
 2. Select the "Services" option and search for VPC. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step2.png"/>
 3. Scroll down the left navigation panel and choose "Your VPC" under "VPC Dashboard". </br> <img src="/resources/aws/ec2/default-vpc-in-use/step3.png"/>
 4. Copy the default "VPC ID" from the "VPC" dashboard.</br>  <img src="/resources/aws/ec2/default-vpc-in-use/step4.png"/>
@@ -24,10 +24,10 @@
 7. Click inside the " Filter by tags and attributes or search by keyword box" and paste the "VPC ID" we copied in Step4 and press "Enter". AWS console will return one or more EC2 instances using "default VPC".</br> <img src="/resources/aws/ec2/default-vpc-in-use/step7.png"/>
 8. Repeat steps number 2 - 6 to check other AWS regions. </br>
 9. Navigate to "VPC Dashboard" and choose "Your VPC" and click on the "Create VPC" button at the top panel. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step9.png"/>
-10. Inside "Create VPC" dialog box provide a name to the new VPC and within IPv4 CIDR block box, specify an IPv4 address range for the new VPC. Select the "IPv6 CIDR block" and "Tenancy" option as per the application requirement and click on the "Create" button at the bottom to create a new VPC. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step10.png"/>
-11. Navigate to the "EC2 dashboard" and select the "EC2 Instance" which is on default VPC. Click on the "Actions" button at the top and choose "Image" to create an "Amazon Machine Image" of the selected Instance. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step11.png"/>
+10. Inside "Create VPC" dialog box provide a name to the new VPC and within IPv4 CIDR block box, specify an IPv4 address range for the new VPC. Select the "IPv6 CIDR block" and "Tenancy" option as per the application requirement and click on the "Create VPC" button at the bottom to create a new VPC. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step10.png"/>
+11. Navigate to the "EC2 dashboard" and select the "EC2 Instance" which is on default VPC. Click on the "Actions" button at the top and choose "Image and templates" and choose "Create image" to create an "Amazon Machine Image" of the selected Instance. </br> <img src="/resources/aws/ec2/default-vpc-in-use/step11.png"/>
 12. Under the "Create Image" panel provide the "Image Name" and "Image Description" and click on the "Create Image" button at the bottom.</br> <img src="/resources/aws/ec2/default-vpc-in-use/step12.png"/>
 13. Once the "AMI" is created click on the "Launch Instance" button at the top panel to create a new "Instance".</br> <img src="/resources/aws/ec2/default-vpc-in-use/step13.png"/>
-14. Clcik on the "My AMIs" option and choose the "AMI".</br> <img src="/resources/aws/ec2/default-vpc-in-use/step14.png"/>
-15. Provide the other necessary details for the new "EC2-Instance" and under the "Configuration Instance" choose the newly created "VPC" instead of default VPC.</br> <img src="/resources/aws/ec2/default-vpc-in-use/step15.png"/>
-16. Click on the "Launch" button once reviewing the necessary configuration to launch the new "EC2-Instance". Once the new "EC2-Instance" is in healthy state remove the older "EC2-Instance" which is using the default VPC.</br>
+14. Click on the "My AMIs" option and choose the "AMI".</br> <img src="/resources/aws/ec2/default-vpc-in-use/step14.png"/>
+15. Provide the other necessary details for the new "EC2-Instance", then click the "Configure Instance Details" and choose the newly created "VPC" instead of default VPC.</br> <img src="/resources/aws/ec2/default-vpc-in-use/step15.png"/>
+16. Click on the "Review and Launch" button once reviewing the necessary configuration to launch the new "EC2-Instance". Once the new "EC2-Instance" is in healthy state remove the older "EC2-Instance" which is using the default VPC.</br>
diff --git a/resources/aws/ec2/default-vpc-in-use/step10.png b/resources/aws/ec2/default-vpc-in-use/step10.png
index 3758840c0..159aa1013 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step10.png and b/resources/aws/ec2/default-vpc-in-use/step10.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step11.png b/resources/aws/ec2/default-vpc-in-use/step11.png
index d4b729edd..6a71d7daa 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step11.png and b/resources/aws/ec2/default-vpc-in-use/step11.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step12.png b/resources/aws/ec2/default-vpc-in-use/step12.png
index 3a6cc9137..67a58c066 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step12.png and b/resources/aws/ec2/default-vpc-in-use/step12.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step13.png b/resources/aws/ec2/default-vpc-in-use/step13.png
index 3e2b38e1e..35e28ae31 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step13.png and b/resources/aws/ec2/default-vpc-in-use/step13.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step2.png b/resources/aws/ec2/default-vpc-in-use/step2.png
index f51dc51b9..cec6ee101 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step2.png and b/resources/aws/ec2/default-vpc-in-use/step2.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step3.png b/resources/aws/ec2/default-vpc-in-use/step3.png
index cf94769dd..4999d3818 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step3.png and b/resources/aws/ec2/default-vpc-in-use/step3.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step4.png b/resources/aws/ec2/default-vpc-in-use/step4.png
index 2b0303c28..8ca1e4b88 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step4.png and b/resources/aws/ec2/default-vpc-in-use/step4.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step5.png b/resources/aws/ec2/default-vpc-in-use/step5.png
index f2ff15a32..a69039218 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step5.png and b/resources/aws/ec2/default-vpc-in-use/step5.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step6.png b/resources/aws/ec2/default-vpc-in-use/step6.png
index aec6a7068..f2ddabed8 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step6.png and b/resources/aws/ec2/default-vpc-in-use/step6.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step7.png b/resources/aws/ec2/default-vpc-in-use/step7.png
index 94016d65e..f1f4df7f6 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step7.png and b/resources/aws/ec2/default-vpc-in-use/step7.png differ
diff --git a/resources/aws/ec2/default-vpc-in-use/step9.png b/resources/aws/ec2/default-vpc-in-use/step9.png
index fa7df5583..6a4ec210a 100644
Binary files a/resources/aws/ec2/default-vpc-in-use/step9.png and b/resources/aws/ec2/default-vpc-in-use/step9.png differ