Description

After some customer scenarios w/ confusion, it seems that customers have confused point 4.b in the Set up a Network Peering Connection docs and faced issues with setting the right table. Some customers may need to use the route table for the VPC or in some cases customers have route tables per subnet.

Scope of changes

https://www.mongodb.com/docs/atlas/security-vpc-peering/
AWS section here 

Instead of step 4.b reading:
"Select the Route Table for your VPC."

It might bring more clarity to this section by adding this:
“Select the Route Table for your VPC or subnet(s)."

Impact to Other Docs

None