diff options
| author | likeXXxx <likexin@ghostcloud.cn> | 2018-10-29 13:50:23 +0800 |
|---|---|---|
| committer | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-10-28 22:50:23 -0700 |
| commit | f99704a490d2cbf86e76ee8f8b1f17c0c7e7e75f (patch) | |
| tree | d9ff24a48c6f9130e0690555109eac9031c7c37d /sig-scalability | |
| parent | 38d96e9eaa25da80b6757e6b5b9212259865245f (diff) | |
fix some typos (#2867)
* fix a type
* fix a typo
* fix a typo
* fix a typo
Diffstat (limited to 'sig-scalability')
| -rw-r--r-- | sig-scalability/slos/network_programming_latency.md | 2 | ||||
| -rw-r--r-- | sig-scalability/slos/pod_startup_latency.md | 2 | ||||
| -rw-r--r-- | sig-scalability/slos/slos.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/sig-scalability/slos/network_programming_latency.md b/sig-scalability/slos/network_programming_latency.md index 38eeebf0..dc1dace2 100644 --- a/sig-scalability/slos/network_programming_latency.md +++ b/sig-scalability/slos/network_programming_latency.md @@ -60,7 +60,7 @@ this update: already present at storage layer, so it won't be hard to propagate that. 1. The in-cluster load-balancing programmer will export a prometheus metric once done with programming. The latency of the operation is defined as -difference betweem timestamp of then whe operation is done and timestamp +difference between timestamp of then whe operation is done and timestamp recorded in the newly introduced annotation. #### Caveats diff --git a/sig-scalability/slos/pod_startup_latency.md b/sig-scalability/slos/pod_startup_latency.md index 04fdd63b..7c52777e 100644 --- a/sig-scalability/slos/pod_startup_latency.md +++ b/sig-scalability/slos/pod_startup_latency.md @@ -38,7 +38,7 @@ is heavily application-dependent (and does't depend on Kubernetes itself). not obvious. We decided for the semantic of "when all its containers are reported as started and observed via watch", because: - we require all containers to be started (not e.g. the first one) to ensure - that the pod is started. We need to ensure that pontential regressions like + that the pod is started. We need to ensure that potential regressions like linearization of container startups within a pod will be catch by this SLI. - note that we don't require all container to be running - if some of them finished before the last one was started that is also fine. It is just diff --git a/sig-scalability/slos/slos.md b/sig-scalability/slos/slos.md index 5b9fb4bf..1f9a15c8 100644 --- a/sig-scalability/slos/slos.md +++ b/sig-scalability/slos/slos.md @@ -27,7 +27,7 @@ Our SLIs/SLOs need to have the following properties: arcane knowledge. We may also introduce internal(for developers only) SLIs, that may be useful -for understanding performance characterstic of the system, but for which +for understanding performance characteristic of the system, but for which we don't provide any guarantees for users (and thus don't require them to be that easily understandable). |