address review comments

apache · Nov 17, 2024 · 351930f · 351930f
1 parent d486cf3
commit 351930f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -19,7 +19,7 @@
 
 # Ballista: Making DataFusion Applications Distributed
 
-Ballista is a library which makes [Apache DataFusion](https://github.com/apache/datafusion) applications distributed.
+Ballista is a distributed execution engine which makes [Apache DataFusion](https://github.com/apache/datafusion) applications distributed.
 
 Existing DataFusion application:
 
@@ -74,7 +74,8 @@ If you are looking for documentation or more examples, please refer to the [Ball
 
 A Ballista cluster consists of one or more scheduler processes and one or more executor processes. These processes
 can be run as native binaries and are also available as Docker Images, which can be easily deployed with
-[Docker Compose](https://datafusion.apache.org/ballista/user-guide/deployment/docker-compose.html).
+[Docker Compose](https://datafusion.apache.org/ballista/user-guide/deployment/docker-compose.html) or
+[Kubernetes](https://datafusion.apache.org/ballista/user-guide/deployment/kubernetes.html).
 
 The following diagram shows the interaction between clients and the scheduler for submitting jobs, and the interaction
 between the executor(s) and the scheduler for fetching tasks and reporting task status.

diff --git a/docs/source/user-guide/configs.md b/docs/source/user-guide/configs.md
@@ -21,7 +21,7 @@
 
 ## Ballista Configuration Settings
 
-Configuring Ballista is like configuring DataFusion. Apart from a few Ballista specific configurations all others are the same like DataFusion.
+Configuring Ballista is quite similar to configuring DataFusion. Most settings are identical, with only a few configurations specific to Ballista.
 
 _Example: Specifying configuration options when creating a context_