fix_whitespace_formatting

Author: coderfender

docs/docs/spark-procedures.md

@@ -407,6 +407,7 @@ Iceberg can compact data files in parallel using Spark with the `rewriteDataFile
 | `delete-ratio-threshold` | 0.3 | Minimum deletion ratio that needs to be associated with a data file for it to be considered for rewriting |
 | `output-spec-id` | current partition spec id | Identifier of the output partition spec. Data will be reorganized during the rewrite to align with the output partitioning. |
 | `remove-dangling-deletes` | false | Remove dangling position and equality deletes after rewriting. A delete file is considered dangling if it does not apply to any live data files. Enabling this will generate an additional commit for the removal. |
+| `max-files-to-rewrite` | null | This option sets an upper limit on the number of files eligible for rewrite operation. It can be useful for improving job stability, particularly when dealing with a large number of files. If this option is not specified, all files will be considered for rewriting |
 
 !!! info
     Dangling delete files are removed based solely on data sequence numbers. This action does not apply to global 
@@ -533,7 +534,6 @@ Dangling deletes are always filtered out during rewriting.
 | `min-input-files` | 5 | Any file group exceeding this number of files will be rewritten regardless of other criteria |
 | `rewrite-all` | false | Force rewriting of all provided files overriding other options |
 | `max-file-group-size-bytes` | 107374182400 (100GB) | Largest amount of data that should be rewritten in a single file group. The entire rewrite operation is broken down into pieces based on partitioning and within partitions based on size into file-groups.  This helps with breaking down the rewriting of very large partitions which may not be rewritable otherwise due to the resource constraints of the cluster. |
-| `max-files-to-rewrite` | null | This option sets an upper limit on the number of files eligible for rewrite operation. It can be useful for improving job stability, particularly when dealing with a large number of files. If this option is not specified, all files will be considered for rewriting |
 
 #### Output
 
@@ -867,11 +867,11 @@ that provide additional information about the changes being tracked. These colum
 Here is an example of corresponding results. It shows that the first snapshot inserted 2 records, and the
 second snapshot deleted 1 record. 
 
-|  id   | name    |_change_type |   _change_ordinal | _commit_snapshot_id |
+|  id	| name	  |_change_type |	_change_ordinal	| _commit_snapshot_id |
 |---|--------|---|---|---|
-|1  | Alice  |INSERT    |0  |5390529835796506035|
-|2  | Bob      |INSERT  |0  |5390529835796506035|
-|1  | Alice  |DELETE    |1  |8764748981452218370|
+|1	| Alice	 |INSERT	|0	|5390529835796506035|
+|2	| Bob	   |INSERT	|0	|5390529835796506035|
+|1	| Alice  |DELETE	|1	|8764748981452218370|
 
 #### Net Changes
 
@@ -887,9 +887,9 @@ CALL spark_catalog.system.create_changelog_view(
 
 With the net changes, the above changelog view only contains the following row since Alice was inserted in the first snapshot and deleted in the second snapshot.
 
-|  id   | name    |_change_type |   _change_ordinal | _commit_snapshot_id |
+|  id	| name	  |_change_type |	_change_ordinal	| _commit_snapshot_id |
 |---|--------|---|---|---|
-|2  | Bob      |INSERT  |0  |5390529835796506035|
+|2	| Bob	   |INSERT	|0	|5390529835796506035|
 
 #### Carry-over Rows
 
@@ -1056,4 +1056,4 @@ metadata files and data files to the target location.
 Lastly, the [register_table](#register_table) procedure can be used to register the copied table in the target location with a catalog.
 
 !!! warning
-    Iceberg tables with partition statistics files are not currently supported for path rewrite.
+    Iceberg tables with partition statistics files are not currently supported for path rewrite.