Touchups

Author: szarnyasg

docs/preview/duckdb/advanced_features/data_inlining.md

@@ -32,7 +32,7 @@ SET ducklake_default_data_inlining_row_limit = 0;
 
 ### Per-Connection Override
 
-The `DATA_INLINING_ROW_LIMIT` ATTACH parameter overrides the default for a single connection. This setting is not persisted and must be specified on each attach:
+The `DATA_INLINING_ROW_LIMIT` parameter of the `ATTACH` statement overrides the default for a single connection. This setting is not persisted and must be specified on each attach:
 
 ```sql
 ATTACH 'ducklake:inlining.duckdb' AS my_ducklake (DATA_INLINING_ROW_LIMIT 10);
@@ -55,7 +55,7 @@ When insertion inlining is enabled, small inserts are stored directly in the met
 
 ```sql
 -- created and managed internally by DuckLake; one table per schema version
-ducklake_inlined_data_{table_id}_{schema_version} (
+ducklake_inlined_data_⟨table_id⟩_⟨schema_version⟩ (
     row_id         BIGINT,
     begin_snapshot BIGINT,
     end_snapshot   BIGINT,
@@ -110,7 +110,7 @@ When deletion inlining is enabled, deletes from existing Parquet data files that
 
 ```sql
 -- created and managed internally by DuckLake; one table per DuckLake table
-ducklake_inlined_delete_{table_id} (
+ducklake_inlined_delete_⟨table_id⟩ (
     file_id        BIGINT,
     row_id         BIGINT,
     begin_snapshot BIGINT

docs/preview/duckdb/guides/using_a_remote_data_path.md

@@ -24,39 +24,47 @@ DETACH tpch_sf1_ducklake;
 
 ## Generating the Data
 
-We generate the data using the [`tpchgen-cli`](https://github.com/clflushopt/tpchgen-rs/) tool:
+Generate the data using the [`tpchgen-cli`](https://github.com/clflushopt/tpchgen-rs/) tool:
 
 ```batch
 tpchgen-cli --scale-factor 1 --format parquet
 ```
 
 ## Populating the DuckLake
 
-We attach to the DuckLake with a _local data path_ using the `OVERRIDE_DATA_PATH true` flag:
+Populating the DuckLake requires the following steps:
 
-```sql
-ATTACH 'tpch-sf1.ducklake' AS tpch_sf1_ducklake (
-    TYPE ducklake,
-    DATA_PATH 'tpch-sf1',
-    OVERRIDE_DATA_PATH true
-);
-USE tpch_sf1_ducklake;
-```
+1. Attach to the DuckLake with a _local data path_ using the `OVERRIDE_DATA_PATH true` flag:
 
-We then load the data into the DuckLake:
+   ```sql
+   ATTACH 'tpch-sf1.ducklake' AS tpch_sf1_ducklake (
+       TYPE ducklake,
+       DATA_PATH 'tpch-sf1',
+       OVERRIDE_DATA_PATH true
+   );
+   USE tpch_sf1_ducklake;
+   ```
 
-```sql
-CREATE TABLE customer AS FROM 'customer.parquet';
-CREATE TABLE lineitem AS FROM 'lineitem.parquet';
-CREATE TABLE nation AS FROM 'nation.parquet';
-CREATE TABLE orders AS FROM 'orders.parquet';
-CREATE TABLE part AS FROM 'part.parquet';
-CREATE TABLE partsupp AS FROM 'partsupp.parquet';
-CREATE TABLE region AS FROM 'region.parquet';
-CREATE TABLE supplier AS FROM 'supplier.parquet';
-```
+2. Load the data into the DuckLake:
+
+   ```sql
+   CREATE TABLE customer AS FROM 'customer.parquet';
+   CREATE TABLE lineitem AS FROM 'lineitem.parquet';
+   CREATE TABLE nation AS FROM 'nation.parquet';
+   CREATE TABLE orders AS FROM 'orders.parquet';
+   CREATE TABLE part AS FROM 'part.parquet';
+   CREATE TABLE partsupp AS FROM 'partsupp.parquet';
+   CREATE TABLE region AS FROM 'region.parquet';
+   CREATE TABLE supplier AS FROM 'supplier.parquet';
+   ```
+
+3. Flush the inlined data:
+
+   ```sql
+   CALL ducklake_flush_inlined_data('tpch_sf1_ducklake');
+   ```
 
-Finally, we close DuckDB with `Ctrl + D` or `.quit`.
+4. Close the DuckDB session with `Ctrl + D` or `.quit`.
 
 ## Uploading the DuckLake