kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3106 from vagababov/unify-formatting 

Unify how the example lists are formatted in the document.
This commit is contained in:
Kubernetes Prow Robot 2019-01-17 15:02:46 -08:00 committed by GitHub
parent 2a20f6fa53 449ee0588c
commit a67239367a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
contributors/devel/api-conventions.md
View File

@ -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