fix main

Signed-off-by: Ruihang Xia <waynestxia@gmail.com>

Author: waynexia

dev/update_config_docs.sh

@@ -167,7 +167,7 @@ In conclusion, for queries under a very tight memory limit, it's recommended to
 set `target_partitions` and `batch_size` to smaller values.
 
 ```sql
--- Query still gets paralleized, but each partition will have more memory to use
+-- Query still gets parallelized, but each partition will have more memory to use
 SET datafusion.execution.target_partitions = 4;
 -- Smaller than the default '8192', while still keep the benefit of vectorized execution
 SET datafusion.execution.batch_size = 1024;

docs/source/library-user-guide/upgrading.md

@@ -152,7 +152,7 @@ for more details.
 
 ### Added `ExecutionPlan::reset_state`
 
-In order to fix a bug in DataFusion `49.0.0` where dynamic filters (currently only generated in the precense of a query such as `ORDER BY ... LIMIT ...`)
+In order to fix a bug in DataFusion `49.0.0` where dynamic filters (currently only generated in the presence of a query such as `ORDER BY ... LIMIT ...`)
 produced incorrect results in recursive queries, a new method `reset_state` has been added to the `ExecutionPlan` trait.
 
 Any `ExecutionPlan` that needs to maintain internal state or references to other nodes in the execution plan tree should implement this method to reset that state.

docs/source/user-guide/configs.md

@@ -239,7 +239,7 @@ In conclusion, for queries under a very tight memory limit, it's recommended to
 set `target_partitions` and `batch_size` to smaller values.
 
 ```sql
--- Query still gets paralleized, but each partition will have more memory to use
+-- Query still gets parallelized, but each partition will have more memory to use
 SET datafusion.execution.target_partitions = 4;
 -- Smaller than the default '8192', while still keep the benefit of vectorized execution
 SET datafusion.execution.batch_size = 1024;