AWS vpc: Grammar and wording fixes in PrivateLink resource configuration docs
Summary
Minor copyediting: added commas, changed 'service-network' to 'service network', and fixed a typo ('tag you' to 'tag your'). No technical or security content changed.
Security assessment
The only changes are punctuation, hyphenation, and a typo fix in prose. No security feature, permission, or configuration behavior is documented or altered.
Evidence
+ 6. (Optional) To tag your VPC endpoint, choose **Add new tag** , and enter a tag key and tag value.
Diff
diff --git a/vpc/latest/privatelink/resource-configuration-associations.md b/vpc/latest/privatelink/resource-configuration-associations.md index 449df4c58..097ea02fa 100644 --- a//vpc/latest/privatelink/resource-configuration-associations.md +++ b//vpc/latest/privatelink/resource-configuration-associations.md @@ -11 +11 @@ Manage service network resource associationsManage resource VPC endpoint associa -Consumer accounts with which you share a resource configuration with and clients in your account can access the resource configuration either directly using a resource VPC endpoint or through a service-network endpoint. As a result your resource configuration will have endpoint associations and service network associations. +Consumer accounts with which you share a resource configuration, and clients in your account, can access the resource configuration either directly using a resource VPC endpoint or through a service network endpoint. As a result, your resource configuration will have endpoint associations and service network associations. @@ -56 +56 @@ Use the [delete-service-network-resource-association](https://awscli.amazonaws.c -Consumer accounts with access to your resource configuration or clients in your account can access the resource configuration using a resource VPC endpoint. If your resource configuration has a custom domain name, you can use enable private DNS to allow VPC Lattice to provision private hosted zones for your resource endpoint or service-network endpoint. With this, clients can directly curl the domain name to access the resource configuration. For more information, see [Custom domain names for resource consumers](./resource-configuration.html#custom-domain-name-resource-consumers). +Consumer accounts with access to your resource configuration or clients in your account can access the resource configuration using a resource VPC endpoint. If your resource configuration has a custom domain name, you can use enable private DNS to allow VPC Lattice to provision private hosted zones for your resource endpoint or service network endpoint. With this, clients can directly curl the domain name to access the resource configuration. For more information, see [Custom domain names for resource consumers](./resource-configuration.html#custom-domain-name-resource-consumers). @@ -67 +67 @@ AWS Management Console - 4. Select the VPC, subnets and security groups. + 4. Select the VPC, subnets, and security groups. @@ -71 +71 @@ AWS Management Console - 6. (Optional) To tag you VPC endpoint, choose **Add new tag** , and enter a tag key and tag value. + 6. (Optional) To tag your VPC endpoint, choose **Add new tag** , and enter a tag key and tag value.