Skip to content

Commit

Permalink
Fixes documentation typos
Browse files Browse the repository at this point in the history
  • Loading branch information
ctilden1 committed Aug 24, 2011
1 parent e5e9579 commit 0172868
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/gitolite-and-ssh.mkd
Expand Up @@ -135,7 +135,7 @@ When `gl-auth-command` gets control, it looks at the first argument
`SSH_ORIGINAL_COMMAND` variable to find out which repository you want to
access, and whether you're reading or writing.

Now is has user, repository, and access requested (read/write), gitolite looks
Now that it has a user, repository, and access requested (read/write), gitolite looks
at its config file, and either allows or rejects the request.

But this cannot differentiate between different branches within a repo; that
Expand All @@ -155,7 +155,7 @@ happen -- see `git help hooks` for details. One of those hooks is the
tag is about to be updated. The hook is passed the name of the branch or tag,
the old SHA1 value, and the new SHA1 value, as arguments. Hooks that are
called *before* an action happens are allowed to prevent that action from
happening y returning an error code.
happening by returning an error code.

When gitolite is told to create a new repository (by the admin), it installs
a special update hook. This hook takes all the information presented, looks
Expand Down

0 comments on commit 0172868

Please sign in to comment.