summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaruf Tuhin <maruf.2hin@gmail.com>2018-02-22 14:20:42 +0600
committerGitHub <noreply@github.com>2018-02-22 14:20:42 +0600
commitfda94d5330484950d1d07d89f0984340fcfb65b6 (patch)
tree31b76e98b915f3d9779b9f31c17dd5f405512eef
parentde7ea79159cc222c6afb93ba36725789340ce91a (diff)
Fix typo in aggregated-api-servers.md doc
-rw-r--r--contributors/design-proposals/api-machinery/aggregated-api-servers.md2
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