diff --git a/docs/website/docs/general-usage/incremental-loading.md b/docs/website/docs/general-usage/incremental-loading.md
index 631b1a41ca..5094e56e4a 100644
--- a/docs/website/docs/general-usage/incremental-loading.md
+++ b/docs/website/docs/general-usage/incremental-loading.md
@@ -120,7 +120,7 @@ If you use the `merge` write disposition, but do not specify merge or primary ke
 The appended data will be inserted from a staging table in one transaction for most destinations in this case.
 :::
 
-Example: Dedup sort behavior example
+Example: Deduplication with Timestamp based sorting
 
 ```py
 # Sample data
@@ -145,13 +145,13 @@ def sample_data():
 ```
 When this resource is executed, the following deduplication rules are applied:
 
-1. For records with different values in the dedup_sort column:
+1. For records with different values in the `dedup_sort` column:
    - The record with the highest value is kept when using `desc`
-   - For example, between records with id=1, the one with metadata_modified="2024-01-02" is kept
+   - For example, between records with id=1, the one with `"metadata_modified"="2024-01-02"` is kept
 
 2. For records with identical values in the dedup_sort column:
    - The first occurrence encountered is kept
-   - For example, between records with id=2 and identical metadata_modified="2024-01-01", the first record (value="C") is kept
+   - For example, between records with id=2 and identical `"metadata_modified"="2024-01-01"`, the first record (value="C") is kept
 
 #### Delete records
 The `hard_delete` column hint can be used to delete records from the destination dataset. The behavior of the delete mechanism depends on the data type of the column marked with the hint: