Skip to content

added grammatical changes #2354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

added grammatical changes #2354

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions site/en/community/contribute/code.md
View file
Original file line number Diff line number Diff line change
@@ -2,7 +2,7 @@

Whether you are adding a loss function, improving test coverage, or writing an
RFC for a major design change, this portion of the contributor guide will help
you get started. Thank you for your work and interest in improving TensorFlow.
you get started. Thank you for your contributions and interest in improving TensorFlow.

## Before you get started

@@ -24,10 +24,10 @@ project is to work on known issues.
## Issues for new contributors

New contributors should look for the following tags when searching for a first
contribution to the TensorFlow code base. We strongly recommend that new
contribution to the TensorFlow codebase. We strongly recommend that new
contributors tackle “good first issue” and "contributions welcome" projects
first; this helps the contributor become familiar with the contribution
workflow, and for the core devs to become acquainted with the contributor.
first. this helps the contributor become familiar with the contribution
workflow, and allows core developers to get to know them.

- [good first issue](https://github.com/tensorflow/tensorflow/labels/good%20first%20issue)
- [contributions welcome](https://github.com/tensorflow/tensorflow/labels/stat%3Acontributions%20welcome)
@@ -60,7 +60,7 @@ Here are some questions to keep in mind during the code review process:

## Test and improve test coverage

High-quality unit testing is a corner-stone of the TensorFlow development
High-quality unit testing is a cornerstone of the TensorFlow development
process. For this purpose, we use Docker images. The test functions are
appropriately named, and are responsible for checking the validity of algorithms
as well as different options of the code.
@@ -73,7 +73,7 @@ currently causing a bug — please file an issue and, if possible, a pull reques
For the specific details of testing procedures in each TensorFlow project, see
the `README.md` and `CONTRIBUTING.md` files in the project repo on GitHub.

Of particular concerns in *adequate testing*:
Of particular concern in *adequate testing*:

* Is *every public function and class* tested?
* Are a *reasonable set of parameters*, their values, value types, and
6 changes: 3 additions & 3 deletions site/en/community/contribute/community.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Contribute to the TensorFlow community

An open source project isn't just about the code, it's also about the community of users, developers, writers, researchers, and other contributors. You can help grow and support this community.
An open source project isn't just about the code; it's also about the community of users, developers, writers, researchers, and other contributors. You can help grow and support this community.

Please read the TensorFlow [Code and Collaboration governance](https://github.com/tensorflow/community/blob/master/governance/code-and-collaboration.md).

@@ -34,7 +34,7 @@ The primary communication about work on TensorFlow happens in the [TensorFlow re

### Mailing lists

Most communication happens on the TensorFlow Forum. The following mailing lists are still used for announcements and contributor conversations. Note that they are not intended to provide technical support.
Most of the communication happens on the TensorFlow Forum. The following mailing lists are still used for announcements and contributor conversations. Note that they are not intended to provide technical support.

* [announce@tensorflow.org](mailto:announce@tensorflow.org) — All major releases and important announcements are sent to this mailing group. We recommend that you join this list if you depend on TensorFlow in any way.
* [developers@tensorflow.org](mailto:developers@tensorflow.org) — Discussion for developers who are contributing to TensorFlow.
@@ -43,7 +43,7 @@ For more information on project-specific communication, visit the [Contribute to

### Blog and social media

The [TensorFlow Blog](http://blog.tensorflow.org/) is full of great content both from our team at Google and the broader community. We'd love to hear what you have to say, so if you would like to submit an article for review, please contact us at tensorflow-blog@google.com. Note that we receive many great submissions, and setting expectations, we can only publish a few.
The [TensorFlow Blog](http://blog.tensorflow.org/) is full of great content both from our team at Google and the broader community. We'd love to hear what you have to say, so if you would like to submit an article for review, please contact us at tensorflow-blog@google.com. Note that we receive many great submissions, and set expectations, we can only publish a few.

On [Twitter](https://twitter.com/tensorflow) we share the latest and greatest from our community, and our [YouTube channel](https://www.youtube.com/tensorflow) has free educational content to help you create, understand and deploy models for a variety of applications.