PR feedback

Author: Hein

mint.json

@@ -400,7 +400,7 @@
           "pages": [
             "tutorials/client/data/overview",
             "tutorials/client/data/cascading-delete",
-            "tutorials/client/data/map-local-uuid"
+            "tutorials/client/data/sequential-id-mapping"
           ]
         }
       ]

tutorials/client/data/overview.mdx

@@ -5,5 +5,5 @@ description: "A collection of tutorials showcasing various data management strat
 
 <CardGroup>
   <Card title="Cascading Delete" icon="database" href="/tutorials/client/data/cascading-delete" horizontal/>
-  <Card title="Auto-Incrementing ID Mapping " icon="database" href="/tutorials/client/data/map-local-uuid" horizontal/>
+  <Card title="Sequential ID Mapping" icon="database" href="/tutorials/client/data/sequential-id-mapping" horizontal/>
 </CardGroup>

tutorials/client/data/map-local-uuid.mdx renamed to tutorials/client/data/sequential-id-mapping.mdx

@@ -1,7 +1,7 @@
 ---
 title: Sequential ID Mapping
 description: In this tutorial we will show you how to map a local UUID to a remote sequential (auto-incrementing) ID.
-sidebarTitle: Auto-Incrementing ID Mapping
+sidebarTitle: Sequential ID Mapping
 keywords: ["data", "uuid", "map", "auto increment", "id", "sequential id"]
 ---
 
@@ -20,7 +20,7 @@ on the client and map them to sequential IDs on the backend database (Supabase i
 ### Overview
 Before we get started, let's outline the changes we will have to make:
 <Steps>
-    <Step title={"Data model"}>
+    <Step title={"Schema"}>
         Update the `lists` and `todos` tables
     </Step>
 
@@ -46,14 +46,14 @@ Before we get started, let's outline the changes we will have to make:
     </Step>
 </Steps>
 
-# Data Model
+# Schema
 
 In order to map the UUID to the integer ID, we need to update the
 - `lists` table by adding a `uuid` column, which will be the secondary ID, and
 - `todos` table by adding a `uuid` column, and a `list_uuid` foreign key column which references the `uuid` column in the `lists` table.
 
 <CodeGroup>
-    ```sql data model {3, 13, 21, 26}
+    ```sql schema {3, 13, 21, 26}
     create table public.lists (
         id serial,
         uuid uuid not null unique,
@@ -84,7 +84,7 @@ In order to map the UUID to the integer ID, we need to update the
     ```
 </CodeGroup>
 
-With the data mode updated, we now need a method to synchronize and map the `list_id` and `list_uuid` in the `todos` table, with the `id` and `uuid` columns in the `lists` table.
+With the schema updated, we now need a method to synchronize and map the `list_id` and `list_uuid` in the `todos` table, with the `id` and `uuid` columns in the `lists` table.
 We can achieve this by creating SQL triggers.
 
 # Create SQL Triggers
@@ -182,7 +182,7 @@ We will create the following two triggers that cover either scenario of updating
     </Accordion>
 </AccordionGroup>
 
-We now have triggers in place that will handle the mapping for our updated data model and
+We now have triggers in place that will handle the mapping for our updated schema and
 can move on to updating the Sync Rules to use the UUID column instead of the integer ID.
 
 # Update Sync Rules

usage/sync-rules/client-id.mdx

@@ -54,4 +54,4 @@ Use UUIDs on the client, then map them to sequential IDs when performing an upda
 
 This mapping must be performed wherever the UUIDs are referenced, including for every foreign key column.
 
-For more information, have a look at the [ID mapping tutorial](/tutorials/client/data/map-local-uuid).
+For more information, have a look at the [Sequential ID Mapping tutorial](/tutorials/client/data/sequential-id-mapping).