whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typo fix: some word error (#8524)

Browse Source 
* Typo fix: Acceptible=>Acceptable and componenets=>components

* Typo fix: Availablity=>Availability

* Typo fix: implicity=>implicitly
This commit is contained in:
Wen Gao
2018-05-16 08:48:28 +08:00
committed by k8s-ci-robot
parent b16dae5309
commit 53d2e174d7
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/setup-ha-etcd-with-kubeadm.md
+1 -1
View File
@@ -1,7 +1,7 @@
---
reviewers:
- chuckha
title: Set up a High-Availablity Etcd Cluster With Kubeadm
title: Set up a High-Availability Etcd Cluster With Kubeadm
content_template: templates/task
---
content/en/docs/tasks/federation/set-up-cluster-federation-kubefed.md
+1 -1
View File
@@ -379,7 +379,7 @@ For more information see
It is possible to utilize AWS Route53 as a cloud DNS provider when the
federation controller-manager is run on-premise. The controller-manager
Deployment must be configured with AWS credentials since it cannot implicity
Deployment must be configured with AWS credentials since it cannot implicitly
gather them from a VM running on AWS.
Currently, `kubefed init` does not read AWS Route53 credentials from the