From d5c07162c46c40253d6c749069271e12d04be29d Mon Sep 17 00:00:00 2001 From: AdamDang Date: Fri, 4 May 2018 12:20:51 +0800 Subject: [PATCH] fix some typos (#8300) * Update add-entries-to-pod-etc-hosts-with-host-aliases.md * Update audit.md * Update partner-script.js --- _includes/partner-script.js | 2 +- .../add-entries-to-pod-etc-hosts-with-host-aliases.md | 2 +- docs/tasks/debug-application-cluster/audit.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_includes/partner-script.js b/_includes/partner-script.js index a874c80f62..36d1f66bcc 100644 --- a/_includes/partner-script.js +++ b/_includes/partner-script.js @@ -271,7 +271,7 @@ name: 'Emerging Technology Advisors', logo: 'eta', link: 'https://www.emergingtechnologyadvisors.com/services/kubernetes.html', - blurb: 'ETA helps companies architect, implement, and manage scalable applications using Kubernetes on on public or private cloud.' + blurb: 'ETA helps companies architect, implement, and manage scalable applications using Kubernetes on public or private cloud.' }, { type: 0, diff --git a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md index d17c7b8043..43dbd26205 100644 --- a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md +++ b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md @@ -14,7 +14,7 @@ Modification not using HostAliases is not suggested because the file is managed ## Default Hosts File Content -Lets start an Nginx Pod which is assigned an Pod IP: +Lets start an Nginx Pod which is assigned a Pod IP: ```shell $ kubectl run nginx --image nginx --generator=run-pod/v1 diff --git a/docs/tasks/debug-application-cluster/audit.md b/docs/tasks/debug-application-cluster/audit.md index 2bdfeabab3..9e004a9805 100644 --- a/docs/tasks/debug-application-cluster/audit.md +++ b/docs/tasks/debug-application-cluster/audit.md @@ -170,7 +170,7 @@ Parameters should be set to accommodate the load on the apiserver. For example, if kube-apiserver receives 100 requests each second, and each request is audited only on `ResponseStarted` and `ResponseComplete` stages, you should account for ~200 audit events being generated each second. Assuming that there are up to 100 events in a batch, -you should set throttling level at at least 2 QPS. Assuming that the backend can take up to +you should set throttling level at least 2 QPS. Assuming that the backend can take up to 5 seconds to write events, you should set the buffer size to hold up to 5 seconds of events, i.e. 10 batches, i.e. 1000 events.