summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGin <hejin@ghostcloud.cn>2017-11-05 15:22:51 +0800
committerGitHub <noreply@github.com>2017-11-05 15:22:51 +0800
commita46a4dd4c59e80fe9925031c8d8cee0743793ee6 (patch)
tree548a52875c6277c6278513916222b30095b7053d
parent24d28655d80ede1e4ccedd9ac0ed5abd6b8034af (diff)
Update alternate-api-representations.md
-rw-r--r--contributors/design-proposals/api-machinery/alternate-api-representations.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/api-machinery/alternate-api-representations.md b/contributors/design-proposals/api-machinery/alternate-api-representations.md
index 2e96ef81..e7635bc3 100644
--- a/contributors/design-proposals/api-machinery/alternate-api-representations.md
+++ b/contributors/design-proposals/api-machinery/alternate-api-representations.md
@@ -80,7 +80,7 @@ a real API group.
* We wish to support retrieving object representations in multiple schemas - JSON for
simple clients and Protobuf for clients concerned with efficiency.
* Most clients will wish to retrieve a newer format, but for older servers will desire
- to fall back to the implict resource represented by the endpoint.
+ to fall back to the implicit resource represented by the endpoint.
* Over time, clients may need to request results in multiple API group versions
because of breaking changes (when we introduce v2, clients that know v2 will want
to ask for v2, then v1)