Initial

Author: philo-he

velox/docs/develop/TpchBenchmark.rst

@@ -45,9 +45,9 @@ responsible for both **driver** threads and I/O threads.
 Multiple Process Executor Use Case
 ----------------------------------
 
-This use case is used by Spark + `Gluten <https://github.com/oap-project/gluten>`_
+This use case is used by Spark + `Gluten <https://github.com/apache/gluten>`_
 and it differs from the Presto use case where parallelism is concerned. Spark
-uses multiple processes where each process is a Gluten+Velox query processor.
+uses multiple processes where each process is a Gluten + Velox query processor.
 Spark scales by using many Linux processes for query processing. In this case
 this means that the **drivers** are outside of Velox and Gluten and is defined
 by the Spark configuration and number of workers. Gluten takes on the role of

velox/docs/develop/memory.rst

@@ -539,7 +539,7 @@ between queries by adjusting their memory pool’s capacities accordingly (see
 
 The *MemoryArbitrator* is defined to support different implementations for
 different query systems. As for now, we implement *SharedArbitrator* for both
-Prestissimo and Prestissimo-on-Spark. `Gluten <https://github.com/apache/incubator-gluten>`_ implements its own memory
+Prestissimo and Prestissimo-on-Spark. `Gluten <https://github.com/apache/gluten>`_ implements its own memory
 arbitrator to integrate with the `Spark memory system <https://www.linkedin.com/pulse/apache-spark-memory-management-deep-dive-deepak-rajak/>`_. *SharedArbitrator*
 ensures the total allocated memory capacity is within the query memory limit
 (*MemoryManager::Options::arbitratorCapacity*), and also ensures each individual