github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-08 04:32:37 +00:00
Code Issues Projects Releases Wiki Activity

The VS and dot is seprated

Browse Source 
Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>
This commit is contained in:
YuPengZTE
2016-09-26 17:05:53 +08:00
parent 3aa8abd687
commit d0f69ee0f9
11 changed files with 18 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -63,7 +63,7 @@ resources](../user-guide/working-with-resources.md).*
- [List Operations](#list-operations)
- [Map Operations](#map-operations)
- [Idempotency](#idempotency)
- [Optional vs Required](#optional-vs-required)
- [Optional vs. Required](#optional-vs-required)
- [Defaulting](#defaulting)
- [Late Initialization](#late-initialization)
- [Concurrency Control and Consistency](#concurrency-control-and-consistency)
@@ -658,7 +658,7 @@ exists - instead, it will either return 201 Created or 504 with Reason
allotted, and the client should retry (optionally after the time indicated in
the Retry-After header).
## Optional vs Required
## Optional vs. Required
Fields must be either optional or required.

2
docs/devel/faster_reviews.md
View File

@@ -109,7 +109,7 @@ fast-moving codebase - lock in your changes ASAP, and make merges be someone
else's problem.
Obviously, we want every PR to be useful on its own, so you'll have to use
common sense in deciding what can be a PR vs what should be a commit in a larger
common sense in deciding what can be a PR vs. what should be a commit in a larger
PR. Rule of thumb - if this commit or set of commits is directly related to
Feature-X and nothing else, it should probably be part of the Feature-X PR. If
you can plausibly imagine someone finding value in this commit outside of