diff --git a/README.md b/README.md
index 42e5b7a..aa02cf6 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,11 @@
 
 Kubeye aims to find various problems on Kubernetes, such as application misconfiguration, cluster components unhealthy and node problems(using [Node-Problem-Detector](https://github.com/kubernetes/node-problem-detector)). Besides predefined rules, it also supports custom defined rules.
 
+## Architecture
+Kubeye gets cluster diagnostic data by calling the Kubernetes API, by regular matching of key error messages in logs and by rule matching of container syntax. See Architecture for details.
+
+![Image](./docs/Kubeye-Architecture.jpg?raw=true)
+
 ## How to use
 -  Install Kubeye on your machine 
     - Download pre built executables from [Releases](https://github.com/kubesphere/kubeye/releases).
@@ -161,4 +166,4 @@ kube-system   Warning     calico-kube-controllers   Deployment   2020-11-27T17:1
 kube-system   Warning     nodelocaldns              DaemonSet    2020-11-27T17:18:31+08:00   [runAsPrivileged cpuLimitsMissing]
 default       Warning     nginx                     Deployment   2020-11-27T17:18:31+08:00   [livenessProbeMissing cpuLimitsMissing]
 kube-system   Warning     coredns                   Deployment   2020-11-27T17:18:31+08:00   [cpuLimitsMissing]
-```
\ No newline at end of file
+```
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 721c688..9a90ce2 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -10,12 +10,12 @@ Node not ready. The error log shows the following error message:
 ##### Cause: 
 Docker service exception
 ##### Resolving the problem:
-1. On the corresponding node, see if the docker service is Running or exist?, such as the following command:  
+1. Go to the corresponding node and check if the docker service is running or exist by the following command:  
 `systemctl status docker`
-2. If it's not running, start it, such as the following command:  
+2. If it's not running, start the docker service with the following command:  
 `systemctl start docker`
-3. If it's not exist, it means that the corresponding node is reset and need to add node or delete node. prefer to [add/delete](https://github.com/kubesphere/kubekey#add-nodes)
-4. If start fails, you can open two terminals on the same machine, one with the command view docker logs and the other with start docker command. such as the following command:   
+3. If does not exist, it means that the corresponding node is reset and need to be added or deleted. prefer to [add/delete](https://github.com/kubesphere/kubekey#add-nodes)
+4. If start fails, open two terminals on the same machine, one with the command view docker logs and the other with start docker command. such as the following command:   
 one terminal: `journalctl -u docker -f`, other terminal: `systemctl start docker`
 
 ## Pod-level issues
diff --git a/docs/Kubeye-Architecture.jpg b/docs/Kubeye-Architecture.jpg
new file mode 100644
index 0000000..d41d78c
Binary files /dev/null and b/docs/Kubeye-Architecture.jpg differ