aboutsummaryrefslogtreecommitdiff
path: root/doc/rcs
diff options
context:
space:
mode:
authorhttps://launchpad.net/~kralph <kralph@web>2011-01-26 15:57:44 +0000
committerJoey Hess <joey@kitenet.net>2011-01-26 15:57:44 +0000
commitbeaa2790922328be6a9907ed47c6855203082f22 (patch)
treeb83b3cebf8ef90d22e3bd6eac9574ce1bad51bbf /doc/rcs
parentd9e347079e8c6517a08025dc632c09d44106b3f5 (diff)
downloadikiwiki-beaa2790922328be6a9907ed47c6855203082f22.tar
ikiwiki-beaa2790922328be6a9907ed47c6855203082f22.tar.gz
spelling, grammar
Diffstat (limited to 'doc/rcs')
-rw-r--r--doc/rcs/git.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/rcs/git.mdwn b/doc/rcs/git.mdwn
index c627792d7..1b66493dd 100644
--- a/doc/rcs/git.mdwn
+++ b/doc/rcs/git.mdwn
@@ -56,8 +56,8 @@ repositories:
repositories are also clones of the bare root repository above --
and these have a working directory for you to work on. Use either
the `git` transport (if available), or `ssh`. These repositories may
- be on remote machines, your laptop, whereever you find convenient to
- hack on your wiki. you can commit local changes to the version on
+ be on remote machines, your laptop, wherever you find convenient to
+ hack on your wiki. You can commit local changes to the version on
the laptop, perhaps while offline. Any new content should be pushed to the
bare master repository when you are ready to publish it, and then
the post-update hook of the bare repository will ensure that the