You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kyuubi.apache.org by ul...@apache.org on 2021/11/08 01:27:57 UTC

[incubator-kyuubi] branch master updated: [KYUUBI #1347] [DOC] Fix miscellaneous doc typos

This is an automated email from the ASF dual-hosted git repository.

ulyssesyou pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-kyuubi.git


The following commit(s) were added to refs/heads/master by this push:
     new 0f1d4ec  [KYUUBI #1347] [DOC] Fix miscellaneous doc typos
0f1d4ec is described below

commit 0f1d4ec0e067736c6976fb83535eb7d6ffa1b0c7
Author: zhenjiaguo <zh...@163.com>
AuthorDate: Mon Nov 8 09:27:37 2021 +0800

    [KYUUBI #1347] [DOC] Fix miscellaneous doc typos
    
    <!--
    Thanks for sending a pull request!
    
    Here are some tips for you:
      1. If this is your first time, please read our contributor guidelines: https://kyuubi.readthedocs.io/en/latest/community/contributions.html
      2. If the PR is related to an issue in https://github.com/apache/incubator-kyuubi/issues, add '[KYUUBI #XXXX]' in your PR title, e.g., '[KYUUBI #XXXX] Your PR title ...'.
      3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][KYUUBI #XXXX] Your PR title ...'.
    -->
    
    ### _Why are the changes needed?_
    <!--
    Please clarify why the changes are needed. For instance,
      1. If you add a feature, you can talk about the use case of it.
      2. If you fix a bug, you can clarify why it is a bug.
    -->
    
    Some spelling & grammar format fix.
    
    ### _How was this patch tested?_
    - [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible
    
    - [ ] Add screenshots for manual tests if appropriate
    
    - [ ] [Run test](https://kyuubi.readthedocs.io/en/latest/develop_tools/testing.html#running-tests) locally before make a pull request
    
    Closes #1347 from zhenjiaguo/typo-fix.
    
    Closes #1347
    
    5c20ae28 [zhenjiaguo] change serial to several
    db3fa969 [zhenjiaguo] typo fix
    
    Authored-by: zhenjiaguo <zh...@163.com>
    Signed-off-by: ulysses-you <ul...@apache.org>
---
 docs/appendix/terminology.md                |  4 ++--
 docs/client/hive_jdbc.md                    |  2 +-
 docs/community/contributions.md             |  4 ++--
 docs/community/release.md                   |  8 ++++----
 docs/deployment/high_availability_guide.md  |  4 ++--
 docs/deployment/hive_metastore.md           | 12 ++++++------
 docs/deployment/on_yarn.md                  |  6 +++---
 docs/deployment/spark/aqe.md                |  8 ++++----
 docs/deployment/spark/dynamic_allocation.md |  2 +-
 docs/develop_tools/build_document.md        |  4 ++--
 docs/develop_tools/debugging.md             |  2 +-
 docs/develop_tools/developer.md             |  4 ++--
 docs/develop_tools/distribution.md          |  4 ++--
 docs/develop_tools/testing.md               |  2 +-
 docs/monitor/logging.md                     |  2 +-
 docs/monitor/trouble_shooting.md            |  2 +-
 docs/overview/architecture.md               |  2 +-
 docs/overview/kyuubi_vs_hive.md             |  2 +-
 docs/overview/kyuubi_vs_thriftserver.md     |  2 +-
 19 files changed, 38 insertions(+), 38 deletions(-)

diff --git a/docs/appendix/terminology.md b/docs/appendix/terminology.md
index d83445a..c8b365b 100644
--- a/docs/appendix/terminology.md
+++ b/docs/appendix/terminology.md
@@ -44,7 +44,7 @@ Kyuubi is a unified multi-tenant JDBC interface for large-scale data processing
 
 Typically, there is a gap between business development and big data analytics.
 If the two are forcefully coupled, it would make the corresponding system difficult to operate and optimize.
-One the flip side, if decoupled, the values of both can be maximized.
+On the flip side, if decoupled, the values of both can be maximized.
 Business experts can stay focused on their own business development,
 while Big Data engineers can continuously optimize server-side performance and stability.
 Kyuubi combines the two seamlessly through an easy-to-use JDBC interface.
@@ -84,7 +84,7 @@ A ServerSpace is used to register servers and expose them together as a service
 ### Engine
 
 An engine handles all queries through Kyuubi servers.
-It is created one Kyuubi server and can be shared with other Kyuubi servers by registering itself to an engine namespace.
+It is created in one Kyuubi server and can be shared with other Kyuubi servers by registering itself to an engine namespace.
 All its capabilities are mainly powered by Spark SQL.
 
 _**Aliases: Query Engine / Engine Instance / e.i.**_
diff --git a/docs/client/hive_jdbc.md b/docs/client/hive_jdbc.md
index bc6b456..797c37f 100644
--- a/docs/client/hive_jdbc.md
+++ b/docs/client/hive_jdbc.md
@@ -55,7 +55,7 @@ implementation group: 'org.apache.hive', name: 'hive-jdbc', version: '2.3.8'
 ```
 
 For BI tools, please refer to [Quick Start](../quick_start/index.html) to check the guide for the BI tool used.
-If you find there is no specific document for the BI tool that you are using, don't worry, the configuration part for all BI tools are basically same.
+If you find there is no specific document for the BI tool that you are using, don't worry, the configuration part for all BI tools are basically the same.
 Also, we will appreciate if you can help us to improve the document.
 
 
diff --git a/docs/community/contributions.md b/docs/community/contributions.md
index 79a2b1b..b82c8b7 100644
--- a/docs/community/contributions.md
+++ b/docs/community/contributions.md
@@ -33,12 +33,12 @@ Before you start, please read the [Code of Conduct](http://www.apache.org/founda
 ## Prepare github environment
 If you are new to submit a Pull Request, the follow steps are helpful to you.
 
-1. An available [git](https://git-scm.com/downloads), you can run `git version` if you not sure you have
+1. An available [git](https://git-scm.com/downloads), you can run `git version` if you are not sure if you have
 2. Fork [Kyuubi](https://github.com/apache/incubator-kyuubi) on github, now you have a cloned Kyuubi repo 
 3. Clone your Kyuubi repo with cmd `git clone https://github.com/${yourname}/kyuubi.git`
 4. Create a new branch with cmd `git checkout -b test-branch`
 5. Modify the code you want
-6. Commit and push code to your Kyuubi repo with commd `git commit -am "comment"; git push test-branch test-branch`
+6. Commit and push code to your Kyuubi repo with command `git commit -am "comment"; git push test-branch test-branch`
 7. Back to [Kyuubi](https://github.com/apache/incubator-kyuubi), you can see a banner about `new pull request`
 8. Now we can create a pull request to Kyuubi
 
diff --git a/docs/community/release.md b/docs/community/release.md
index 37af4fa..3afbef5 100644
--- a/docs/community/release.md
+++ b/docs/community/release.md
@@ -42,7 +42,7 @@ The release process consists of several steps:
 
 1. Decide to release
 2. Prepare for the release
-3. Cut branch iff for __major__ release
+3. Cut branch off for __major__ release
 4. Build a release candidate
 5. Vote on the release candidate
 6. If necessary, fix any issues and go back to step 3.
@@ -78,7 +78,7 @@ signing the release and access to various release repositories.
 #### ASF authentication
 
 The environments `ASF_USERNAME` and `ASF_PASSWORD` have been used in several places and several times in the release
-process, you can either one-time set up them in `~/.bashrc` or `~/.zshrc`, or export them in terminal everytime.
+process, you can either one-time set up them in `~/.bashrc` or `~/.zshrc`, or export them in terminal every time.
 
 ```shell
 export ASF_USERNAME=<your apache username>
@@ -119,7 +119,7 @@ To export the PGP public key, using:
 gpg --armor --export 29BCC75D
 ```
 
-If you have more than one gpg key, you can specify the default key as following:
+If you have more than one gpg key, you can specify the default key as the following:
 ```
 echo 'default-key <key-fpr>' > ~/.gnupg/gpg.conf
 ```
@@ -226,7 +226,7 @@ Fork and clone [Apache Kyuubi website](https://github.com/apache/incubator-kyuub
 
 ### Create an Announcement
 
-Once everything is working create an announcement on the website and then send an e-mail to the mailing list.
+Once everything is working, create an announcement on the website and then send an e-mail to the mailing list.
 The mailing list includes: `announce@apache.org`, `dev@kyuubi.apache.org`, `user@spark.apache.org`.
 
 Enjoy an adult beverage of your choice, and congratulations on making a Kyuubi release.
diff --git a/docs/deployment/high_availability_guide.md b/docs/deployment/high_availability_guide.md
index 21a3455..3f21547 100644
--- a/docs/deployment/high_availability_guide.md
+++ b/docs/deployment/high_availability_guide.md
@@ -21,11 +21,11 @@ As an enterprise-class ad-hoc SQL query service built on top of [Apache Spark](h
 
 Running Kyuubi in HA mode is to use groups of computers or containers that support SQL query service on Kyuubi that can be reliably utilized with a minimum amount of down-time. Kyuubi operates by using [Apache ZooKeeper](https://zookeeper.apache.org/) to harness redundant service instances in groups that provide continuous service when one or more components fail.
 
-Without HA, if a server crashes, Kyuubi will be unavailable until the crashed server is fixed. With HA, this situation will be remedied by hardware/software faults auto detecting, and immediately another Kyuubi service instance will be ready to serve without requiring human intervention. 
+Without HA, if a server crashes, Kyuubi will be unavailable until the crashed server is fixed. With HA, this situation will be remedied by hardware/software faults auto-detecting, and immediately another Kyuubi service instance will be ready to serve without requiring human intervention. 
 
 ## Load Balance Mode
 
-Load balancing aims to optimize all Kyuubi service units usage, maximize throughput, minimize response time, and avoid overload of a single unit. Using multiple Kyuubi service units with load balancing instead of a single unit may increase reliability and availability through redundancy. 
+Load balancing aims to optimize all Kyuubi service unit's usage, maximize throughput, minimize response time, and avoid overload of a single unit. Using multiple Kyuubi service units with load balancing instead of a single unit may increase reliability and availability through redundancy. 
 
 ![](../imgs/ha.png)
 
diff --git a/docs/deployment/hive_metastore.md b/docs/deployment/hive_metastore.md
index 39a5ebd..94821dd 100644
--- a/docs/deployment/hive_metastore.md
+++ b/docs/deployment/hive_metastore.md
@@ -34,7 +34,7 @@ In this section, you will learn how to configure Kyuubi to interact with Hive Me
   - [Hive Metastore Administration](https://cwiki.apache.org/confluence/display/Hive/AdminManual+Metastore+Administration)
   - [Configuring the Hive Metastore for CDH](https://docs.cloudera.com/documentation/enterprise/latest/topics/cdh_ig_hive_metastore_configure.html)
 - A Spark binary distribution built with `-Phive` support
-  - Use the built in one in the Kyuubi distribution
+  - Use the built-in one in the Kyuubi distribution
   - Download from [Spark official website](https://spark.apache.org/downloads.html)
   - Build from Spark source, [Building With Hive and JDBC Support](http://spark.apache.org/docs/latest/building-spark.html#building-with-hive-and-jdbc-support)
 - A copy of Hive client configuration
@@ -99,7 +99,7 @@ Using this mode for experimental purposes only.
 
 In a real production environment, we always have a communal standalone metadata store,
 to manage the metadata of persistent relational entities, e.g. databases, tables, columns, partitions, for fast access.
-usually, Hive metastore as the defacto.
+Usually, Hive metastore as the de facto.
 
 ## Related Configurations
 
@@ -134,7 +134,7 @@ Kyuubi will take these configurations as system wide defaults for all applicatio
 
 ### Via hive-site.xml
 
-Place your copy of `hive-site.xml` into `$$SPARK_HOME/conf`,
+Place your copy of `hive-site.xml` into `$SPARK_HOME/conf`,
 every single Spark application will automatically load this config file to its classpath.
 
 This version of configuration has lower priority than those in `$KYUUBI_HOME/conf/kyuubi-defaults.conf`.
@@ -147,7 +147,7 @@ We can pass _**Hive primitives**_ or **_Spark derivatives_** directly in the JDB
 jdbc:hive2://localhost:10009/;#hive.metastore.uris=thrift://localhost:9083
 ```
 
-This will override the defaults in `$$SPARK_HOME/conf/hive-site.xml` and `$KYUUBI_HOME/conf/kyuubi-defaults.conf` for each _**user account**_
+This will override the defaults in `$SPARK_HOME/conf/hive-site.xml` and `$KYUUBI_HOME/conf/kyuubi-defaults.conf` for each _**user account**_.
 
 With this feature, end users are possible to visit different Hive metastore server instance.
 Similarly, this works for other services like HDFS, YARN too.
@@ -177,7 +177,7 @@ Most Hive configurations are final and unmodifiable in Spark at runtime, so keep
 If backward compatibility is guaranteed by Hive versioning,
 we can always use a lower version Hive metastore client to communicate with the higher version Hive metastore server.
 
-For example, Spark 3.0 was released with a builtin Hive client (2.3.7), so, ideally, the version of server should &gt;= 2.3.x.
+For example, Spark 3.0 was released with a built-in Hive client (2.3.7), so, ideally, the version of server should &gt;= 2.3.x.
 
 If you do have a legacy Hive metastore server that cannot be easily upgraded, and you may face the issue by default like this,
 
@@ -204,7 +204,7 @@ Caused by: org.apache.thrift.TApplicationException: Invalid method name: 'get_ta
 	... 93 more
 ```
 
-To prevent this problem, we can use Spark's [Interacting with Different Versions of Hive Metastore](http://spark.apache.org/docs/latest/sql-data-sources-hive-tables.html#interacting-with-different-versions-of-hive-metastore)
+To prevent this problem, we can use Spark's [Interacting with Different Versions of Hive Metastore](http://spark.apache.org/docs/latest/sql-data-sources-hive-tables.html#interacting-with-different-versions-of-hive-metastore).
 
 ## Further Readings
 
diff --git a/docs/deployment/on_yarn.md b/docs/deployment/on_yarn.md
index 89abff3..000bc26 100644
--- a/docs/deployment/on_yarn.md
+++ b/docs/deployment/on_yarn.md
@@ -41,7 +41,7 @@ When you want to deploy Kyuubi's Spark SQL engines on YARN, you'd better have co
 
 ### Environment
 
-Either `HADOOP_CONF_DIR` or `YARN_CONF_DIR` is configured and points to the Hadoop client configurations directory, usually,`$HADOOP_HOME/etc/hadoop` 
+Either `HADOOP_CONF_DIR` or `YARN_CONF_DIR` is configured and points to the Hadoop client configurations directory, usually, `$HADOOP_HOME/etc/hadoop`.
 
 If the `HADOOP_CONF_DIR` points the YARN and HDFS cluster correctly, you should be able to run the `SparkPi` example on YARN.
 ```bash
@@ -97,7 +97,7 @@ spark.executor.memory | 1g | Amount of memory to use for the executor process
 spark.executor.memoryOverhead | executorMemory * 0.10, with minimum of 384 | Amount of additional memory to be allocated per executor process. This is memory that accounts for things like VM overheads, interned strings other native overheads, etc
 
 It is recommended to use [Dynamic Allocation](http://spark.apache.org/docs/3.0.1/configuration.html#dynamic-allocation) with Kyuubi,
-since the SQL engine will be long-running for a period, execute user's queries from clients aperiodically,
+since the SQL engine will be long-running for a period, execute user's queries from clients periodically,
 and the demand for computing resources is not the same for those queries.
 It is better for Spark to release some executors when either the query is lightweight, or the SQL engine is being idled. 
 
@@ -117,5 +117,5 @@ Please refer to [Spark properties](http://spark.apache.org/docs/latest/running-o
 Kyuubi currently does not support Spark's [YARN-specific Kerberos Configuration](http://spark.apache.org/docs/3.0.1/running-on-yarn.html#kerberos),
 so `spark.kerberos.keytab` and `spark.kerberos.principal` should not use now.
 
-Instead, you can schedule a periodically `kinit` process via `crontab` task on the local machine that hosts Kyuubi server or simply use [Kyuubi Kinit](settings.html#kinit)
+Instead, you can schedule a periodically `kinit` process via `crontab` task on the local machine that hosts Kyuubi server or simply use [Kyuubi Kinit](settings.html#kinit).
  
\ No newline at end of file
diff --git a/docs/deployment/spark/aqe.md b/docs/deployment/spark/aqe.md
index 863afe2..51ab02e 100644
--- a/docs/deployment/spark/aqe.md
+++ b/docs/deployment/spark/aqe.md
@@ -34,7 +34,7 @@ which supports a variety of optimizations such as,
 - Dynamically Coalesce Shuffle Partitions
 - Dynamically Handle Skew Joins
 
-In Kyuubi, we strongly recommended that you turn on all capabilities of AQE by default for Kyuubi engines no matter on what platform you run Kyuubi and Spark.
+In Kyuubi, we strongly recommended that you turn on all capabilities of AQE by default for Kyuubi engines, no matter on what platform you run Kyuubi and Spark.
 
 ### Dynamically Switch Join Strategies
 
@@ -76,7 +76,7 @@ Without this feature, Spark itself could be a small files maker sometimes, espec
 
 1. When `spark.sql.shuffle.partitions` is set too large compared to the total output size, there comes very small or empty files after a shuffle stage.
 2. When Spark performs a series of optimized `BroadcastHash Join` and `Union` together, the final output size for each partition might be reduced by the join conditions. However, the total final output file numbers get to explode.
-3. Some pipelined jobs with selective filters to produce temporary data.
+3. Some pipeline jobs with selective filters to produce temporary data.
 4. e.t.c
 
 Reading small files leads to very small partitions or tasks. Spark tasks will have worse I/O throughput and tend to suffer more from scheduling overhead and task setup overhead.
@@ -93,7 +93,7 @@ Reading small files leads to very small partitions or tasks. Spark tasks will ha
 </em>
 </p>
 
-Combining small partitions saves resources and improves cluster throughput. Spark provides serval ways to handle small file issues, for example, adding an extra shuffle operation on the partition columns with the `distribute by` clause or using `HINT`[5]. In most scenarios, you need to have a good grasp of your data, Spark jobs, and configurations to apply these solutions case by case. Mostly, the daily used config - `spark.sql.shuffle.partitions` is data-dependent and unchangeable with  [...]
+Combining small partitions saves resources and improves cluster throughput. Spark provides several ways to handle small file issues, for example, adding an extra shuffle operation on the partition columns with the `distribute by` clause or using `HINT`[5]. In most scenarios, you need to have a good grasp of your data, Spark jobs, and configurations to apply these solutions case by case. Mostly, the daily used config - `spark.sql.shuffle.partitions` is data-dependent and unchangeable with [...]
 
 But with AQE, things become more comfortable for you as Spark will do the partition coalescing automatically.
 
@@ -141,7 +141,7 @@ But there are always exceptions. Relating these two seemingly unrelated paramete
 
 ##### How to set `spark.sql.adaptive.coalescePartitions.initialPartitionNum`?
 
-It stands for the initial number of shuffle partitions before coalescing. By default it equals to `spark.sql.shuffle.partitions(200)`. Firstly, it's better to set it explicitly rather than falling back to `spark.sql.shuffle.partitions`. Spark community suggests set a large number to it as Spark will dynamically coalesce shuffle partitions, which I cannot agree more.
+It stands for the initial number of shuffle partitions before coalescing. By default, it equals to `spark.sql.shuffle.partitions(200)`. Firstly, it's better to set it explicitly rather than falling back to `spark.sql.shuffle.partitions`. Spark community suggests set a large number to it as Spark will dynamically coalesce shuffle partitions, which I cannot agree more.
 
 ### Dynamically Handle Skew Joins
 
diff --git a/docs/deployment/spark/dynamic_allocation.md b/docs/deployment/spark/dynamic_allocation.md
index 210078d..d4ab858 100644
--- a/docs/deployment/spark/dynamic_allocation.md
+++ b/docs/deployment/spark/dynamic_allocation.md
@@ -157,7 +157,7 @@ After finish one task,  Spark Driver will schedule a new task for the executor w
 
 </div>
 
-If one executor reach the maximn timeout, it will be removed.
+If one executor reached the maximum timeout, it will be removed.
 ```properties
 spark.dynamicAllocation.executorIdleTimeout=60s
 spark.dynamicAllocation.cachedExecutorIdleTimeout=infinity
diff --git a/docs/develop_tools/build_document.md b/docs/develop_tools/build_document.md
index 5570953..bb4ab07 100644
--- a/docs/develop_tools/build_document.md
+++ b/docs/develop_tools/build_document.md
@@ -48,12 +48,12 @@ virtualenv kyuubi
 Activate it,
 
 ```bash
- source ./kyuubi/bin/activate
+source ./kyuubi/bin/activate
 ```
 
 ## Install all dependencies
 
-Install all dependencies enumerated in the `requirements.txt`
+Install all dependencies enumerated in the `requirements.txt`.
 
 ```bash
 pip install -r requirements.txt
diff --git a/docs/develop_tools/debugging.md b/docs/develop_tools/debugging.md
index f240ee6..b6b316e 100644
--- a/docs/develop_tools/debugging.md
+++ b/docs/develop_tools/debugging.md
@@ -24,7 +24,7 @@
 # Debugging Kyuubi
 
 You can use the [Java Debug Wire Protocol](https://docs.oracle.com/javase/8/docs/technotes/guides/jpda/conninv.html#Plugin) to debug Kyuubi
-with your favorite IDE tool, e.g. Intellij IDEA.
+with your favorite IDE tool, e.g. IntelliJ IDEA.
 
 ## Debugging Server
 
diff --git a/docs/develop_tools/developer.md b/docs/develop_tools/developer.md
index b6da278..38567c6 100644
--- a/docs/develop_tools/developer.md
+++ b/docs/develop_tools/developer.md
@@ -32,7 +32,7 @@ build/mvn versions:set -DgenerateBackupPoms=false
 
 ## Update Document Version
 
-Whenever Project version updates, please also update the document version at `docs/conf.py` to target the upcoming release.
+Whenever project version updates, please also update the document version at `docs/conf.py` to target the upcoming release.
 
 For example,
 
@@ -42,7 +42,7 @@ release = '1.2.0'
 
 ## Update Dependency List
 
-Kyuubi uses the `dev/dependencyList` file to indicates what upstream dependencies will actually go to the server-side classpath.
+Kyuubi uses the `dev/dependencyList` file to indicate what upstream dependencies will actually go to the server-side classpath.
 
 For Pull requests, a linter for dependency check will be automatically executed in GitHub Actions.
 
diff --git a/docs/develop_tools/distribution.md b/docs/develop_tools/distribution.md
index 02ad777..1bf8fee 100644
--- a/docs/develop_tools/distribution.md
+++ b/docs/develop_tools/distribution.md
@@ -24,7 +24,7 @@
 # Building a Runnable Distribution
 
 To create a Kyuubi distribution like those distributed by [Kyuubi Release Page](https://github.com/apache/incubator-kyuubi/releases),
-and that is laid out so as to be runnable, use `./build/dist` in the project root directory.
+and that is laid out to be runnable, use `./build/dist` in the project root directory.
 
 For more information on usage, run `./build/dist --help`
 
@@ -46,7 +46,7 @@ For instance,
 ./build/dist --name custom-name --tgz
 ```
 
-This results a Kyuubi distribution named `kyuubi-{version}-bin-custom-name.tgz` for you.
+This results in a Kyuubi distribution named `kyuubi-{version}-bin-custom-name.tgz` for you.
 
 If you are planing to deploy Kyuubi where `spark` is provided, in other word, it's not required to bundle spark binary, use 
 
diff --git a/docs/develop_tools/testing.md b/docs/develop_tools/testing.md
index cf3b742..cfceded 100644
--- a/docs/develop_tools/testing.md
+++ b/docs/develop_tools/testing.md
@@ -50,7 +50,7 @@ With Maven, you can use the -DwildcardSuites flag to run individual Scala tests:
 ./build/mvn test -Dtest=none -DwildcardSuites=org.apache.kyuubi.service.FrontendServiceSuite
 ```
 
-If you want to make a single test that need integrate with kyuubi-spark-sql-engine module, please build the package for kyuubi-spark-sql-engine module at first.
+If you want to make a single test that need to integrate with kyuubi-spark-sql-engine module, please build the package for kyuubi-spark-sql-engine module at first.
 
 You can leverage the ready-made tool for creating a binary distribution.
 
diff --git a/docs/monitor/logging.md b/docs/monitor/logging.md
index badc747..f1655e8 100644
--- a/docs/monitor/logging.md
+++ b/docs/monitor/logging.md
@@ -153,7 +153,7 @@ Operation log will show how SQL queries are executed, such as query planning, ex
 
 Operation logs can reveal directly to end-users how their queries are being executed on the server/engine-side, including some process-oriented information, and why their queries are slow or in error.
 
-For example, when you, as a end-user, use `beeline` to connect a Kyuubi server and execute query like below.
+For example, when you, as an end-user, use `beeline` to connect a Kyuubi server and execute query like below.
 
 ```shell
 bin/beeline -u 'jdbc:hive2://10.242.189.214:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=kyuubi' -n kent -e 'select * from src;'
diff --git a/docs/monitor/trouble_shooting.md b/docs/monitor/trouble_shooting.md
index 00f2748..9106841 100644
--- a/docs/monitor/trouble_shooting.md
+++ b/docs/monitor/trouble_shooting.md
@@ -200,7 +200,7 @@ Caused by: org.apache.thrift.TApplicationException: Invalid method name: 'get_ta
 
 This error means that you are using incompatible version of Hive metastore client to connect the Hive metastore server.
 
-To fix this problem you could use a compatible version for Hive client by configuring
+To fix this problem you could use a compatible version of Hive client by configuring
 `spark.sql.hive.metastore.jars` and `spark.sql.hive.metastore.version` at Spark side.
 
 
diff --git a/docs/overview/architecture.md b/docs/overview/architecture.md
index e805192..ceb7226 100644
--- a/docs/overview/architecture.md
+++ b/docs/overview/architecture.md
@@ -163,7 +163,7 @@ Let us try to break it down from top to bottom based on the above diagram.
 4. For connections from different users, the step 2 and 3 will be repeated.
    This is because in the service discovery layer,
    the namespaces used to store the address of the engine instances are isolated based on the user(by default),
-   and different users cannot access other' s instances across the namespace.
+   and different users cannot access other's instances across the namespace.
 
 ## Authentication & Authorization
 
diff --git a/docs/overview/kyuubi_vs_hive.md b/docs/overview/kyuubi_vs_hive.md
index c8c9b37..40ee913 100644
--- a/docs/overview/kyuubi_vs_hive.md
+++ b/docs/overview/kyuubi_vs_hive.md
@@ -29,7 +29,7 @@ They are both designed to provide better support for open API clients like JDBC
 ## Hive on Spark
 
 The purpose of Hive on Spark is to add Spark as a third execution backend, parallel to MR and Tez.
-Comparing to Hive on MR, it the Spark DAG will help improve the performance of Hive queries, especially those
+Comparing to Hive on MR, it's use the Spark DAG will help improve the performance of Hive queries, especially those
 have multiple reducer stages.
 
 
diff --git a/docs/overview/kyuubi_vs_thriftserver.md b/docs/overview/kyuubi_vs_thriftserver.md
index 5f28477..d50e5e3 100644
--- a/docs/overview/kyuubi_vs_thriftserver.md
+++ b/docs/overview/kyuubi_vs_thriftserver.md
@@ -182,7 +182,7 @@ The HiveServer2 is also introduced here for a more comprehensive comparison.
 |**Multi<br/>tenancy** | Yes | No | Yes|
 |**Permission<br/>Control** | SQL Standard,<br/>Fine-Grained | No | SQL Standard,<br/>Fine-Grained |
 |**Performance** | Fair | Good | Good |
-|**Client<br/>Concurrency** | High | Low | High
+|**Client<br/>Concurrency** | High | Low | High |
 |**Queuing** | for queries | None | for Engines|
 |**Resource<br/>Setting** | for queries | for pools | for Engines|
 |**Compute<br/>Resource<br/>Management** | YARN |pools| YARN, Kubernetes, etc. |