Documentation edits made through Mintlify web editor

Author: mintlify[bot]

usage/use-case-examples/prioritized-sync.mdx

@@ -3,18 +3,26 @@ title: "Prioritized Sync"
 description: "In some scenarios, you may want to sync tables using different priorities. For example, you may want to sync a subset of all tables first to log a user in as fast as possible, then sync the remaining tables in the background."
 ---
 
+<Info>
+  Note that this strategy is specifically to prioritize data on initial sync, and cannot be used for incremental sync after that.
+</Info>
+
 ## Overview
 
 The general approach is as follows:
 
 1. Define how many priority types you want - typically only two are needed: "high priority" and "the rest"
+
 2. Create a sync bucket for each priority type
+
 3. Use [client parameters](/usage/sync-rules/advanced-topics/client-parameters) to control which priorities you want the client to sync
 
 ## Example
+
 Suppose we have two tables: `lists` and `todos` (as per the standard todolist demo app [schema](/integration-guides/supabase-+-powersync#create-the-demo-database-schema)). Further, suppose we want the sync priority to behave as follows:
 
 1. First, sync all the user's lists, enabling us to render the initial screen in the app
+
 2. Then, sync the user's todos
 
 Below are the sync rules that will enable this:
@@ -36,7 +44,7 @@ bucket_definitions:
 It is recommended to set Client Parameters in the [Diagnostics App](https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app) to verify functionality at this point:
 
 <Frame>
-  <img src="/images/usage/use-case-prioritized.png"/>
+  <img src="/images/usage/use-case-prioritized.png" />
 </Frame>
 
 If everything checks out, you can then proceed to implement the client parameter switching accordingly in your app.