brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sjcorb...@apache.org
Subject [2/4] incubator-brooklyn git commit: fixes typos
Date Thu, 08 Jan 2015 16:11:30 GMT
fixes typos

Project: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/commit/06c8ce36
Tree: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/tree/06c8ce36
Diff: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/diff/06c8ce36

Branch: refs/heads/master
Commit: 06c8ce36e800089590ad08d22abbd9eb62858298
Parents: 7c35d20
Author: Robert Moss <robertgmoss@gmail.com>
Authored: Wed Jan 7 13:28:37 2015 +0000
Committer: Robert Moss <robertgmoss@gmail.com>
Committed: Wed Jan 7 13:28:37 2015 +0000

----------------------------------------------------------------------
 docs/website/community/how-to-contribute-docs.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/06c8ce36/docs/website/community/how-to-contribute-docs.md
----------------------------------------------------------------------
diff --git a/docs/website/community/how-to-contribute-docs.md b/docs/website/community/how-to-contribute-docs.md
index b6b3cd5..2e29b6b 100644
--- a/docs/website/community/how-to-contribute-docs.md
+++ b/docs/website/community/how-to-contribute-docs.md
@@ -93,7 +93,7 @@ Contributing using GitHub
 Our GitHub repository is located at
 [https://github.com/apache/incubator-brooklyn](https://github.com/apache/incubator-brooklyn)
 
-Your commit messages must properly describes the changes that have been made and
+Your commit messages must properly describe the changes that have been made and
 their purpose ([here are some
 guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)).
 If your contributions fix a Jira issue, then ensure that you reference the issue
@@ -130,7 +130,7 @@ set of commits, and having an atomic change per commit is preferred in
the end.
 Use your best judgement and work with your reviewer as to when you should revise
 a commit or create a new one.
 
-A pull request is considered ready to be merged once it gets at lease one +1
+A pull request is considered ready to be merged once it gets at least one +1
 from a committer. Once all the changes have been completed and the pull request
 is accepted, you may be asked to rebase it against the latest code. You may also
 wish to squash some commits together and make other history revisions, to leave


Mime
View raw message