Skip to content

Commit 79b71ae

Browse files
docs: standardize heading case and sync terminology (#480)
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
1 parent 5b1a96f commit 79b71ae

10 files changed

Lines changed: 11 additions & 11 deletions

File tree

client-sdks/advanced/gis-data-postgis.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Postgres' internal binary representation of the PostGIS type is as follows:
6262

6363
## On the Client
6464

65-
### AppSchema example
65+
### AppSchema Example
6666

6767
```js
6868
export const AppSchema = new Schema([

client-sdks/advanced/local-only-usage.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,6 @@ It is up to the application to then re-create the queue when the user registers,
8989

9090
A small amount of metadata per row is also stored in the `ps_oplog` table. We do not recommend deleting this data, as it can cause or hide consistency issues when later uploading the data. If the overhead in `ps_oplog` is too much, rather use the local-only tables approach.
9191

92-
### Local-only columns on synced tables
92+
### Local-Only Columns on Synced Tables
9393

9494
If you need individual local-only columns on a table that is otherwise synced (rather than an entirely local-only table), this can be achieved with [raw tables](/client-sdks/advanced/raw-tables#local-only-columns).

client-sdks/javascript-web/usage-examples.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "JavaScript Web SDK usage examples"
2+
title: "JavaScript Web SDK Usage Examples"
33
description: "Code snippets and patterns for common PowerSync JavaScript Web SDK scenarios."
44
sidebarTitle: "Usage Examples"
55
---

configuration/app-backend/cloudcode.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "CloudCode for MongoDB backends"
2+
title: "CloudCode for MongoDB Backends"
33
description: "Use JourneyApps CloudCode as a managed backend for PowerSync with MongoDB."
44
---
55

handling-writes/handling-write-validation-errors.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ For more details on strategies, see:
3939

4040

4141
<Card title="Custom Conflict Resolution" icon="code-merge" href="/handling-writes/custom-conflict-resolution" horizontal/>
42-
#### Dead-letter queue
42+
#### Dead-Letter Queue
4343

4444
Optionally, the server can implement a "dead-letter queue":
4545

integrations/supabase/local-development.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Local development with Supabase and PowerSync"
2+
title: "Local Development with Supabase and PowerSync"
33
description: "Set up local development with Supabase and PowerSync."
44
sidebarTitle: "Local Development"
55
---

resources/hipaa.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The Health Insurance Portability and Accountability Act (HIPAA) is a comprehensi
99

1010
Entities that handle ePHI must comply with the HIPAA Privacy Rule, Security Rule, and Breach Notification Rule.
1111

12-
PowerSync serves as a **Business Associate (BA)** for customers (the **Covered Entity** or their BA) who utilize our service to synchronize healthcare-related data. As a BA, PowerSync has specific legal obligations to safeguard ePHI that passes through our synchronization service.
12+
PowerSync serves as a **Business Associate (BA)** for customers (the **Covered Entity** or their BA) who utilize our service to synchronize healthcare-related data. As a BA, PowerSync has specific legal obligations to safeguard ePHI that passes through our sync service.
1313

1414
To achieve HIPAA compliance when using PowerSync, two primary conditions must be met:
1515

@@ -55,7 +55,7 @@ The customer remains the owner of their application, databases, and client devic
5555

5656
## PowerSync’s Responsibilities (as BA)
5757

58-
PowerSync’s core responsibility is to protect ePHI while it is in transit and temporarily processed by our synchronization service.
58+
PowerSync’s core responsibility is to protect ePHI while it is in transit and temporarily processed by our sync service.
5959

6060
As a Business Associate, PowerSync is directly liable for compliance with certain provisions of the HIPAA Rules and adheres to the terms of the BAA by:
6161

sync/advanced/sync-data-by-time.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Sync data by time with Sync Streams"
2+
title: "Sync Data by Time with Sync Streams"
33
description: "Filter and sync data based on time ranges using Sync Streams/Sync Rules, with patterns for recent-only and sliding-window queries."
44
sidebarTitle: "Sync Data by Time"
55
---

sync/rules/many-to-many-join-tables.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Many-to-many relationships and join tables in Sync Rules"
2+
title: "Many-to-Many Relationships and Join Tables in Sync Rules"
33
sidebarTitle: "Many-to-Many and Join Tables"
44
description: "Handle many-to-many relationships in Sync Rules using join table strategies."
55
---

tools/local-development.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Run PowerSync locally with Docker and the CLI"
2+
title: "Run PowerSync Locally with Docker and the CLI"
33
description: "Set up PowerSync locally for development using Docker and the CLI."
44
sidebarTitle: Local Development
55
---

0 commit comments

Comments
 (0)