From 27aeb15c4e94877326fda97d5e131a0ce7646deb Mon Sep 17 00:00:00 2001 From: yank1 Date: Wed, 7 Feb 2018 00:00:19 +0800 Subject: [PATCH] fix a typo in alternate api representations --- .../api-machinery/alternate-api-representations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/api-machinery/alternate-api-representations.md b/contributors/design-proposals/api-machinery/alternate-api-representations.md index e7635bc31..d54709a59 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.