From 3b163f9fe088fc29547070312c78840ce9e729a8 Mon Sep 17 00:00:00 2001 From: bruceauyeung Date: Wed, 11 Jan 2017 16:54:10 +0800 Subject: [PATCH] fix-syntax-errors-and-typos Signed-off-by: bruceauyeung --- docs/getting-started-guides/kubeadm.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 74d2f18906..1765e0a1f4 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -27,14 +27,14 @@ automatically configuring cloud providers. Please refer to the specific cloud pr use another provisioning system.** kubeadm assumes you have a set of machines (virtual or real) that are up and running. It is designed -to be part of a larger provisioning system - or just for easy manual provisioning. kubeadm is a great +to be part of a large provisioning system - or just for easy manual provisioning. kubeadm is a great choice where you have your own infrastructure (e.g. bare metal), or where you have an existing orchestration system (e.g. Puppet) that you have to integrate with. -If you are not constrained, other tools build on kubeadm to give you complete clusters: +If you are not constrained, there are some other tools built to give you complete clusters: -* On GCE, [Google Container Engine](https://cloud.google.com/container-engine/) gives you turn-key Kubernetes -* On AWS, [kops](https://github.com/kubernetes/kops) makes installation and cluster management easy (and supports high availability) +* On GCE, [Google Container Engine](https://cloud.google.com/container-engine/) gives you one-click Kubernetes clusters +* On AWS, [kops](https://github.com/kubernetes/kops) makes cluster installation and management easy (and supports high availability) ## Prerequisites @@ -97,7 +97,7 @@ For each host in turn: The kubelet is now restarting every few seconds, as it waits in a crashloop for `kubeadm` to tell it what to do. -Note: To disable SELinux by running `setenforce 0` is required in order to allow containers to access the host filesystem, which is required by pod networks for example. You have to do this until kubelet can handle SELinux better. +Note: Disabling SELinux by running `setenforce 0` is required in order to allow containers to access the host filesystem, which is required by pod networks for example. You have to do this until kubelet can handle SELinux better. ### (2/4) Initializing your master