Skip to content

Commit

Permalink
Merge pull request progit#218 from dtikhonov/setup
Browse files Browse the repository at this point in the history
Grammar fix: setup is not a verb.
  • Loading branch information
ben committed Dec 22, 2014
2 parents f782ee5 + a32f689 commit ff44911
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion book/06-github/sections/2-contributing.asc
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
=== Contributing to a Project

Now that our account is setup, let's walk through some details that could be useful in helping you contribute to an existing project.
Now that our account is set up, let's walk through some details that could be useful in helping you contribute to an existing project.

==== Forking Projects

Expand Down
2 changes: 1 addition & 1 deletion book/06-github/sections/5-scripting.asc
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@ Hopefully this is fairly simple to follow. In this web hook handler we look thro

In this case you can send a state ('success', 'failure', 'error'), a description of what happened, a target URL the user can go to for more information and a ``context'' in case there are multiple statuses for a single commit. For example, a testing service may provide a status and a validation service like this may also provide a status -- the ``context'' field is how they're differentiated.

If someone opens a new Pull Request on GitHub and this hook is setup, you may see something like <<_commit_status>>.
If someone opens a new Pull Request on GitHub and this hook is set up, you may see something like <<_commit_status>>.

[[_commit_status]]
.Commit status via the API.
Expand Down

0 comments on commit ff44911

Please sign in to comment.