@matheusbsbs / matheus-bagliano / commits / 3742506578
Fork 0

Some doc typo fixes

All should be clear enough, except perhaps committish / commitish. I just kept the more-used one within the current docs. [jc: with rephrasing of check-ref-format description later discussed on the list] Signed-off-by: Francis Daly <francis@daoine.org> Signed-off-by: Junio C Hamano <junkio@cox.net>

Francis Daly committed Jun 7, 2006 at 13:56 UTC 3742506578dda5de2fe97e403f04150a85ffef17
10 files changed +14 -13
Documentation/config.txt
+3 -3
@@ -113,12 +113,12 @@ gitcvs.logfile::
113
114 http.sslVerify::
115 Whether to verify the SSL certificate when fetching or pushing
116 - over HTTPS. Can be overriden by the 'GIT_SSL_NO_VERIFY' environment
116 + over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
117 variable.
118
119 http.sslCert::
120 File containing the SSL certificate when fetching or pushing
121 - over HTTPS. Can be overriden by the 'GIT_SSL_CERT' environment
121 + over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
122 variable.
123
124 http.sslKey::
@@ -133,7 +133,7 @@ http.sslCAInfo::
133
134 http.sslCAPath::
135 Path containing files with the CA certificates to verify the peer
136 - with when fetching or pushing over HTTPS. Can be overriden
136 + with when fetching or pushing over HTTPS. Can be overridden
137 by the 'GIT_SSL_CAPATH' environment variable.
138
139 http.maxRequests::
Documentation/cvs-migration.txt
+1 -1
@@ -106,7 +106,7 @@ Make sure committers have a umask of at most 027, so that the directories
106 they create are writable and searchable by other group members.
107
108 Suppose this repository is now set up in /pub/repo.git on the host
109 -foo.com. Then as an individual commiter you can clone the shared
109 +foo.com. Then as an individual committer you can clone the shared
110 repository:
111
112 ------------------------------------------------
Documentation/everyday.txt
+1 -1
@@ -45,7 +45,7 @@ Everybody uses these commands to feed and care git repositories.
45
46 * gitlink:git-fsck-objects[1] to validate the repository.
47
48 - * gitlink:git-prune[1] to garbage collect crufts in the
48 + * gitlink:git-prune[1] to garbage collect cruft in the
49 repository.
50
51 * gitlink:git-repack[1] to pack loose objects for efficiency.
Documentation/git-check-ref-format.txt
+3 -2
@@ -19,8 +19,9 @@ branch head is stored under `$GIT_DIR/refs/heads` directory, and
19 a tag is stored under `$GIT_DIR/refs/tags` directory. git
20 imposes the following rules on how refs are named:
21
22 -. It could be named hierarchically (i.e. separated with slash
23 - `/`), but each of its component cannot begin with a dot `.`;
22 +. It can include slash `/` for hierarchical (directory)
23 + grouping, but no slash-separated component can begin with a
24 + dot `.`;
25
26 . It cannot have two consecutive dots `..` anywhere;
27
Documentation/git-describe.txt
+1 -1
@@ -21,7 +21,7 @@ object name of the commit.
21 OPTIONS
22 -------
23 <committish>::
24 - The object name of the comittish.
24 + The object name of the committish.
25
26 --all::
27 Instead of using only the annotated tags, use any ref
Documentation/git-name-rev.txt
+1 -1
@@ -8,7 +8,7 @@ git-name-rev - Find symbolic names for given revs
8
9 SYNOPSIS
10 --------
11 -'git-name-rev' [--tags] ( --all | --stdin | <commitish>... )
11 +'git-name-rev' [--tags] ( --all | --stdin | <committish>... )
12
13 DESCRIPTION
14 -----------
Documentation/git-p4import.txt
+1 -1
@@ -128,7 +128,7 @@ Therefore after the import you can use git to access any commit by its
128 Perforce number, eg. git show p4/327.
129
130 The tag associated with the HEAD commit is also how `git-p4import`
131 -determines if their are new changes to incrementally import from the
131 +determines if there are new changes to incrementally import from the
132 Perforce repository.
133
134 If you import from a repository with many thousands of changes
Documentation/git-read-tree.txt
+1 -1
@@ -257,7 +257,7 @@ file that does not match stage 2.
257 This is done to prevent you from losing your work-in-progress
258 changes, and mixing your random changes in an unrelated merge
259 commit. To illustrate, suppose you start from what has been
260 -commited last to your repository:
260 +committed last to your repository:
261
262 ----------------
263 $ JC=`git-rev-parse --verify "HEAD^0"`
Documentation/hooks.txt
+1 -1
@@ -100,7 +100,7 @@ update
100 This hook is invoked by `git-receive-pack` on the remote repository,
101 which is happens when a `git push` is done on a local repository.
102 Just before updating the ref on the remote repository, the update hook
103 -is invoked. It's exit status determines the success or failure of
103 +is invoked. Its exit status determines the success or failure of
104 the ref update.
105
106 The hook executes once for each ref to be updated, and takes
Documentation/tutorial.txt
+1 -1
@@ -357,7 +357,7 @@ $ git diff v2.5 HEAD # compare the current HEAD to v2.5
357 $ git branch stable v2.5 # start a new branch named "stable" based
358 # at v2.5
359 $ git reset --hard HEAD^ # reset your current branch and working
360 - # directory its state at HEAD^
360 + # directory to its state at HEAD^
361 -------------------------------------
362
363 Be careful with that last command: in addition to losing any changes