From a7bff13583bbdb808666a4bc02489dcfae0efdee Mon Sep 17 00:00:00 2001 From: Sherlock113 Date: Mon, 7 Jun 2021 18:07:35 +0800 Subject: [PATCH] Minor wording fix Signed-off-by: Sherlock113 --- content/en/docs/installing-on-linux/introduction/kubekey.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/installing-on-linux/introduction/kubekey.md b/content/en/docs/installing-on-linux/introduction/kubekey.md index b875558ee..dbd2aeb63 100644 --- a/content/en/docs/installing-on-linux/introduction/kubekey.md +++ b/content/en/docs/installing-on-linux/introduction/kubekey.md @@ -20,7 +20,7 @@ There are several scenarios to use KubeKey: After you download KubeKey, you use an executable called `kk` to perform different operations. No matter you use it to create, scale or upgrade a cluster, you must prepare a configuration file using `kk` beforehand. This configuration file contains basic parameters of your cluster, such as host information, network configurations (CNI plugin and Pod and Service CIDR), registry mirrors, add-ons (YAML or Chart) and pluggable component options (if you install KubeSphere). For more information, see [an example configuration file](https://github.com/kubesphere/kubekey/blob/release-1.1/docs/config-example.md). -With the configuration file in place, you execute the `./kk` command with varied flags for different operations. After that, KubeKey automatically installs Docker and pulls all the necessary images for installation. When the installation is complete, you can also inspect installation logs. +With the configuration file in place, you execute the `./kk` command with varied flags for different operations. After that, KubeKey automatically installs Docker and pulls all the necessary images for installation. When the installation is complete, you can inspect installation logs. ## Why KubeKey