Update the confusing statements (#468)

* Fix the wrong statement

* Fix a typo

* Fix the statement

* Fix the quotation mark

* Update the statement of tikv-ctl

* Update the MySQL related statement

* Update the statement regarding the MySQL client

op-guide/ansible-deployment.md

@@ -318,6 +318,8 @@ To deploy TiDB using a normal user account, take the following steps:
 
 ## Test the cluster
 
+> **Note:** Because TiDB is compatible with MySQL, you must use MySQL client to connect to TiDB directly.
+
 It is recommended to configure load balancing to provide uniform SQL interface.
 
 1. Connect to the TiDB cluster using the MySQL client.
@@ -467,7 +469,7 @@ Run the following command. If it returns `running`, then the NTP service is runn
 
 ```
 $ sudo systemctl status ntpd.service
-● ntpd.service - Network Time Service
+  ntpd.service - Network Time Service
    Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled)
    Active: active (running) since 一 2017-12-18 13:13:19 CST; 3s ago
 ```
@@ -728,4 +730,4 @@ Check whether the `zookeeper_addrs` configuration in `inventory.ini` is the same
 # zookeeper_addrs = "192.168.0.11:2181,192.168.0.12:2181,192.168.0.13:2181"
 # You can also append an optional chroot string to the URLs to specify the root directory for all Kafka znodes. Example:
 # zookeeper_addrs = "192.168.0.11:2181,192.168.0.12:2181,192.168.0.13:2181/kafka/123"
-```
+```

op-guide/binary-deployment.md

@@ -132,7 +132,9 @@ The key's randomart image is:
 
 TiDB provides the official binary installation package that supports Linux. For the operating system, it is recommended to use Redhat 7.3+, CentOS 7.3+ and higher versions.
 
-### Operating system: Linux (Redhat 7+, CentOS 7+)
+> **Note:** Because TiDB is compatible with MySQL, you must use MySQL client to connect to TiDB directly.
+
+### Download and extract the package on each node
 
 ```
 # Download the package.
@@ -207,19 +209,29 @@ Follow the steps below to start PD, TiKV and TiDB:
                     --log-file=pd.log
     ```
 
-2. Start TiKV on Node2, Node3 and Node4.
+2. Log in and start TiKV on other nodes: Node2, Node3 and Node4:
+
+    On Node2:
 
     ```bash
     ./bin/tikv-server --pd="192.168.199.113:2379" \
                       --addr="192.168.199.114:20160" \
                       --data-dir=tikv1 \
                       --log-file=tikv.log
+    ```
+
+    On Node3: 
 
+    ```bash
     ./bin/tikv-server --pd="192.168.199.113:2379" \
                       --addr="192.168.199.115:20160" \
                       --data-dir=tikv2 \
                       --log-file=tikv.log
+    ```
 
+    On Node4:
+    
+    ```bash
     ./bin/tikv-server --pd="192.168.199.113:2379" \
                       --addr="192.168.199.116:20160" \
                       --data-dir=tikv3 \

tools/tikv-control.md

@@ -5,8 +5,7 @@ category: tools
 
 # TiKV Control User Guide
 
-TiKV Control (`tikv-ctl`) is a command line tool of TiKV, used to manage the cluster. When you compile TiKV, the `tikv-ctl` command is also compiled at the same time. If the cluster is deployed using Ansible, the binary file also exist in the corresponding `tidb-ansible/resources/bin` directory.
-
+TiKV Control (`tikv-ctl`) is a command line tool of TiKV, used to manage the cluster. When you compile TiKV, the `tikv-ctl` command is also compiled at the same time. If the cluster is deployed using Ansible, the `tikv-ctl` binary file exists in the corresponding `tidb-ansible/resources/bin` directory. If the cluster is deployed using the binary, the `tikv-ctl` file is in the `bin` directory together with other files such as `tidb-server`, `pd-server`, `tikv-server`, etc.
 ## General options
 
 `tikv-ctl` provides two operation modes: