diff options
| author | yank1 <kay.yan@daocloud.io> | 2018-02-07 00:00:19 +0800 |
|---|---|---|
| committer | yank1 <kay.yan@daocloud.io> | 2018-02-07 00:00:19 +0800 |
| commit | 27aeb15c4e94877326fda97d5e131a0ce7646deb (patch) | |
| tree | 167bfb40972332eff766e6a7a89edd535787debe | |
| parent | ce0cb1796b4fe82dd648c6a437749166b34faa7f (diff) | |
fix a typo in alternate api representations
| -rw-r--r-- | contributors/design-proposals/api-machinery/alternate-api-representations.md | 2 |
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 e7635bc3..d54709a5 100644 --- a/contributors/design-proposals/api-machinery/alternate-api-representations.md +++ b/contributors/design-proposals/api-machinery/alternate-api-representations.md @@ -25,7 +25,7 @@ versions of the existing content and are not intended to support arbitrary param Also, the server today contains a number of objects which are common across multiple groups, but which clients must be able to deal with in a generic fashion. These objects - Status, ListMeta, ObjectMeta, List, ListOptions, ExportOptions, and Scale - are embedded into each -group version but are actually part of a a shared API group. It must be possible for a naive +group version but are actually part of a shared API group. It must be possible for a naive client to translate the Scale response returned by two different API group versions. |