diff options
| author |  Brad Wannow <wannow21@gmail.com> | 2018-02-08 12:47:34 -0600 |
|---|---|---|
| committer |  Jonathan Hseu <vomjom@vomjom.net> | 2018-02-08 10:47:34 -0800 |
| commit | 4272366ff2152434cc5cdd94595a2352e5a0d826 (patch) | |
| tree | 5192f447c324d3bfd336597e540699a262d11f4a /CONTRIBUTING.md | |
| parent | 169337f8dae87e75e4535fb22fcaac85d341036c (diff) | |
Update CONTRIBUTING.md (#16806)
* Update CONTRIBUTING.md
Edited a few grammar issues.
* Fix
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2e2182bb21..3dad41a88c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,7 +41,7 @@ TensorFlow coding style. #### General guidelines and philosophy for contribution * Include unit tests when you contribute new features, as they help to - a) prove that your code works correctly, b) guard against future breaking + a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost. * Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage. @@ -51,7 +51,7 @@ TensorFlow coding style. non-backward-compatible API changes without a major release. Reviewers of your pull request will comment on any API compatibility issues. * When you contribute a new feature to TensorFlow, the maintenance burden is (by - default) transferred to the TensorFlow team. This means that benefit of + default) transferred to the TensorFlow team. This means that benefit of the contribution must be compared against the cost of maintaining the feature. * Full new features (e.g., a new op implementing a cutting-edge algorithm) typically will live in |