Minor tweaks.

Author: rkistner

installation/database-setup/private-endpoints.mdx

@@ -4,9 +4,9 @@ title: "Private Endpoints"
 
 ## PowerSync Cloud: AWS Private Endpoints
 
-To avoid exposing a database in AWS to the public internet, AWS Private Endpoints ([AWS PrivateLink](https://aws.amazon.com/privatelink/)) is an option that provides private networking between the source database and the PowerSync Service. Private Endpoints are currently available on our [Team and Enterprise plans](https://www.powersync.com/pricing).
+To avoid exposing a database in AWS to the public internet, AWS Private Endpoints ([AWS PrivateLink](https://aws.amazon.com/privatelink/)) are an option that provides private networking between the source database and the PowerSync Service. Private Endpoints are currently available on our [Team and Enterprise plans](https://www.powersync.com/pricing).
 
-We use Private Endpoints instead of VPC Peering, to avoid exposing any other resources between the VPCs.
+We use Private Endpoints instead of VPC Peering, to ensure that no other resources are exposed between the VPCs.
 
 <Warning>
 Do not rely on Private Endpoints as the only form of security. Always use strong database passwords, and use client certificates if additional security is required.
@@ -23,8 +23,9 @@ Do not rely on Private Endpoints as the only form of security. Always use strong
 
 * AWS PrivateLink is the overarching feature on AWS.
 
-* VPC/Private Endpoint Service is the service that exposes the database, and lives in the same VPC as the source database. It provides a one-way connection to the specific database, without exposing any other resources in the VPC.
-  * Endpoint Service Name is an unique identifier for this Endpoint Service.
+* VPC/Private Endpoint Service is the service that exposes the database, and lives in the same VPC as the source database. It provides a one-way connection to the database without exposing other resources in the VPC..
+
+  * Endpoint Service Name is a unique identifier for this Endpoint Service.
   * Each Endpoint Service may have multiple Private Endpoints in different VPCs.
 
 * VPC/Private Endpoint is the endpoint in the PowerSync VPC. This is what the PowerSync instance connects to.
@@ -52,7 +53,7 @@ Limitations:
 3. Select AWS and the relevant AWS region.
 4. Wait for the Endpoint Service to be created.
 5. "Your VPC ID" and "Your Subnet IDs" are not relevant for PowerSync - leave those blank.
-6. Do not run the command to create the "VPC Interface Endpoint" - this is done on the PowerSync side.
+6. Avoid running the command to create the "VPC Interface Endpoint"; this step is handled by PowerSync.
 7. Note the Endpoint Service Name. This is displayed in the command to run, as the `--service-name` option.
 
 The Service Name should look something like `com.amazonaws.vpce.us-east-1.vpce-svc-0123456`.