diff options
| author | Ed Costello <epc@epcostello.com> | 2015-10-29 14:36:29 -0400 |
|---|---|---|
| committer | Ed Costello <epc@epcostello.com> | 2015-12-22 09:30:48 -0500 |
| commit | b3849ceb4436cc722929bd742e6614678835a3ce (patch) | |
| tree | 7107763bfbd4c942ba82dac479ce147f0cb3d36c /api-conventions.md | |
| parent | 99d4231f21ddf43919d56888930585f508985c0e (diff) | |
Copy edits for typos
Diffstat (limited to 'api-conventions.md')
| -rw-r--r-- | api-conventions.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/api-conventions.md b/api-conventions.md index ab049694..00c2ec62 100644 --- a/api-conventions.md +++ b/api-conventions.md @@ -403,7 +403,7 @@ Using the `omitempty` tag causes swagger documentation to reflect that the field Using a pointer allows distinguishing unset from the zero value for that type. There are some cases where, in principle, a pointer is not needed for an optional field -since the zero value is forbidden, and thus imples unset. There are examples of this in the +since the zero value is forbidden, and thus implies unset. There are examples of this in the codebase. However: - it can be difficult for implementors to anticipate all cases where an empty value might need to be |