From c6170eb79d694fb8c124a5854585ecab3ebb8393 Mon Sep 17 00:00:00 2001
From: Nguyen Hai Truong <truongnh@vn.fujitsu.com>
Date: Wed, 26 Feb 2020 19:46:28 +0700
Subject: [PATCH] docs: fix some typos (#5618)
Although it is spelling mistakes, it might make affect while reading.
Signed-off-by: Nguyen Hai Truong <truongnh@vn.fujitsu.com>
---
docs/comparisons.md | 2 +-
docs/kubernetes-reliability.md | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/comparisons.md b/docs/comparisons.md
index e0244d469..d0f50c548 100644
--- a/docs/comparisons.md
+++ b/docs/comparisons.md
@@ -1,4 +1,4 @@
-# Comparaison
+# Comparison
## Kubespray vs [Kops](https://github.com/kubernetes/kops)
diff --git a/docs/kubernetes-reliability.md b/docs/kubernetes-reliability.md
index b2491840f..06357bf4e 100644
--- a/docs/kubernetes-reliability.md
+++ b/docs/kubernetes-reliability.md
@@ -12,14 +12,14 @@ By default the normal behavior looks like:
1. Kubelet updates it status to apiserver periodically, as specified by
`--node-status-update-frequency`. The default value is **10s**.
-2. Kubernetes controller manager checks the statuses of Kubelets every
+2. Kubernetes controller manager checks the statuses of Kubelet every
`–-node-monitor-period`. The default value is **5s**.
3. In case the status is updated within `--node-monitor-grace-period` of time,
Kubernetes controller manager considers healthy status of Kubelet. The
default value is **40s**.
-> Kubernetes controller manager and Kubelets work asynchronously. It means that
+> Kubernetes controller manager and Kubelet work asynchronously. It means that
> the delay may include any network latency, API Server latency, etcd latency,
> latency caused by load on one's master nodes and so on. So if
> `--node-status-update-frequency` is set to 5s in reality it may appear in
--
GitLab