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 fab9e79e71a6..f4e6c7472a9b 100644
--- a/website/www/site/content/en/documentation/io/managed-io.md
+++ b/website/www/site/content/en/documentation/io/managed-io.md
@@ -58,31 +58,6 @@ and Beam SQL is invoked via the Managed API under the hood.
       <th>Read Configuration</th>
       <th>Write Configuration</th>
     </tr>
-    <tr>
-      <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>
-        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>
-        drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        filter (<code style="color: green">str</code>)<br>
-        keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
-      </td>
-      <td>
-        <strong>table</strong> (<code style="color: green">str</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>
-        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>
-        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>
       <td><strong>KAFKA</strong></td>
       <td>
@@ -111,6 +86,31 @@ and Beam SQL is invoked via the Managed API under the hood.
         schema (<code style="color: green">str</code>)<br>
       </td>
     </tr>
+    <tr>
+      <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>
+        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>
+        drop (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        filter (<code style="color: green">str</code>)<br>
+        keep (<code>list[<span style="color: green;">str</span>]</code>)<br>
+      </td>
+      <td>
+        <strong>table</strong> (<code style="color: green">str</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>
+        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>
+        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>
       <td><strong>ICEBERG_CDC</strong></td>
       <td>
@@ -134,9 +134,10 @@ and Beam SQL is invoked via the Managed API under the hood.
       </td>
     </tr>
     <tr>
-      <td><strong>SQLSERVER</strong></td>
+      <td><strong>MYSQL</strong></td>
       <td>
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
+        connection_init_sql (<code>list[<span style="color: green;">str</span>]</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>
@@ -152,6 +153,7 @@ and Beam SQL is invoked via the Managed API under the hood.
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
         autosharding (<code style="color: orange">boolean</code>)<br>
         batch_size (<code style="color: #f54251">int64</code>)<br>
+        connection_init_sql (<code>list[<span style="color: green;">str</span>]</code>)<br>
         connection_properties (<code style="color: green">str</code>)<br>
         location (<code style="color: green">str</code>)<br>
         password (<code style="color: green">str</code>)<br>
@@ -160,10 +162,27 @@ and Beam SQL is invoked via the Managed API under the hood.
       </td>
     </tr>
     <tr>
-      <td><strong>MYSQL</strong></td>
+      <td><strong>BIGQUERY</strong></td>
+      <td>
+        kms_key (<code style="color: green">str</code>)<br>
+        query (<code style="color: green">str</code>)<br>
+        row_restriction (<code style="color: green">str</code>)<br>
+        fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
+        table (<code style="color: green">str</code>)<br>
+      </td>
+      <td>
+        <strong>table</strong> (<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>
+        kms_key (<code style="color: green">str</code>)<br>
+        only (<code style="color: green">str</code>)<br>
+        triggering_frequency_seconds (<code style="color: #f54251">int64</code>)<br>
+      </td>
+    </tr>
+    <tr>
+      <td><strong>SQLSERVER</strong></td>
       <td>
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
-        connection_init_sql (<code>list[<span style="color: green;">str</span>]</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>
@@ -179,7 +198,6 @@ and Beam SQL is invoked via the Managed API under the hood.
         <strong>jdbc_url</strong> (<code style="color: green">str</code>)<br>
         autosharding (<code style="color: orange">boolean</code>)<br>
         batch_size (<code style="color: #f54251">int64</code>)<br>
-        connection_init_sql (<code>list[<span style="color: green;">str</span>]</code>)<br>
         connection_properties (<code style="color: green">str</code>)<br>
         location (<code style="color: green">str</code>)<br>
         password (<code style="color: green">str</code>)<br>
@@ -187,24 +205,6 @@ and Beam SQL is invoked via the Managed API under the hood.
         write_statement (<code style="color: green">str</code>)<br>
       </td>
     </tr>
-    <tr>
-      <td><strong>BIGQUERY</strong></td>
-      <td>
-        kms_key (<code style="color: green">str</code>)<br>
-        query (<code style="color: green">str</code>)<br>
-        row_restriction (<code style="color: green">str</code>)<br>
-        fields (<code>list[<span style="color: green;">str</span>]</code>)<br>
-        table (<code style="color: green">str</code>)<br>
-      </td>
-      <td>
-        <strong>table</strong> (<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>
-        kms_key (<code style="color: green">str</code>)<br>
-        only (<code style="color: green">str</code>)<br>
-        triggering_frequency_seconds (<code style="color: #f54251">int64</code>)<br>
-      </td>
-    </tr>
     <tr>
       <td><strong>POSTGRES</strong></td>
       <td>
@@ -235,7 +235,7 @@ and Beam SQL is invoked via the Managed API under the hood.
 
 ## Configuration Details
 
-### `ICEBERG` Write
+### `KAFKA` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -246,141 +246,162 @@ and Beam SQL is invoked via the Managed API under the hood.
     </tr>
     <tr>
       <td>
-        <strong>table</strong>
+        <strong>bootstrap_servers</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`.
+        A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. This list should be in the form `host1:port1,host2:port2,...`
       </td>
     </tr>
     <tr>
       <td>
-        catalog_name
+        <strong>topic</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Name of the catalog containing the table.
+        n/a
       </td>
     </tr>
     <tr>
       <td>
-        catalog_properties
+        allow_duplicates
       </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 used to set up the Iceberg catalog.
+        If the Kafka read allows duplicates.
       </td>
     </tr>
     <tr>
       <td>
-        config_properties
+        confluent_schema_registry_subject
       </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 passed to the Hadoop Configuration.
+        n/a
       </td>
     </tr>
     <tr>
       <td>
-        direct_write_byte_limit
+        confluent_schema_registry_url
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        For a streaming pipeline, sets the limit for lifting bundles into the direct write path.
+        n/a
       </td>
     </tr>
     <tr>
       <td>
-        drop
+        consumer_config_updates
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        A list of field names to drop from the input record before writing. Is mutually exclusive with 'keep' and 'only'.
+        A list of key-value pairs that act as configuration parameters for Kafka consumers. Most of these configurations will not be needed, but if you need to customize your Kafka consumer, you may use this. See a detailed list: https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html
       </td>
     </tr>
     <tr>
       <td>
-        keep
+        file_descriptor_path
       </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'.
+        The path to the Protocol Buffer File Descriptor Set file. This file is used for schema definition and message serialization.
       </td>
     </tr>
     <tr>
       <td>
-        only
+        format
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
+        The encoding format for the data stored in Kafka. Valid options are: RAW,STRING,AVRO,JSON,PROTO
       </td>
     </tr>
     <tr>
       <td>
-        partition_fields
+        message_name
       </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.
+        The name of the Protocol Buffer message to be used for schema extraction and data conversion.
       </td>
     </tr>
     <tr>
       <td>
-        table_properties
+        offset_deduplication
       </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.
+        If the redistribute is using offset deduplication mode.
       </td>
     </tr>
     <tr>
       <td>
-        triggering_frequency_seconds
+        redistribute_by_record_key
+      </td>
+      <td>
+        <code style="color: orange">boolean</code>
+      </td>
+      <td>
+        If the redistribute keys by the Kafka record key.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        redistribute_num_keys
       </td>
       <td>
         <code style="color: #f54251">int32</code>
       </td>
       <td>
-        For a streaming pipeline, sets the frequency at which snapshots are produced.
+        The number of keys for redistributing Kafka inputs.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        redistributed
+      </td>
+      <td>
+        <code style="color: orange">boolean</code>
+      </td>
+      <td>
+        If the Kafka read should be redistributed.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        schema
+      </td>
+      <td>
+        <code style="color: green">str</code>
+      </td>
+      <td>
+        The schema in which the data is encoded in the Kafka topic. For AVRO data, this is a schema defined with AVRO schema syntax (https://avro.apache.org/docs/1.10.2/spec.html#schemas). For JSON data, this is a schema defined with JSON-schema syntax (https://json-schema.org/). If a URL to Confluent Schema Registry is provided, then this field is ignored, and the schema is fetched from Confluent Schema Registry.
       </td>
     </tr>
   </table>
 </div>
 
-### `ICEBERG` Read
+### `KAFKA` Write
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -391,85 +412,85 @@ For more information on table properties, please visit https://iceberg.apache.or
     </tr>
     <tr>
       <td>
-        <strong>table</strong>
+        <strong>bootstrap_servers</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Identifier of the Iceberg table.
+        A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. | Format: host1:port1,host2:port2,...
       </td>
     </tr>
     <tr>
       <td>
-        catalog_name
+        <strong>format</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Name of the catalog containing the table.
+        The encoding format for the data stored in Kafka. Valid options are: RAW,JSON,AVRO,PROTO
       </td>
     </tr>
     <tr>
       <td>
-        catalog_properties
+        <strong>topic</strong>
       </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.
+        n/a
       </td>
     </tr>
     <tr>
       <td>
-        config_properties
+        file_descriptor_path
       </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 passed to the Hadoop Configuration.
+        The path to the Protocol Buffer File Descriptor Set file. This file is used for schema definition and message serialization.
       </td>
     </tr>
     <tr>
       <td>
-        drop
+        message_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 exclude from reading. If null or empty, all columns will be read.
+        The name of the Protocol Buffer message to be used for schema extraction and data conversion.
       </td>
     </tr>
     <tr>
       <td>
-        filter
+        producer_config_updates
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        SQL-like predicate to filter data at scan time. Example: "id > 5 AND status = 'ACTIVE'". Uses Apache Calcite syntax: https://calcite.apache.org/docs/reference.html
+        A list of key-value pairs that act as configuration parameters for Kafka producers. Most of these configurations will not be needed, but if you need to customize your Kafka producer, you may use this. See a detailed list: https://docs.confluent.io/platform/current/installation/configuration/producer-configs.html
       </td>
     </tr>
     <tr>
       <td>
-        keep
+        schema
       </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.
+        n/a
       </td>
     </tr>
   </table>
 </div>
 
-### `KAFKA` Read
+### `ICEBERG` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -480,245 +501,224 @@ For more information on table properties, please visit https://iceberg.apache.or
     </tr>
     <tr>
       <td>
-        <strong>bootstrap_servers</strong>
-      </td>
-      <td>
-        <code style="color: green">str</code>
-      </td>
-      <td>
-        A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. This list should be in the form `host1:port1,host2:port2,...`
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <strong>topic</strong>
+        <strong>table</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        n/a
-      </td>
-    </tr>
-    <tr>
-      <td>
-        allow_duplicates
-      </td>
-      <td>
-        <code style="color: orange">boolean</code>
-      </td>
-      <td>
-        If the Kafka read allows duplicates.
+        Identifier of the Iceberg table.
       </td>
     </tr>
     <tr>
       <td>
-        confluent_schema_registry_subject
+        catalog_name
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        n/a
+        Name of the catalog containing the table.
       </td>
     </tr>
     <tr>
       <td>
-        confluent_schema_registry_url
+        catalog_properties
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        n/a
+        Properties used to set up the Iceberg catalog.
       </td>
     </tr>
     <tr>
       <td>
-        consumer_config_updates
+        config_properties
       </td>
       <td>
         <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        A list of key-value pairs that act as configuration parameters for Kafka consumers. Most of these configurations will not be needed, but if you need to customize your Kafka consumer, you may use this. See a detailed list: https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html
+        Properties passed to the Hadoop Configuration.
       </td>
     </tr>
     <tr>
       <td>
-        file_descriptor_path
+        drop
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        The path to the Protocol Buffer File Descriptor Set file. This file is used for schema definition and message serialization.
+        A subset of column names to exclude from reading. If null or empty, all columns will be read.
       </td>
     </tr>
     <tr>
       <td>
-        format
+        filter
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The encoding format for the data stored in Kafka. Valid options are: RAW,STRING,AVRO,JSON,PROTO
+        SQL-like predicate to filter data at scan time. Example: "id > 5 AND status = 'ACTIVE'". Uses Apache Calcite syntax: https://calcite.apache.org/docs/reference.html
       </td>
     </tr>
     <tr>
       <td>
-        message_name
+        keep
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        The name of the Protocol Buffer message to be used for schema extraction and data conversion.
+        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>
-      <td>
-        offset_deduplication
-      </td>
-      <td>
-        <code style="color: orange">boolean</code>
-      </td>
-      <td>
-        If the redistribute is using offset deduplication mode.
-      </td>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
     </tr>
     <tr>
       <td>
-        redistribute_by_record_key
+        <strong>table</strong>
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        If the redistribute keys by the Kafka record key.
+        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>
-        redistribute_num_keys
+        catalog_name
       </td>
       <td>
-        <code style="color: #f54251">int32</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        The number of keys for redistributing Kafka inputs.
+        Name of the catalog containing the table.
       </td>
     </tr>
     <tr>
       <td>
-        redistributed
+        catalog_properties
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        If the Kafka read should be redistributed.
+        Properties used to set up the Iceberg catalog.
       </td>
     </tr>
     <tr>
       <td>
-        schema
+        config_properties
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        The schema in which the data is encoded in the Kafka topic. For AVRO data, this is a schema defined with AVRO schema syntax (https://avro.apache.org/docs/1.10.2/spec.html#schemas). For JSON data, this is a schema defined with JSON-schema syntax (https://json-schema.org/). If a URL to Confluent Schema Registry is provided, then this field is ignored, and the schema is fetched from Confluent Schema Registry.
+        Properties passed to the Hadoop Configuration.
       </td>
     </tr>
-  </table>
-</div>
-
-### `KAFKA` 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>bootstrap_servers</strong>
+        direct_write_byte_limit
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. | Format: host1:port1,host2:port2,...
+        For a streaming pipeline, sets the limit for lifting bundles into the direct write path.
       </td>
     </tr>
     <tr>
       <td>
-        <strong>format</strong>
+        drop
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        The encoding format for the data stored in Kafka. Valid options are: RAW,JSON,AVRO,PROTO
+        A list of field names to drop from the input record before writing. Is mutually exclusive with 'keep' and 'only'.
       </td>
     </tr>
     <tr>
       <td>
-        <strong>topic</strong>
+        keep
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        n/a
+        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>
-        file_descriptor_path
+        only
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The path to the Protocol Buffer File Descriptor Set file. This file is used for schema definition and message serialization.
+        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
       </td>
     </tr>
     <tr>
       <td>
-        message_name
+        partition_fields
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        The name of the Protocol Buffer message to be used for schema extraction and data conversion.
+        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>
-        producer_config_updates
+        table_properties
       </td>
       <td>
         <code>map[<span style="color: green;">str</span>, <span style="color: green;">str</span>]</code>
       </td>
       <td>
-        A list of key-value pairs that act as configuration parameters for Kafka producers. Most of these configurations will not be needed, but if you need to customize your Kafka producer, you may use this. See a detailed list: https://docs.confluent.io/platform/current/installation/configuration/producer-configs.html
+        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>
-        schema
+        triggering_frequency_seconds
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        n/a
+        For a streaming pipeline, sets the frequency at which snapshots are produced.
       </td>
     </tr>
   </table>
@@ -890,7 +890,7 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `SQLSERVER` Write
+### `MYSQL` Write
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -932,6 +932,17 @@ For more information on table properties, please visit https://iceberg.apache.or
         n/a
       </td>
     </tr>
+    <tr>
+      <td>
+        connection_init_sql
+      </td>
+      <td>
+        <code>list[<span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Sets the connection init sql statements used by the Driver. Only MySQL and MariaDB support this.
+      </td>
+    </tr>
     <tr>
       <td>
         connection_properties
@@ -990,7 +1001,7 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `SQLSERVER` Read
+### `MYSQL` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -1010,6 +1021,17 @@ For more information on table properties, please visit https://iceberg.apache.or
         Connection URL for the JDBC source.
       </td>
     </tr>
+    <tr>
+      <td>
+        connection_init_sql
+      </td>
+      <td>
+        <code>list[<span style="color: green;">str</span>]</code>
+      </td>
+      <td>
+        Sets the connection init sql statements used by the Driver. Only MySQL and MariaDB support this.
+      </td>
+    </tr>
     <tr>
       <td>
         connection_properties
@@ -1123,7 +1145,7 @@ For more information on table properties, please visit https://iceberg.apache.or
   </table>
 </div>
 
-### `MYSQL` Read
+### `BIGQUERY` Write
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -1134,140 +1156,141 @@ For more information on table properties, please visit https://iceberg.apache.or
     </tr>
     <tr>
       <td>
-        <strong>jdbc_url</strong>
+        <strong>table</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Connection URL for the JDBC source.
+        The bigquery table to write to. Format: [${PROJECT}:]${DATASET}.${TABLE}
       </td>
     </tr>
     <tr>
       <td>
-        connection_init_sql
+        drop
       </td>
       <td>
         <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        Sets the connection init sql statements used by the Driver. Only MySQL and MariaDB support this.
+        A list of field names to drop from the input record before writing. Is mutually exclusive with 'keep' and 'only'.
       </td>
     </tr>
     <tr>
       <td>
-        connection_properties
+        keep
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</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;".
+        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>
-        disable_auto_commit
+        kms_key
       </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.
+        Use this Cloud KMS key to encrypt your data
       </td>
     </tr>
     <tr>
       <td>
-        fetch_size
+        only
       </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.
+        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
       </td>
     </tr>
     <tr>
       <td>
-        location
+        triggering_frequency_seconds
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int64</code>
       </td>
       <td>
-        Name of the table to read from.
+        Determines how often to 'commit' progress into BigQuery. Default is every 5 seconds.
       </td>
     </tr>
+  </table>
+</div>
+
+### `BIGQUERY` Read
+
+<div class="table-container-wrapper">
+  <table class="table table-bordered">
     <tr>
-      <td>
-        num_partitions
-      </td>
-      <td>
-        <code style="color: #f54251">int32</code>
-      </td>
-      <td>
-        The number of partitions
-      </td>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
     </tr>
     <tr>
       <td>
-        output_parallelization
+        kms_key
       </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.
+        Use this Cloud KMS key to encrypt your data
       </td>
     </tr>
     <tr>
       <td>
-        partition_column
+        query
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Name of a column of numeric type that will be used for partitioning.
+        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>
-        read_query
+        fields
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code>list[<span style="color: green;">str</span>]</code>
       </td>
       <td>
-        SQL query used to query 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>
-        username
+        table
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Username for the JDBC source.
+        The fully-qualified name of the BigQuery table to read from. Format: [${PROJECT}:]${DATASET}.${TABLE}
       </td>
     </tr>
   </table>
 </div>
 
-### `MYSQL` Write
+### `SQLSERVER` Read
 
 <div class="table-container-wrapper">
   <table class="table table-bordered">
@@ -1284,240 +1307,217 @@ For more information on table properties, please visit https://iceberg.apache.or
         <code style="color: green">str</code>
       </td>
       <td>
-        Connection URL for the JDBC sink.
+        Connection URL for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        autosharding
+        connection_properties
       </td>
       <td>
-        <code style="color: orange">boolean</code>
+        <code style="color: green">str</code>
       </td>
       <td>
-        If true, enables using a dynamically determined number of shards to write.
+        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>
-        batch_size
+        disable_auto_commit
       </td>
       <td>
-        <code style="color: #f54251">int64</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        n/a
+        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>
-        connection_init_sql
+        fetch_size
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        Sets the connection init sql statements used by the Driver. Only MySQL and MariaDB support this.
+        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>
-        connection_properties
+        location
       </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;".
+        Name of the table to read from.
       </td>
     </tr>
     <tr>
       <td>
-        location
+        num_partitions
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: #f54251">int32</code>
       </td>
       <td>
-        Name of the table to write to.
+        The number of partitions
       </td>
     </tr>
     <tr>
       <td>
-        password
+        output_parallelization
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        Password for the JDBC source.
+        Whether to reshuffle the resulting PCollection so results are distributed to all workers.
       </td>
     </tr>
     <tr>
       <td>
-        username
+        partition_column
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Username for the JDBC source.
+        Name of a column of numeric type that will be used for partitioning.
       </td>
     </tr>
     <tr>
       <td>
-        write_statement
+        password
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        SQL query used to insert records into the JDBC sink.
+        Password for the JDBC source.
       </td>
     </tr>
-  </table>
-</div>
-
-### `BIGQUERY` 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>
+        read_query
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The bigquery table to write to. Format: [${PROJECT}:]${DATASET}.${TABLE}
+        SQL query used to query the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        drop
+        username
       </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'.
+        Username for the JDBC source.
       </td>
     </tr>
+  </table>
+</div>
+
+### `SQLSERVER` Write
+
+<div class="table-container-wrapper">
+  <table class="table table-bordered">
     <tr>
-      <td>
-        keep
-      </td>
-      <td>
-        <code>list[<span style="color: green;">str</span>]</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'.
-      </td>
+      <th>Configuration</th>
+      <th>Type</th>
+      <th>Description</th>
     </tr>
     <tr>
       <td>
-        kms_key
+        <strong>jdbc_url</strong>
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Use this Cloud KMS key to encrypt your data
+        Connection URL for the JDBC sink.
       </td>
     </tr>
     <tr>
       <td>
-        only
+        autosharding
       </td>
       <td>
-        <code style="color: green">str</code>
+        <code style="color: orange">boolean</code>
       </td>
       <td>
-        The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
+        If true, enables using a dynamically determined number of shards to write.
       </td>
     </tr>
     <tr>
       <td>
-        triggering_frequency_seconds
+        batch_size
       </td>
       <td>
         <code style="color: #f54251">int64</code>
       </td>
       <td>
-        Determines how often to 'commit' progress into BigQuery. Default is every 5 seconds.
+        n/a
       </td>
     </tr>
-  </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
+        connection_properties
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        Use this Cloud KMS key to encrypt your data
+        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>
-        query
+        location
       </td>
       <td>
         <code style="color: green">str</code>
       </td>
       <td>
-        The SQL query to be executed to read from the BigQuery table.
+        Name of the table to write to.
       </td>
     </tr>
     <tr>
       <td>
-        row_restriction
+        password
       </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.
+        Password for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        fields
+        username
       </td>
       <td>
-        <code>list[<span style="color: green;">str</span>]</code>
+        <code style="color: green">str</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"
+        Username for the JDBC source.
       </td>
     </tr>
     <tr>
       <td>
-        table
+        write_statement
       </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}
+        SQL query used to insert records into the JDBC sink.
       </td>
     </tr>
   </table>