Small edits

cahofmeyr · cahofmeyr · commit 7df1c983e7f0 · 2025-01-22T15:11:47.000-07:00
diff --git a/architecture/architecture-overview.mdx b/architecture/architecture-overview.mdx
@@ -16,7 +16,7 @@ The [PowerSync Service](/architecture/powersync-service) and client SDK operate
 
 ### Protocol
 
-Learn about the sync protocol used between PowerSync clients and a [PowerSync service](/architecture/powersync-service):
+Learn about the sync protocol used between PowerSync clients and a [PowerSync Service](/architecture/powersync-service):
 
 <CardGroup>
 <Card title="PowerSync Protocol" icon="network-wired" href="/architecture/powersync-protocol" horizontal/>
diff --git a/installation/database-setup/private-endpoints.mdx b/installation/database-setup/private-endpoints.mdx
@@ -4,7 +4,7 @@ title: "Private Endpoints"
 
 ## PowerSync Cloud: AWS Private Endpoints
 
-To avoid exposing a database in AWS to the public internet, AWS Private Endpoints (AWS 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.
+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).
 
 
 <Warning>
@@ -14,8 +14,8 @@ Do not rely on Private Endpoints as the only form of security. Always use strong
 ## Current Limitations
 
 1. Private Endpoints are only supported for Postgres instances currently. [Contact us](/resources/contact-us) if you need this for MongoDB or MySQL.
-2. The guide below does not handle dynamic IPs if the RDS instance's IP changes. This needs additional work to automatically update the IP - see this [AWS Blog Post](https://aws.amazon.com/blogs/database/access-amazon-rds-across-vpcs-using-aws-privatelink-and-network-load-balancer/) on the topic. This is specifically relevant if using a RDS cluster with failover support.
-3. Self-service is not yet available on the PowerSync side - contact support to configure the instance.
+2. The guide below does not handle dynamic IPs if the RDS instance's IP changes. This needs additional work to automatically update the IP - see this [AWS blog post](https://aws.amazon.com/blogs/database/access-amazon-rds-across-vpcs-using-aws-privatelink-and-network-load-balancer/) on the topic. This is specifically relevant if using a RDS cluster with failover support.
+3. Self-service is not yet available on the PowerSync side - contact PowerSync support to configure the instance.
 4. Only AWS is supported currently, other cloud providers are not supported yet.
 
 ## Endpoint Service Setup
@@ -24,7 +24,7 @@ To configure a Private Endpoint Service, a network load balancer is required to
  1. Create a Target Group for the Network Load Balancer:
     1. Obtain the RDS Instance's private IP address. Make sure this points to a writable instance.
     2. Create a Target Group with IP addresses as target type, using the IP address from above. Use TCP protocol, and specify the database port (typically 5432 for Postgres).
-    3. Note: The IP address of your RDS instance may change over time. To maintain a consistent connection, consider implementing automation to monitor and update the target group's IP address as needed. See the [AWS Blog Post](https://aws.amazon.com/blogs/database/access-amazon-rds-across-vpcs-using-aws-privatelink-and-network-load-balancer/) on the topic.
+    3. Note: The IP address of your RDS instance may change over time. To maintain a consistent connection, consider implementing automation to monitor and update the target group's IP address as needed. See the [AWS blog post](https://aws.amazon.com/blogs/database/access-amazon-rds-across-vpcs-using-aws-privatelink-and-network-load-balancer/) on the topic.
  2. Create a Network Load Balancer (NLB):
     1. Select the same VPC as your RDS instance.
     2. Choose at least two subnets in different availability zones.
@@ -33,7 +33,7 @@ To configure a Private Endpoint Service, a network load balancer is required to
  3. Modify the security group associated with your RDS instance to permit traffic from the load balancer.
  4. Create a VPC Endpoint Service:
     1. In the AWS Management Console, navigate to the VPC service and select Endpoint Services.
-    2. Click on Create Endpoint Service.
+    2. Click on "Create Endpoint Service".
     3. Select the Network Load Balancer created in the previous step.
     4. If the load balancer is in one of the PowerSync regions (see below), it is not required to select any "Supported Region". If the load balancer is in a different region, select the region corresponding to your PowerSync instance here. Note that this will incur additional AWS charges.
     5. Decide whether to require acceptance for endpoint connections. Disabling acceptance can simplify the process but may reduce control over connections.
@@ -45,14 +45,14 @@ To configure a Private Endpoint Service, a network load balancer is required to
 
 On PowerSync, create a new instance, but do not configure the connection yet.
 
-[Contact us](/resources/contact-us) and provide the Service Name from above, as well as the PowerSync instance id created above. We will then configure the instance to use the Endpoint Service for the database connection.
+[Contact us](/resources/contact-us) and provide the Service Name from above, as well as the PowerSync instance ID created above. We will then configure the instance to use the Endpoint Service for the database connection.
 
 ## AWS Regions
 
 PowerSync currently runs in the AWS regions below. Make sure the region matching your PowerSync instance is supported in by the Endpoint Service.
 
- 1. US: us-east-1
- 2. EU: eu-west-1
- 3. BR: sa-east-1
- 4. JP: ap-northeast-1
- 5. AU: ap-southeast-2
+ 1. US: `us-east-1`
+ 2. EU: `eu-west-1`
+ 3. BR: `sa-east-1`
+ 4. JP: `ap-northeast-1`
+ 5. AU: `ap-southeast-2`
diff --git a/integration-guides/coolify.mdx b/integration-guides/coolify.mdx
@@ -200,7 +200,7 @@ The following Compose file serves as a universal starting point for deploying th
         - -c
         - 'mongosh --host mongo:27017 --eval ''try{rs.status().ok && quit(0)} catch {} rs.initiate({_id: "rs0", version: 1, members: [{ _id: 0, host : "mongo:27017" }]})'''
 
-    # PowerSync service
+    # PowerSync Service
     powersync:
         image: journeyapps/powersync-service:latest
         container_name: powersync
@@ -337,7 +337,7 @@ The following Compose file serves as a universal starting point for deploying th
 
 <AccordionGroup>
 
-  <Accordion title="Step 1: Add PowerSync service to project resources" defaultOpen={false}>
+  <Accordion title="Step 1: Add PowerSync Service to project resources" defaultOpen={false}>
     Add the PowerSync Service resource to your project by either scrolling through the `Services` section or by searching for `powersync` in the search bar.
     <Frame>
         <img src="/images/coolify/powersync_resource.png"/>
diff --git a/resources/faq.mdx b/resources/faq.mdx
@@ -38,7 +38,7 @@ mode: wide
   </Accordion>
 
   <Accordion title="I don’t have direct database access, and can only access data via an API. Can I use PowerSync for this?">
-    **Right now, we don’t have support for replicating data via APIs.** A workaround would be to have custom code to replicate the data from the API to a PostgreSQL instance, then sync that with PowerSync.We may add a way in the future to replicate the data directly from an API to the PowerSync service, without a database in between.
+    **Right now, we don’t have support for replicating data via APIs.** A workaround would be to have custom code to replicate the data from the API to a PostgreSQL instance, then sync that with PowerSync. We may add a way in the future to replicate the data directly from an API to the PowerSync Service, without a database in between.
   </Accordion>
 
   <Accordion title="Are “live queries” supported?">
diff --git a/resources/security.mdx b/resources/security.mdx
@@ -12,6 +12,12 @@ At PowerSync, we take security very seriously and everything we do is designed t
 * Additionally, customers on our [Enterprise plan](https://www.powersync.com/pricing) can request their data to be housed in managed, isolated tenants.
 * SOC 2 Type 2 audit results are available to customers on our [Enterprise plan](https://www.powersync.com/pricing). On our most recent annual SOC 2 audit, we had zero exceptions.
 
+
+### PowerSync Cloud: AWS Private Endpoints
+
+See [Private Endpoints](/installation/database-setup/private-endpoints) for using a private network to your database using AWS PrivateLink.
+
+
 ### Client-Side Security
 
 Refer to: [Data Encryption](/usage/use-case-examples/data-encryption)
diff --git a/resources/usage-and-billing/pricing-example.mdx b/resources/usage-and-billing/pricing-example.mdx
@@ -53,8 +53,8 @@ For 50,000 app installs (5,000 Daily Active Users): **$56/month** on the Pro pla
 ## Data Processing
 |               |      |
 |---------------|------|
-|Data replicated from Postgres to PowerSync service / month|100 messages / day \* 5,000 DAUs \* 0.25 KB \* 30 = 3.75 GB / month|
-|Data replicated from PowerSync service to app / month| 100 messages / day \* 5,000 DAUs \* 0.25 KB \* 30 = 3.75 GB / month|
+|Data replicated from Postgres to PowerSync Service / month|100 messages / day \* 5,000 DAUs \* 0.25 KB \* 30 = 3.75 GB / month|
+|Data replicated from PowerSync Service to app / month| 100 messages / day \* 5,000 DAUs \* 0.25 KB \* 30 = 3.75 GB / month|
 
 | Total data processing costs / month   |     |
 | --- | --- |
@@ -75,7 +75,7 @@ For 50,000 app installs (5,000 Daily Active Users): **$56/month** on the Pro pla
 | Cost for additional usage: | 5,000,000 \* $1/1,000,000 |
 | **Total usage costs** | **$5 / month** |
 
-## Replicated data cached on PowerSync service
+## Replicated data cached on PowerSync Service
 |     |     |
 | --- | --- |
 |Total size of replicated data to be cached and synced|100 messages / day \* 5,000 DAUs \* 0.25 KB \* 90 days = 11.25 GB|
diff --git a/self-hosting/local-development.mdx b/self-hosting/local-development.mdx
@@ -135,7 +135,7 @@ For some additional details on this file, see [PowerSync Service Setup](/self-ho
 
 Next, the `client_auth` sections needs to be completed.
 
-The PowerSync service can verify JWTs from client applications using either HMAC (HS\*) or RSA (RS\*) based algorithms. It can also obtain the necessary settings from Supabase automatically if you are using it.
+The PowerSync Service can verify JWTs from client applications using either HMAC (HS\*) or RSA (RS\*) based algorithms. It can also obtain the necessary settings from Supabase automatically if you are using it.
 
 1. In the case of Supabase, simply set the `supabase` key to `true`
 2. In the case of HS\* algorithms, specify the secret as base64 encoded in the `k`field.
diff --git a/usage/tools/monitoring-and-alerting.mdx b/usage/tools/monitoring-and-alerting.mdx
@@ -7,7 +7,7 @@ You can monitor activity and alert on issues and usage for your PowerSync Cloud
 
 * **Monitor Usage**: View time-series and aggregated usage data with [Usage Metrics](#usage-metrics)
 
-* **Monitor Service and Replication Activity**: Track your PowerSync service and replication logs with [Instance Logs](#instance-logs)
+* **Monitor Service and Replication Activity**: Track your PowerSync Service and replication logs with [Instance Logs](#instance-logs)
 
 * **Configure Alerts**: Set up alerts for replication issues or usage activity \*
 
