diff options
| author | laushinka <laurie.malau@gmail.com> | 2016-02-13 02:33:32 +0700 |
|---|---|---|
| committer | laushinka <laurie.malau@gmail.com> | 2016-02-18 06:58:05 +0700 |
| commit | 024b847eb1f07f450008f6997cdff1f9233c7b01 (patch) | |
| tree | 31eef82c5fcde795825b597e636b9b45206cdb9b /api_changes.md | |
| parent | 4457026c6fb93f74d3c36ae88a5a460602e24339 (diff) | |
Spelling fixes inspired by github.com/client9/misspell
Diffstat (limited to 'api_changes.md')
| -rw-r--r-- | api_changes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/api_changes.md b/api_changes.md index 0c039aab..585f015d 100644 --- a/api_changes.md +++ b/api_changes.md @@ -306,7 +306,7 @@ removed value as deprecated but allowed). This is actually a special case of a new representation, discussed above. For [Unions](api-conventions.md), sets of fields where at most one should be set, -it is acceptible to add a new option to the union if the [appropriate conventions] +it is acceptable to add a new option to the union if the [appropriate conventions] were followed in the original object. Removing an option requires following the deprecation process. |
