diff options
| author | Xiang Dai <long0dai@foxmail.com> | 2020-06-12 10:48:38 +0800 |
|---|---|---|
| committer | Xiang Dai <long0dai@foxmail.com> | 2020-06-12 10:48:38 +0800 |
| commit | 41c2e2c475f19dd3bc66faa334b5254b822bbd34 (patch) | |
| tree | e24765b43801db4e68bc1978d86d64ec3c997145 /docs | |
| parent | Merge pull request #1795 from daixiang0/keadm (diff) | |
| download | kubeedge-41c2e2c475f19dd3bc66faa334b5254b822bbd34.tar.gz | |
Docs: fix spell issue
Signed-off-by: Xiang Dai <long0dai@foxmail.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/contributing/contribute.md | 2 | ||||
| -rw-r--r-- | docs/governance.md | 2 | ||||
| -rw-r--r-- | docs/proposals/cloudcore-ha-design.md | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/contributing/contribute.md b/docs/contributing/contribute.md index 418265a67..a09910f25 100644 --- a/docs/contributing/contribute.md +++ b/docs/contributing/contribute.md @@ -12,7 +12,7 @@ The goal of the community is to develop a cloud native edge computing platform b - See [Community Membership](community.md) for a list of various community roles. With gradual contributions, one can move up in the chain. -## Prepartion +## Preparation - Choose matched [golang](https://golang.org/dl) version and install: diff --git a/docs/governance.md b/docs/governance.md index 5ca7f5cc7..8d81e07f4 100644 --- a/docs/governance.md +++ b/docs/governance.md @@ -1,6 +1,6 @@ # Governance -The governance model adopted here is heaviliy influenced by a set of CNCF projects, especially drew +The governance model adopted here is heavily influenced by a set of CNCF projects, especially drew reference from [Kubernetes governance](https://github.com/kubernetes/community/blob/master/governance.md). *For similar structures some of the same wordings from kubernetes governance are borrowed to adhere to the originally construed meaning.* diff --git a/docs/proposals/cloudcore-ha-design.md b/docs/proposals/cloudcore-ha-design.md index dcba8ecc2..d99c1c4ef 100644 --- a/docs/proposals/cloudcore-ha-design.md +++ b/docs/proposals/cloudcore-ha-design.md @@ -75,7 +75,7 @@ At present, CloudCore is essentially an edge-resource distribution center, which 1. Become the leader 1. Start each controller and serve for edge-nodes 1. Notify the LoadBalance cloudcore is ready - 1. Lose the leadership position due to network fluctuation or other reason, **shutdown immediatly**;At the same time, one of the standby cloudcores becomes leader. + 1. Lose the leadership position due to network fluctuation or other reason, **shutdown immediately**;At the same time, one of the standby cloudcores becomes leader. 1. Restart by an external operation, downgrade to be a standby cloudcore also known as follower. The process of 3(start the controllers) also contains the cache initialization, such as the above-mentioned LocationCache.Ideally cache should initialize before the Leader election block, but it means the deconstruction of controllers as well as a lot of work. If subsequent discoveries show that cache initialization time led to the switch time growth greatly, then consider to deconstruct the controllers. At present, the cache initialization time is in milliseconds. @@ -138,7 +138,7 @@ status: `Endpoint is readiness == All container are ready + PodReadinessGate is true` -It means traffic is not forward to the back cloudcore untill we Patch the status of "kubeedge.io/CloudCoreIsLeader" from "False" to "True" after this cloudcore becoming leader. +It means traffic is not forward to the back cloudcore until we Patch the status of "kubeedge.io/CloudCoreIsLeader" from "False" to "True" after this cloudcore becoming leader. ##### Other LoadBalance such as keepalived |