diff options
| author | AdamDang <adam.dang@daocloud.io> | 2018-06-12 13:08:30 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-12 13:08:30 +0800 |
| commit | c95f85ac7016e2674702a0da7f16764d100e4d2a (patch) | |
| tree | 4cf20eaa1a0b0e3fb46c360ab64c72558e519e19 | |
| parent | 2b07e541f8a24ffe393498bddd1cc1b0b08d5091 (diff) | |
Typo fix: Descibe->Describe
Descibe->Describe
| -rw-r--r-- | sig-scalability/slos/api_call_latency.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sig-scalability/slos/api_call_latency.md b/sig-scalability/slos/api_call_latency.md index 65d7dc26..9f40924d 100644 --- a/sig-scalability/slos/api_call_latency.md +++ b/sig-scalability/slos/api_call_latency.md @@ -6,7 +6,7 @@ response from an API call. - As an administrator of Kubernetes cluster, if I know characteristics of my external dependencies of apiserver (e.g custom admission plugins, webhooks and initializers) I want to be able to provide guarantees for API calls latency to -users of my cluster +users of my cluster. ### Other notes - We obviously can’t give any guarantee in general, because cluster @@ -44,4 +44,4 @@ comparable with `namespaced` ones. ### Test scenario -__TODO: Descibe test scenario.__ +__TODO: Describe test scenario.__ |