diff options
| author | Yusuke Tsutsumi <yusuke@tsutsumi.io> | 2021-05-21 21:05:39 -0700 |
|---|---|---|
| committer | Yusuke Tsutsumi <yusuke@tsutsumi.io> | 2021-05-24 21:51:07 -0700 |
| commit | 9b694b1b7908489d1064d2740d583bdac4d491c7 (patch) | |
| tree | 9597f8d4baf910fcaaf5ef26c4fdbaf403559a77 | |
| parent | fed5c1e6a61e65ceabc7a9ffa0829eceeb51f275 (diff) | |
Update contributors/devel/sig-architecture/api-conventions.md
Co-authored-by: Daniel Smith <dbsmith@google.com>
| -rw-r--r-- | contributors/devel/sig-architecture/api-conventions.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/contributors/devel/sig-architecture/api-conventions.md b/contributors/devel/sig-architecture/api-conventions.md index 143ccd61..4c02eeff 100644 --- a/contributors/devel/sig-architecture/api-conventions.md +++ b/contributors/devel/sig-architecture/api-conventions.md @@ -903,7 +903,7 @@ The "{field}" component should be named to indicate the purpose of the reference endpoint indicates that the object reference specifies the target. It is okay to have the "{field}" component indicate the resource type. For example, "secretRef" when referencing -a secret. However, this comes with the risk off the field being a misnomer in the case that the field is expanded to +a secret. However, this comes with the risk of the field being a misnomer in the case that the field is expanded to reference more than one type. ### Object References Examples @@ -1549,4 +1549,3 @@ Example: "must be greater than \`request\`". be less than 256", "must be greater than or equal to 0". Do not use words like "larger than", "bigger than", "more than", "higher than", etc. * When specifying numeric ranges, use inclusive ranges when possible. - |