Documentation: fix typos in man pages
Signed-off-by: Øystein Walle <oystwa@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Øystein Walle committed
Feb 5, 2014 at 23:19 UTC
5fe8f49b6d59cf143a5898ddbb161444a95fa871
6 files changed
+7
-7
Documentation/git-clone.txt
+1
-1
@@ -213,7 +213,7 @@ objects from the source repository into a pack in the cloned repository.
213
--separate-git-dir=<git dir>::
214
Instead of placing the cloned repository where it is supposed
215
to be, place the cloned repository at the specified directory,
216
- then make a filesytem-agnostic Git symbolic link to there.
216
+ then make a filesystem-agnostic Git symbolic link to there.
217
The result is Git repository can be separated from working
218
tree.
219
Documentation/git-diff.txt
+1
-1
@@ -44,7 +44,7 @@ two blob objects, or changes between two files on disk.
44
commit relative to the named <commit>. Typically you
45
would want comparison with the latest commit, so if you
46
do not give <commit>, it defaults to HEAD.
47
- If HEAD does not exist (e.g. unborned branches) and
47
+ If HEAD does not exist (e.g. unborn branches) and
48
<commit> is not given, it shows all staged changes.
49
--staged is a synonym of --cached.
50
Documentation/gitcli.txt
+1
-1
@@ -28,7 +28,7 @@ arguments. Here are the rules:
28
they can be disambiguated by placing `--` between them.
29
E.g. `git diff -- HEAD` is, "I have a file called HEAD in my work
30
tree. Please show changes between the version I staged in the index
31
- and what I have in the work tree for that file". not "show difference
31
+ and what I have in the work tree for that file", not "show difference
32
between the HEAD commit and the work tree as a whole". You can say
33
`git diff HEAD --` to ask for the latter.
34
Documentation/githooks.txt
+1
-1
@@ -251,7 +251,7 @@ three parameters:
251
252
- the name of the ref being updated,
253
- the old object name stored in the ref,
254
- - and the new objectname to be stored in the ref.
254
+ - and the new object name to be stored in the ref.
255
256
A zero exit from the update hook allows the ref to be updated.
257
Exiting with a non-zero status prevents 'git-receive-pack'
Documentation/gitweb.conf.txt
+2
-2
@@ -630,13 +630,13 @@ need to set this element to empty list i.e. `[]`.
630
631
override::
632
If this field has a true value then the given feature is
633
- overriddable, which means that it can be configured
633
+ overridable, which means that it can be configured
634
(or enabled/disabled) on a per-repository basis.
635
+
636
Usually given "<feature>" is configurable via the `gitweb.<feature>`
637
config variable in the per-repository Git configuration file.
638
+
639
-*Note* that no feature is overriddable by default.
639
+*Note* that no feature is overridable by default.
640
641
sub::
642
Internal detail of implementation. What is important is that
Documentation/user-manual.txt
+1
-1
@@ -3795,7 +3795,7 @@ like so:
3795
$ git update-index filename
3796
-------------------------------------------------
3797
3798
-but to avoid common mistakes with filename globbing etc, the command
3798
+but to avoid common mistakes with filename globbing etc., the command
3799
will not normally add totally new entries or remove old entries,
3800
i.e. it will normally just update existing cache entries.
3801