diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-02-22 06:31:40 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-22 06:31:40 -0800 |
| commit | 320c827df9075546d42fca5f77395bc3793b14f2 (patch) | |
| tree | 31b76e98b915f3d9779b9f31c17dd5f405512eef | |
| parent | de7ea79159cc222c6afb93ba36725789340ce91a (diff) | |
| parent | fda94d5330484950d1d07d89f0984340fcfb65b6 (diff) | |
Merge pull request #1838 from the-redback/patch-1
Fix typo in aggregated-api-servers.md doc
| -rw-r--r-- | contributors/design-proposals/api-machinery/aggregated-api-servers.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/api-machinery/aggregated-api-servers.md b/contributors/design-proposals/api-machinery/aggregated-api-servers.md index d1299a19..7817cd1f 100644 --- a/contributors/design-proposals/api-machinery/aggregated-api-servers.md +++ b/contributors/design-proposals/api-machinery/aggregated-api-servers.md @@ -20,7 +20,7 @@ aggregated servers. unblock these APIs. * Place for staging experimental APIs: New APIs can be developed in separate aggregated servers, and installed only by those willing to take the risk of - installing an experimental API. One they are stable, it is then easy to + installing an experimental API. Once they are stable, it is then easy to package them up for installation in other clusters. * Ensure that new APIs follow kubernetes conventions: Without the mechanism proposed here, community members might be forced to roll their own thing which |