Skip to content

Commit 5b113ce

Browse files
authored
docs: Correcting *.md files using Grammarly (#97)
1 parent fbe682b commit 5b113ce

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,14 @@ This project adheres to [Semantic Versioning](http://semver.org/).
8787
### BREAKING Change
8888
- [Pull #14](https://github.com/sendgrid/java-http-client/pull/14): Make response have private variables
8989
- Fixed [Issue #12](https://github.com/sendgrid/java-http-client/issues/12): The public Response variables should be private
90-
- The breaking change is that variables that were public are now private and accessable only via getters and setters
90+
- The breaking change is that variables that were public are now private and accessible only via getters and setters
9191
- BIG thanks to [Diego Camargo](https://github.com/belfazt) for the pull request!
9292

9393
## [3.0.0] - 2016-10-06
9494
### BREAKING Change
9595
- [Pull #15](https://github.com/sendgrid/java-http-client/pull/15): Update the request object with sensible defaults and access methods
9696
- Fixes [Issue #13](https://github.com/sendgrid/java-http-client/issues/13): Update the Request object with sensible defaults and access methods
97-
- The breaking change is that variables that were public are now private and accessable only via getters and setters
97+
- The breaking change is that variables that were public are now private and accessible only via getters and setters
9898
- BIG thanks to [Diego Camargo](https://github.com/belfazt) for the pull request!
9999

100100
## [2.3.4] - 2016-08-09

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Hello! Thank you for choosing to help contribute to one of the SendGrid open source projects. There are many ways you can contribute and help is always welcome. We simply ask that you follow the following contribution policies.
1+
Hello! Thank you for choosing to help contribute to one of the SendGrid open source projects. There are many ways you can contribute and help is always welcome. We simply ask that you follow the following contribution policies.
22

33
- [Feature Request](#feature-request)
44
- [Submit a Bug Report](#submit-a-bug-report)
@@ -9,7 +9,7 @@ Hello! Thank you for choosing to help contribute to one of the SendGrid open sou
99
- [Creating a Pull Request](#creating-a-pull-request)
1010
- [Code Reviews](#code-reviews)
1111

12-
We use [Milestones](https://github.com/sendgrid/java-http-client/milestones) to help define current roadmaps, please feel free to grab an issue from the current milestone. Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions and additional PRs are welcomed and encouraged.
12+
We use [Milestones](https://github.com/sendgrid/java-http-client/milestones) to help define current roadmaps, please feel free to grab an issue from the current milestone. Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions, and additional PRs are welcomed and encouraged.
1313

1414
<a name="feature-request"></a>
1515
## Feature Request
@@ -31,7 +31,7 @@ A software bug is a demonstrable issue in the code base. In order for us to diag
3131
Before you decide to create a new issue, please try the following:
3232

3333
1. Check the Github issues tab if the identified issue has already been reported, if so, please add a +1 to the existing post.
34-
2. Update to the latest version of this code and check if issue has already been fixed
34+
2. Update to the latest version of this code and check if the issue has already been fixed
3535
3. Copy and fill in the Bug Report Template we have provided below
3636

3737
### Please use our Bug Report Template
@@ -157,7 +157,7 @@ Please run your code through:
157157

158158
4. Commit your changes in logical chunks. Please adhere to these [git commit
159159
message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
160-
or your code is unlikely be merged into the main project. Use Git's
160+
or your code is unlikely to be merged into the main project. Use Git's
161161
[interactive rebase](https://help.github.com/articles/interactive-rebase)
162162
feature to tidy up your commits before making them public.
163163

0 commit comments

Comments
 (0)