From 449ee0588c30198ede13217efb7809cdb44faf04 Mon Sep 17 00:00:00 2001 From: Victor Agababov Date: Thu, 17 Jan 2019 14:16:51 -0800 Subject: [PATCH] Unify how the example lists are formatted in the document. --- contributors/devel/api-conventions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributors/devel/api-conventions.md b/contributors/devel/api-conventions.md index 72ff7cf3e..0f32cce6c 100644 --- a/contributors/devel/api-conventions.md +++ b/contributors/devel/api-conventions.md @@ -122,7 +122,7 @@ defaults) and may not have lists. filtering (see [the labels documentation](https://kubernetes.io/docs/user-guide/labels/)), and most lists should support filtering by fields. - Examples: PodLists, ServiceLists, NodeLists + Examples: `PodLists`, `ServiceLists`, `NodeLists`. TODO: Describe field filtering below or in a separate doc. @@ -487,7 +487,7 @@ selectors, annotations, data), as opposed to sets of subobjects. Some fields will have a list of allowed values (enumerations). These values will be strings, and they will be in CamelCase, with an initial uppercase letter. -Examples: "ClusterFirst", "Pending", "ClientIP". +Examples: `ClusterFirst`, `Pending`, `ClientIP`. #### Unions