Skip to content

Commit ff44911

Browse files
committed
Merge pull request #218 from dtikhonov/setup
Grammar fix: setup is not a verb.
2 parents f782ee5 + a32f689 commit ff44911

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

book/06-github/sections/2-contributing.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
=== Contributing to a Project
22

3-
Now that our account is setup, let's walk through some details that could be useful in helping you contribute to an existing project.
3+
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.
44

55
==== Forking Projects
66

book/06-github/sections/5-scripting.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,7 @@ Hopefully this is fairly simple to follow. In this web hook handler we look thro
245245

246246
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.
247247

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

250250
[[_commit_status]]
251251
.Commit status via the API.

0 commit comments

Comments
 (0)