From 157923911d652fc2a926125e2fbd0b806b6e524c Mon Sep 17 00:00:00 2001 From: Sherlock113 Date: Sat, 8 May 2021 10:21:31 +0800 Subject: [PATCH] Fix some desc Signed-off-by: Sherlock113 --- content/en/docs/application-store/app-lifecycle-management.md | 2 +- content/en/docs/devops-user-guide/how-to-integrate/sonarqube.md | 2 +- content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md | 2 +- content/en/docs/faq/observability/monitoring.md | 2 +- .../high-availability-configurations/ha-configuration.md | 2 +- .../en/docs/installing-on-linux/introduction/multioverview.md | 2 +- .../application-workloads/container-image-settings.md | 2 +- .../examples/monitor-sample-web.md | 2 +- content/en/docs/quick-start/wordpress-deployment.md | 2 +- .../high-availability-configurations/ha-configuration.md | 2 +- .../zh/docs/installing-on-linux/introduction/multioverview.md | 2 +- 11 files changed, 11 insertions(+), 11 deletions(-) diff --git a/content/en/docs/application-store/app-lifecycle-management.md b/content/en/docs/application-store/app-lifecycle-management.md index 0288e491e..bbd4ba29e 100644 --- a/content/en/docs/application-store/app-lifecycle-management.md +++ b/content/en/docs/application-store/app-lifecycle-management.md @@ -92,7 +92,7 @@ You need to create two accounts first, one for ISVs (`isv`) and the other (`revi ![edit-app-information](/images/docs/appstore/application-lifecycle-management/edit-app-information.jpg) -7. Click **OK** to save your changes, then you can test this application by deploying it to Kubernetes. Click the draft version to expand the menu and select **Test Deploy**. +7. Click **OK** to save your changes, then you can test this application by deploying it to Kubernetes. Click the draft version to expand the menu and select **Test Deployment**. ![test-deployment](/images/docs/appstore/application-lifecycle-management/test-deployment.jpg) diff --git a/content/en/docs/devops-user-guide/how-to-integrate/sonarqube.md b/content/en/docs/devops-user-guide/how-to-integrate/sonarqube.md index a0eb10781..40776b491 100644 --- a/content/en/docs/devops-user-guide/how-to-integrate/sonarqube.md +++ b/content/en/docs/devops-user-guide/how-to-integrate/sonarqube.md @@ -196,7 +196,7 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir {{< notice note >}} - You may need to set up necessary port forwarding rules and open the port `30180` to access Jenkins in your security groups depending on where your instances are deployed. + You may need to set up necessary port forwarding rules and open port `30180` to access Jenkins in your security groups depending on where your instances are deployed. {{}} diff --git a/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md b/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md index f93c47c88..d186865f3 100644 --- a/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md +++ b/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md @@ -62,7 +62,7 @@ After you modified `jenkins-casc-config`, you need to reload your updated system {{< notice note >}} - You may need to set up necessary port forwarding rules and open the port `30180` to access Jenkins in your security groups depending on where your instances are deployed. + You may need to set up necessary port forwarding rules and open port `30180` to access Jenkins in your security groups depending on where your instances are deployed. {{}} diff --git a/content/en/docs/faq/observability/monitoring.md b/content/en/docs/faq/observability/monitoring.md index 5e506030d..615265417 100644 --- a/content/en/docs/faq/observability/monitoring.md +++ b/content/en/docs/faq/observability/monitoring.md @@ -100,7 +100,7 @@ Check if your computer browser's local clock is in sync with the Internet time a ## No monitoring data for both nodes and the control plane -Check your network plugin and make sure no IPPool overlap between your hosts and Pod network CIDR. It is strongly recommended that you install Kubernetes with [KubeKey](https://github.com/kubesphere/kubekey). +Check your network plugin and make sure that there is no IP Pool overlap between your hosts and Pod network CIDR. It is strongly recommended that you install Kubernetes with [KubeKey](https://github.com/kubesphere/kubekey). Chinese readers may refer to [the discussion](https://kubesphere.com.cn/forum/d/2027/16) in the KubeSphere China forum for more information. diff --git a/content/en/docs/installing-on-linux/high-availability-configurations/ha-configuration.md b/content/en/docs/installing-on-linux/high-availability-configurations/ha-configuration.md index 2294914ec..1f61c76d2 100644 --- a/content/en/docs/installing-on-linux/high-availability-configurations/ha-configuration.md +++ b/content/en/docs/installing-on-linux/high-availability-configurations/ha-configuration.md @@ -157,7 +157,7 @@ For more information about different fields in this configuration file, see [Kub - The address and port should be indented by two spaces in `config-sample.yaml`. - In most cases, you need to provide the **private IP address** of the load balancer for the field `address`. However, different cloud providers may have different configurations for load balancers. For example, if you configure a Server Load Balancer (SLB) on Alibaba Cloud, the platform assigns a public IP address to the SLB, which means you need to specify the public IP address for the field `address`. -- The domain name of the load balancer is `lb.kubesphere.local` by default for internal access. If you need to change the domain name, please uncomment and modify it. +- The domain name of the load balancer is `lb.kubesphere.local` by default for internal access. {{}} diff --git a/content/en/docs/installing-on-linux/introduction/multioverview.md b/content/en/docs/installing-on-linux/introduction/multioverview.md index 639cea1e6..260bbf999 100644 --- a/content/en/docs/installing-on-linux/introduction/multioverview.md +++ b/content/en/docs/installing-on-linux/introduction/multioverview.md @@ -248,7 +248,7 @@ List all your machines under `hosts` and add their detailed information as above #### controlPlaneEndpoint (for HA installation only) -`controlPlaneEndpoint` allows you to define an external load balancer for an HA cluster. You need to prepare and configure an external load balancer if and only if you need to install multiple master nodes. Please note that the address and port should be indented by two spaces in `config-sample.yaml`, and `address` should be VIP. See [HA Configuration](../ha-configuration/) for details. +The `controlPlaneEndpoint` is where you provide your external load balancer information for an HA cluster. You need to prepare and configure the external load balancer if and only if you need to install multiple master nodes. Please note that the address and port should be indented by two spaces in `config-sample.yaml`, and `address` should be your load balancer's IP address. See [HA Configurations](../../../installing-on-linux/high-availability-configurations/ha-configuration/) for details. #### addons diff --git a/content/en/docs/project-user-guide/application-workloads/container-image-settings.md b/content/en/docs/project-user-guide/application-workloads/container-image-settings.md index ac90cec8f..f861ce5b5 100644 --- a/content/en/docs/project-user-guide/application-workloads/container-image-settings.md +++ b/content/en/docs/project-user-guide/application-workloads/container-image-settings.md @@ -165,7 +165,7 @@ Configure environment variables for Pods in the form of key-value pairs. ![envi-var](/images/docs/project-user-guide/workloads/envi-var.jpg) - name: The name of the environment variable, specified by `env.name`. -- value: The value of the variable reference, specified by `env.value`. +- value: The value of the variable referenced, specified by `env.value`. - type: The type of environment variables. It supports customization, configuration items, keys, and variable/variable references. For more information about the command, please visit [Pod variable](https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/?spm=a2c4g.11186623.2.20.16704b3e9qHXPb). diff --git a/content/en/docs/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md b/content/en/docs/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md index a7fdd6ccd..1a49949d0 100644 --- a/content/en/docs/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md +++ b/content/en/docs/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md @@ -59,7 +59,7 @@ You need to deploy the sample web application into `test`. For demonstration pur ![deploy-sample-web-1](/images/docs/project-user-guide/custom-application-monitoring/deploy-sample-web-1.jpg) -2. Expand the menu and click **Test Deploy**. +2. Expand the menu and click **Test Deployment**. ![deploy-sample-web-2](/images/docs/project-user-guide/custom-application-monitoring/deploy-sample-web-2.jpg) diff --git a/content/en/docs/quick-start/wordpress-deployment.md b/content/en/docs/quick-start/wordpress-deployment.md index 5a34a0928..e900a8fad 100644 --- a/content/en/docs/quick-start/wordpress-deployment.md +++ b/content/en/docs/quick-start/wordpress-deployment.md @@ -68,7 +68,7 @@ Follow the same steps above to create a WordPress Secret `wordpress-secret` with ![composing-app1](/images/docs/quickstart/wordpress-deployment/composing-app1.png) -2. Enter the basic information (e.g. input `wordpress` for Application Name) and click **Next**. +2. Enter the basic information (e.g. `wordpress` for **App Name**) and click **Next**. ![basic-info1](/images/docs/quickstart/wordpress-deployment/basic-info1.png) diff --git a/content/zh/docs/installing-on-linux/high-availability-configurations/ha-configuration.md b/content/zh/docs/installing-on-linux/high-availability-configurations/ha-configuration.md index 4d53509a7..0c1c2178d 100644 --- a/content/zh/docs/installing-on-linux/high-availability-configurations/ha-configuration.md +++ b/content/zh/docs/installing-on-linux/high-availability-configurations/ha-configuration.md @@ -158,7 +158,7 @@ spec: - `config-sample.yaml` 文件中的 `address` 和 `port` 应缩进两个空格。 - 大多数情况下，您需要在负载均衡器的 `address` 字段中提供**私有 IP 地址**。但是，不同的云厂商可能对负载均衡器有不同的配置。例如，如果您在阿里云上配置服务器负载均衡器 (SLB)，平台会为 SLB 分配一个公共 IP 地址，所以您需要在 `address` 字段中指定公共 IP 地址。 -- 负载均衡器默认的内部访问域名是 `lb.kubesphere.local`。如果您需要更改域名，请去掉注释并修改域名。 +- 负载均衡器默认的内部访问域名是 `lb.kubesphere.local`。 {{}} diff --git a/content/zh/docs/installing-on-linux/introduction/multioverview.md b/content/zh/docs/installing-on-linux/introduction/multioverview.md index 41b141c69..f5ab6c8cd 100644 --- a/content/zh/docs/installing-on-linux/introduction/multioverview.md +++ b/content/zh/docs/installing-on-linux/introduction/multioverview.md @@ -250,7 +250,7 @@ spec: #### controlPlaneEndpoint（仅适用于高可用安装） -您可以用 `controlPlaneEndpoint` 为高可用集群定义外部负载均衡器。当且仅当安装多个主节点时，才需要准备和配置外部负载均衡器。请注意，`config-sample.yaml` 中的地址和端口应缩进两个空格，`address` 应为 VIP。有关详细信息，请参见[高可用配置](../../../installing-on-linux/high-availability-configurations/ha-configuration/)。 +您需要在 `controlPlaneEndpoint` 部分为高可用集群提供外部负载均衡器信息。当且仅当您安装多个主节点时，才需要准备和配置外部负载均衡器。请注意，`config-sample.yaml` 中的地址和端口应缩进两个空格，`address` 应为您的负载均衡器地址。有关详细信息，请参见[高可用配置](../../../installing-on-linux/high-availability-configurations/ha-configuration/)。 #### addons