PCX Review

Author: Oxyjun

src/content/docs/r2/data-catalog/about-compaction.mdx

@@ -30,12 +30,12 @@ You can configure the target file size for compaction. Currently, the minimum is
 Different compute engines have different optimal file sizes, so check their documentation.
 
 Performance tradeoffs depend on your use case. For example, queries that return small amounts of data may perform better with smaller files, as larger files could result in reading unnecessary data.
-- For workloads that are more latency sensitive, consider a smaller target file size (for example, 64MB - 128MB)
-- For streaming ingest workloads, consider medium file sizes (for example, 128MB - 256MB)
-- For OLAP style queries that need to scan a lot of data, consider larger file sizes (for example, 256MB - 512MB)
+- For workloads that are more latency sensitive, consider a smaller target file size (for example, 64 MB - 128 MB)
+- For streaming ingest workloads, consider medium file sizes (for example, 128 MB - 256 MB)
+- For OLAP style queries that need to scan a lot of data, consider larger file sizes (for example, 256 MB - 512 MB)
 
 ## Current limitations
-- During open beta, compaction will compact up to 2GB worth of files once per hour for each table.
+- During open beta, compaction will compact up to 2 GB worth of files once per hour for each table.
 - Only data files stored in parquet format are currently supported with compaction.
 - Snapshot expiration and orphan file cleanup is not supported yet.
 - Minimum target file size is 64 MB and maximum is 512 MB.

src/content/docs/r2/data-catalog/manage-catalogs.mdx

@@ -88,7 +88,7 @@ Compaction improves query performance by combining the many small files created
    <DashButton url="/?to=/:account/r2/overview" />
 2. Select the bucket you want to enable compaction on.
 3. Switch to the **Settings** tab, scroll down to **R2 Data Catalog**, and click on the **Edit** icon next to the compaction card.
-4. Enable compaction and optionally set a target file size. The default is 128MB.
+4. Enable compaction and optionally set a target file size. The default is 128 MB.
 5. (Optional) Provide a Cloudflare API token for compaction to access and rewrite files in your bucket.
 6. Select **Save**.
 </Steps>
@@ -103,9 +103,13 @@ npx wrangler r2 bucket catalog compaction enable <BUCKET_NAME>  --target-size 12
 ```
 </TabItem>
 </Tabs>
-Compaction requires a Cloudflare API token with **both** R2 storage and R2 Data Catalog read/write permissions to act as a service credential. The compaction process uses this token to read files, combine them, and update table metadata. Refer to [Authenticate your Iceberg engine](#authenticate-your-iceberg-engine) for details on creating a token with the required permissions.
 
-Once enabled, compaction applies retroactively to all existing tables and automatically to newly created tables. During open beta, we currently compact up to 2GB worth of files once per hour for each table.
+:::note[API token permission requirements]
+Compaction requires a Cloudflare API token with both R2 storage and R2 Data Catalog read/write permissions to act as a service credential. The compaction process uses this token to read files, combine them, and update table metadata.
+
+Refer to [Authenticate your Iceberg engine](#authenticate-your-iceberg-engine) for details on creating a token with the required permissions.
+
+Once enabled, compaction applies retroactively to all existing tables and automatically to newly created tables. During open beta, we currently compact up to 2 GB worth of files once per hour for each table.
 
 ## Disable compaction
 Disabling compaction will prevent the process from running for all tables managed by the catalog. You can re-enable it at any time.