AWS efs documentation change
Summary
Changed 'EFS Access Points' to lowercase 'EFS access points' for consistency
Security assessment
The change is purely stylistic/capitalization correction with no security implications
Diff
diff --git a/efs/latest/ug/manage-fs-access-vpc-peering.md b/efs/latest/ug/manage-fs-access-vpc-peering.md index 5b875c9f0..a8ef2af4f 100644 --- a//efs/latest/ug/manage-fs-access-vpc-peering.md +++ b//efs/latest/ug/manage-fs-access-vpc-peering.md @@ -7 +7 @@ -You can mount your EFS file system using IAM authorization for NFS clients and EFS Access Points using the EFS mount helper. By default, the EFS mount helper uses domain name service (DNS) to resolve the IP address of your EFS mount target. If you are mounting the file system from a different account or virtual private cloud (VPC), you need to resolve the EFS mount target manually. +You can mount your EFS file system using IAM authorization for NFS clients and EFS access points using the EFS mount helper. By default, the EFS mount helper uses domain name service (DNS) to resolve the IP address of your EFS mount target. If you are mounting the file system from a different account or virtual private cloud (VPC), you need to resolve the EFS mount target manually.