diff --git a/website/www/site/content/en/documentation/io/managed-io.md b/website/www/site/content/en/documentation/io/managed-io.md
index ec3bb90183d4..925f55aa52a5 100644
--- a/website/www/site/content/en/documentation/io/managed-io.md
+++ b/website/www/site/content/en/documentation/io/managed-io.md
@@ -59,7 +59,7 @@ and Beam SQL is invoked via the Managed API under the hood.
       <th>Write Configuration</th>
     </tr>
     <tr>
-      <td><strong>ICEBERG_CDC</strong></td>
+      <td><strong>ICEBERG</strong></td>
       <td>
         <strong>table</strong> (<code style="color: green">str</code>)<br>
         catalog_name (<code style="color: green">str</code>)<br>
@@ -67,17 +67,23 @@ and Beam SQL is invoked via the Managed API under the hood.
         config_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
         drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
         filter (<code style="color: green">str</code>)<br>
-        from_snapshot (<code style="color: #f54251">int64</code>)<br>
-        from_timestamp (<code style="color: #f54251">int64</code>)<br>
         keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        poll_interval_seconds (<code style="color: #f54251">int32</code>)<br>
-        starting_strategy (<code style="color: green">str</code>)<br>
-        streaming (<code style="color: orange">boolean</code>)<br>
-        to_snapshot (<code style="color: #f54251">int64</code>)<br>
-        to_timestamp (<code style="color: #f54251">int64</code>)<br>
       </td>
       <td>
-        Unavailable
+        <strong>table</strong> (<code style="color: green">str</code>)<br>
+        autosharding (<code style="color: orange">boolean</code>)<br>
+        catalog_name (<code style="color: green">str</code>)<br>
+        catalog_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
+        config_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
+        direct_write_byte_limit (<code style="color: #f54251">int32</code>)<br>
+        distribution_mode (<code style="color: green">str</code>)<br>
+        drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        only (<code style="color: green">str</code>)<br>
+        partition_fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        sort_fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        table_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
+        triggering_frequency_seconds (<code style="color: #f54251">int32</code>)<br>
       </td>
     </tr>
     <tr>
@@ -109,7 +115,7 @@ and Beam SQL is invoked via the Managed API under the hood.
       </td>
     </tr>
     <tr>
-      <td><strong>ICEBERG</strong></td>
+      <td><strong>ICEBERG_CDC</strong></td>
       <td>
         <strong>table</strong> (<code style="color: green">str</code>)<br>
         catalog_name (<code style="color: green">str</code>)<br>
@@ -117,31 +123,24 @@ and Beam SQL is invoked via the Managed API under the hood.
         config_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
         drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
         filter (<code style="color: green">str</code>)<br>
+        from_snapshot (<code style="color: #f54251">int64</code>)<br>
+        from_timestamp (<code style="color: #f54251">int64</code>)<br>
         keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        poll_interval_seconds (<code style="color: #f54251">int32</code>)<br>
+        starting_strategy (<code style="color: green">str</code>)<br>
+        streaming (<code style="color: orange">boolean</code>)<br>
+        to_snapshot (<code style="color: #f54251">int64</code>)<br>
+        to_timestamp (<code style="color: #f54251">int64</code>)<br>
       </td>
       <td>
-        <strong>table</strong> (<code style="color: green">str</code>)<br>
-        autosharding (<code style="color: orange">boolean</code>)<br>
-        catalog_name (<code style="color: green">str</code>)<br>
-        catalog_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
-        config_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
-        direct_write_byte_limit (<code style="color: #f54251">int32</code>)<br>
-        distribution_mode (<code style="color: green">str</code>)<br>
-        drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        only (<code style="color: green">str</code>)<br>
-        partition_fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        sort_fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        table_properties (<code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>)<br>
-        triggering_frequency_seconds (<code style="color: #f54251">int32</code>)<br>
+        Unavailable
       </td>
     </tr>
     <tr>
-      <td><strong>SQLSERVER</strong></td>
+      <td><strong>POSTGRES</strong></td>
       <td>
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
         connection_properties (<code style="color: green">str</code>)<br>
-        disable_auto_commit (<code style="color: orange">boolean</code>)<br>
         fetch_size (<code style="color: #f54251">int32</code>)<br>
         location (<code style="color: green">str</code>)<br>
         num_partitions (<code style="color: #f54251">int32</code>)<br>
@@ -163,10 +162,11 @@ and Beam SQL is invoked via the Managed API under the hood.
       </td>
     </tr>
     <tr>
-      <td><strong>POSTGRES</strong></td>
+      <td><strong>SQLSERVER</strong></td>
       <td>
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
         connection_properties (<code style="color: green">str</code>)<br>
+        disable_auto_commit (<code style="color: orange">boolean</code>)<br>
         fetch_size (<code style="color: #f54251">int32</code>)<br>
         location (<code style="color: green">str</code>)<br>
         num_partitions (<code style="color: #f54251">int32</code>)<br>
@@ -238,7 +238,7 @@ and Beam SQL is invoked via the Managed API under the hood.
 
 ## Configuration Details
 
-### `ICEBERG_CDC` Read
+### `ICEBERG` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -315,90 +315,194 @@ and Beam SQL is invoked via the Managed API under the hood.
     </tr>
     <tr>
       <td>
-        from_snapshot
+        keep
       </td>
       <td>
-        <code style="color: #f54251">int64</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Starts reading from this snapshot ID (inclusive).
+        A subset of column names to read exclusively. If null or empty, all columns will be read.
+      </td>
+    </tr>
+  </table>
+</div>
+
+### `ICEBERG` Write
+
+<div class="table-container-wrapper">
+  <table class="table table-bordered">
+    <tr>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
+    </tr>
+    <tr>
+      <td>
+        <strong>table</strong>
+      </td>
+      <td>
+        <code style="color: green">str</code>
+      </td>
+      <td>
+        A fully-qualified table identifier. You may also provide a template to write to multiple dynamic destinations, for example: `dataset.my_{col1}_{col2.nested}_table`.
       </td>
     </tr>
     <tr>
       <td>
-        from_timestamp
+        autosharding
       </td>
       <td>
-        <code style="color: #f54251">int64</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        Starts reading from the first snapshot (inclusive) that was created after this timestamp (in milliseconds).
+        Enables dynamic sharding to automatically adjust the number of parallel writers based on data volume. It handles data skew by further sub-dividing partitions into multiple shards to prevent bottlenecks during high-throughput writes. Only available with 'hash' distribution mode.
       </td>
     </tr>
     <tr>
       <td>
-        keep
+        catalog_name
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        A subset of column names to read exclusively. If null or empty, all columns will be read.
+        Name of the catalog containing the table.
       </td>
     </tr>
     <tr>
       <td>
-        poll_interval_seconds
+        catalog_properties
+      </td>
+      <td>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Properties used to set up the Iceberg catalog.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        config_properties
+      </td>
+      <td>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Properties passed to the Hadoop Configuration.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        direct_write_byte_limit
       </td>
       <td>
         <code style="color: #f54251">int32</code>
       </td>
       <td>
-        The interval at which to poll for new snapshots. Defaults to 60 seconds.
+        For a streaming pipeline, sets the limit for lifting bundles into the direct write path.
       </td>
     </tr>
     <tr>
       <td>
-        starting_strategy
+        distribution_mode
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The source's starting strategy. Valid options are: "earliest" or "latest". Can be overriden by setting a starting snapshot or timestamp. Defaults to earliest for batch, and latest for streaming.
+        Defines distribution of write data. Supported distributions:
+- none: don't shuffle rows (default)
+- hash: shuffle rows by partition key before writing data
       </td>
     </tr>
     <tr>
       <td>
-        streaming
+        drop
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Enables streaming reads, where source continuously polls for snapshots forever.
+        A list of field names to drop from the input record before writing. Is mutually exclusive with 'keep' and 'only'.
       </td>
     </tr>
     <tr>
       <td>
-        to_snapshot
+        keep
       </td>
       <td>
-        <code style="color: #f54251">int64</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Reads up to this snapshot ID (inclusive).
+        A list of field names to keep in the input record. All other fields are dropped before writing. Is mutually exclusive with 'drop' and 'only'.
       </td>
     </tr>
     <tr>
       <td>
-        to_timestamp
+        only
       </td>
       <td>
-        <code style="color: #f54251">int64</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        Reads up to the latest snapshot (inclusive) created before this timestamp (in milliseconds).
+        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        partition_fields
+      </td>
+      <td>
+        <code>list[<span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Fields used to create a partition spec that is applied when tables are created. For a field 'foo', the available partition transforms are:
+
+- `foo`
+- `truncate(foo, N)`
+- `bucket(foo, N)`
+- `hour(foo)`
+- `day(foo)`
+- `month(foo)`
+- `year(foo)`
+- `void(foo)`
+
+For more information on partition transforms, please visit https://iceberg.apache.org/spec/#partition-transforms.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        sort_fields
+      </td>
+      <td>
+        <code>list[<span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Fields used to set the table's sort order, applied when the table is created. Each entry has the form `<term> [asc|desc] [nulls first|nulls last]`, where `<term>` is a field name or one of the partition transforms (e.g. `bucket(col, 4)`, `day(ts)`). Direction defaults to ascending; null order defaults to nulls-first for ascending and nulls-last for descending. Note: this sets the table's declared sort order as metadata; it does not cause Beam to physically sort records before writing.
+For more information on sort orders, please visit https://iceberg.apache.org/spec/#sort-orders.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        table_properties
+      </td>
+      <td>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Iceberg table properties to be set on the table when it is created.
+For more information on table properties, please visit https://iceberg.apache.org/docs/latest/configuration/#table-properties.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        triggering_frequency_seconds
+      </td>
+      <td>
+        <code style="color: #f54251">int32</code>
+      </td>
+      <td>
+        For a streaming pipeline, sets the frequency at which snapshots are produced.
       </td>
     </tr>
   </table>
@@ -659,7 +763,7 @@ and Beam SQL is invoked via the Managed API under the hood.
   </table>
 </div>
 
-### `ICEBERG` Read
+### `ICEBERG_CDC` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -736,294 +840,279 @@ and Beam SQL is invoked via the Managed API under the hood.
     </tr>
     <tr>
       <td>
-        keep
+        from_snapshot
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        A subset of column names to read exclusively. If null or empty, all columns will be read.
+        Starts reading from this snapshot ID (inclusive).
       </td>
     </tr>
-  </table>
-</div>
-
-### `ICEBERG` Write
-
-<div class="table-container-wrapper">
-  <table class="table table-bordered">
-    <tr>
-      <th>Configuration</th>
-      <th>Type</th>
-      <th>Description</th>
-    </tr>
     <tr>
       <td>
-        <strong>table</strong>
+        from_timestamp
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        A fully-qualified table identifier. You may also provide a template to write to multiple dynamic destinations, for example: `dataset.my_{col1}_{col2.nested}_table`.
+        Starts reading from the first snapshot (inclusive) that was created after this timestamp (in milliseconds).
       </td>
     </tr>
     <tr>
       <td>
-        autosharding
+        keep
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Enables dynamic sharding to automatically adjust the number of parallel writers based on data volume. It handles data skew by further sub-dividing partitions into multiple shards to prevent bottlenecks during high-throughput writes. Only available with 'hash' distribution mode.
+        A subset of column names to read exclusively. If null or empty, all columns will be read.
       </td>
     </tr>
     <tr>
       <td>
-        catalog_name
+        poll_interval_seconds
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        Name of the catalog containing the table.
+        The interval at which to poll for new snapshots. Defaults to 60 seconds.
       </td>
     </tr>
     <tr>
       <td>
-        catalog_properties
+        starting_strategy
       </td>
       <td>
-        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        Properties used to set up the Iceberg catalog.
+        The source's starting strategy. Valid options are: "earliest" or "latest". Can be overriden by setting a starting snapshot or timestamp. Defaults to earliest for batch, and latest for streaming.
       </td>
     </tr>
     <tr>
       <td>
-        config_properties
+        streaming
       </td>
       <td>
-        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        Properties passed to the Hadoop Configuration.
+        Enables streaming reads, where source continuously polls for snapshots forever.
       </td>
     </tr>
     <tr>
       <td>
-        direct_write_byte_limit
+        to_snapshot
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        For a streaming pipeline, sets the limit for lifting bundles into the direct write path.
+        Reads up to this snapshot ID (inclusive).
       </td>
     </tr>
     <tr>
       <td>
-        distribution_mode
+        to_timestamp
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        Defines distribution of write data. Supported distributions:
-- none: don't shuffle rows (default)
-- hash: shuffle rows by partition key before writing data
+        Reads up to the latest snapshot (inclusive) created before this timestamp (in milliseconds).
       </td>
     </tr>
+  </table>
+</div>
+
+### `POSTGRES` Read
+
+<div class="table-container-wrapper">
+  <table class="table table-bordered">
+    <tr>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
+    </tr>
     <tr>
       <td>
-        drop
+        <strong>jdbc_url</strong>
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        A list of field names to drop from the input record before writing. Is mutually exclusive with 'keep' and 'only'.
+        Connection URL for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        keep
+        connection_properties
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        A list of field names to keep in the input record. All other fields are dropped before writing. Is mutually exclusive with 'drop' and 'only'.
+        Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
       </td>
     </tr>
     <tr>
       <td>
-        only
+        fetch_size
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
+        This method is used to override the size of the data that is going to be fetched and loaded in memory per every database call. It should ONLY be used if the default value throws memory errors.
       </td>
     </tr>
     <tr>
       <td>
-        partition_fields
+        location
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        Fields used to create a partition spec that is applied when tables are created. For a field 'foo', the available partition transforms are:
-
-- `foo`
-- `truncate(foo, N)`
-- `bucket(foo, N)`
-- `hour(foo)`
-- `day(foo)`
-- `month(foo)`
-- `year(foo)`
-- `void(foo)`
-
-For more information on partition transforms, please visit https://iceberg.apache.org/spec/#partition-transforms.
+        Name of the table to read from.
       </td>
     </tr>
     <tr>
       <td>
-        sort_fields
+        num_partitions
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        Fields used to set the table's sort order, applied when the table is created. Each entry has the form `<term> [asc|desc] [nulls first|nulls last]`, where `<term>` is a field name or one of the partition transforms (e.g. `bucket(col, 4)`, `day(ts)`). Direction defaults to ascending; null order defaults to nulls-first for ascending and nulls-last for descending. Note: this sets the table's declared sort order as metadata; it does not cause Beam to physically sort records before writing.
-For more information on sort orders, please visit https://iceberg.apache.org/spec/#sort-orders.
+        The number of partitions
       </td>
     </tr>
     <tr>
       <td>
-        table_properties
+        output_parallelization
       </td>
       <td>
-        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        Iceberg table properties to be set on the table when it is created.
-For more information on table properties, please visit https://iceberg.apache.org/docs/latest/configuration/#table-properties.
+        Whether to reshuffle the resulting PCollection so results are distributed to all workers.
       </td>
     </tr>
     <tr>
       <td>
-        triggering_frequency_seconds
+        partition_column
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        For a streaming pipeline, sets the frequency at which snapshots are produced.
+        Name of a column of numeric type that will be used for partitioning.
       </td>
     </tr>
-  </table>
-</div>
-
-### `SQLSERVER` Read
-
-<div class="table-container-wrapper">
-  <table class="table table-bordered">
-    <tr>
-      <th>Configuration</th>
-      <th>Type</th>
-      <th>Description</th>
-    </tr>
     <tr>
       <td>
-        <strong>jdbc_url</strong>
+        password
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Connection URL for the JDBC source.
+        Password for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        connection_properties
+        read_query
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
+        SQL query used to query the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        disable_auto_commit
+        username
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        Whether to disable auto commit on read. Defaults to true if not provided. The need for this config varies depending on the database platform. Informix requires this to be set to false while Postgres requires this to be set to true.
+        Username for the JDBC source.
       </td>
     </tr>
+  </table>
+</div>
+
+### `POSTGRES` Write
+
+<div class="table-container-wrapper">
+  <table class="table table-bordered">
+    <tr>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
+    </tr>
     <tr>
       <td>
-        fetch_size
+        <strong>jdbc_url</strong>
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        This method is used to override the size of the data that is going to be fetched and loaded in memory per every database call. It should ONLY be used if the default value throws memory errors.
+        Connection URL for the JDBC sink.
       </td>
     </tr>
     <tr>
       <td>
-        location
+        autosharding
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        Name of the table to read from.
+        If true, enables using a dynamically determined number of shards to write.
       </td>
     </tr>
     <tr>
       <td>
-        num_partitions
+        batch_size
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        The number of partitions
+        n/a
       </td>
     </tr>
     <tr>
       <td>
-        output_parallelization
+        connection_properties
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        Whether to reshuffle the resulting PCollection so results are distributed to all workers.
+        Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
       </td>
     </tr>
     <tr>
       <td>
-        partition_column
+        location
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Name of a column of numeric type that will be used for partitioning.
+        Name of the table to write to.
       </td>
     </tr>
     <tr>
@@ -1039,24 +1128,24 @@ For more information on table properties, please visit https://iceberg.apache.or
     </tr>
     <tr>
       <td>
-        read_query
+        username
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        SQL query used to query the JDBC source.
+        Username for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        username
+        write_statement
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Username for the JDBC source.
+        SQL query used to insert records into the JDBC sink.
       </td>
     </tr>
   </table>
@@ -1162,7 +1251,7 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `POSTGRES` Read
+### `SQLSERVER` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -1193,6 +1282,17 @@ For more information on table properties, please visit https://iceberg.apache.or
         Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
       </td>
     </tr>
+    <tr>
+      <td>
+        disable_auto_commit
+      </td>
+      <td>
+        <code style="color: orange">boolean</code>
+      </td>
+      <td>
+        Whether to disable auto commit on read. Defaults to true if not provided. The need for this config varies depending on the database platform. Informix requires this to be set to false while Postgres requires this to be set to true.
+      </td>
+    </tr>
     <tr>
       <td>
         fetch_size
@@ -1284,7 +1384,7 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `POSTGRES` Write
+### `BIGQUERY` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -1295,90 +1395,57 @@ For more information on table properties, please visit https://iceberg.apache.or
     </tr>
     <tr>
       <td>
-        <strong>jdbc_url</strong>
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        Connection URL for the JDBC sink.
-      </td>
-    </tr>
-    <tr>
-      <td>
-        autosharding
-      </td>
-      <td>
-        <code style="color: orange">boolean</code>
-      </td>
-      <td>
-        If true, enables using a dynamically determined number of shards to write.
-      </td>
-    </tr>
-    <tr>
-      <td>
-        batch_size
-      </td>
-      <td>
-        <code style="color: #f54251">int64</code>
-      </td>
-      <td>
-        n/a
-      </td>
-    </tr>
-    <tr>
-      <td>
-        connection_properties
+        kms_key
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
+        Use this Cloud KMS key to encrypt your data
       </td>
     </tr>
     <tr>
       <td>
-        location
+        query
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Name of the table to write to.
+        The SQL query to be executed to read from the BigQuery table.
       </td>
     </tr>
     <tr>
       <td>
-        password
+        row_restriction
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Password for the JDBC source.
+        Read only rows that match this filter, which must be compatible with Google standard SQL. This is not supported when reading via query.
       </td>
     </tr>
     <tr>
       <td>
-        username
+        fields
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Username for the JDBC source.
+        Read only the specified fields (columns) from a BigQuery table. Fields may not be returned in the order specified. If no value is specified, then all fields are returned. Example: "col1, col2, col3"
       </td>
     </tr>
     <tr>
       <td>
-        write_statement
+        table
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        SQL query used to insert records into the JDBC sink.
+        The fully-qualified name of the BigQuery table to read from. Format: [${PROJECT}:]${DATASET}.${TABLE}
       </td>
     </tr>
   </table>
@@ -1462,73 +1529,6 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `BIGQUERY` Read
-
-<div class="table-container-wrapper">
-  <table class="table table-bordered">
-    <tr>
-      <th>Configuration</th>
-      <th>Type</th>
-      <th>Description</th>
-    </tr>
-    <tr>
-      <td>
-        kms_key
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        Use this Cloud KMS key to encrypt your data
-      </td>
-    </tr>
-    <tr>
-      <td>
-        query
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        The SQL query to be executed to read from the BigQuery table.
-      </td>
-    </tr>
-    <tr>
-      <td>
-        row_restriction
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        Read only rows that match this filter, which must be compatible with Google standard SQL. This is not supported when reading via query.
-      </td>
-    </tr>
-    <tr>
-      <td>
-        fields
-      </td>
-      <td>
-        <code>list[<span style="color: green;">str</span>]</code>
-      </td>
-      <td>
-        Read only the specified fields (columns) from a BigQuery table. Fields may not be returned in the order specified. If no value is specified, then all fields are returned. Example: "col1, col2, col3"
-      </td>
-    </tr>
-    <tr>
-      <td>
-        table
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        The fully-qualified name of the BigQuery table to read from. Format: [${PROJECT}:]${DATASET}.${TABLE}
-      </td>
-    </tr>
-  </table>
-</div>
-
 ### `MYSQL` Read
 
 <div class="table-container-wrapper">