docs: typofixes
These were found with an automated CLI tool [1]. Only the "Documentation" subfolder (and not source code files) was considered because the docs are user-facing. [1]: https://crates.io/crates/typos-cli Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Linus Arver committed
Jun 7, 2023 at 19:26 UTC
548afb0d9a5a15e538fbf7e01fafbc27691365f1
12 files changed
+13
-13
Documentation/CodingGuidelines
+1
-1
@@ -687,7 +687,7 @@ Writing Documentation:
687
Do: [-q | --quiet]
688
Don't: [-q|--quiet]
689
690
- Don't use spacing around "|" tokens when they're used to seperate the
690
+ Don't use spacing around "|" tokens when they're used to separate the
691
alternate arguments of an option:
692
Do: --track[=(direct|inherit)]
693
Don't: --track[=(direct | inherit)]
Documentation/config.txt
+1
-1
@@ -182,7 +182,7 @@ included, Git breaks the cycle by prohibiting these files from affecting
182
the resolution of these conditions (thus, prohibiting them from
183
declaring remote URLs).
184
+
185
-As for the naming of this keyword, it is for forwards compatibiliy with
185
+As for the naming of this keyword, it is for forwards compatibility with
186
a naming scheme that supports more variable-based include conditions,
187
but currently Git only supports the exact keyword described above.
188
Documentation/git-cvsserver.txt
+1
-1
@@ -118,7 +118,7 @@ for example:
118
myuser:$5$.NqmNH1vwfzGpV8B$znZIcumu1tNLATgV2l6e1/mY8RzhUDHMOaVOeL1cxV3
119
------
120
You can use the 'htpasswd' facility that comes with Apache to make these
121
-files, but only with the -d option (or -B if your system suports it).
121
+files, but only with the -d option (or -B if your system supports it).
122
123
Preferably use the system specific utility that manages password hash
124
creation in your platform (e.g. mkpasswd in Linux, encrypt in OpenBSD or
Documentation/git-describe.txt
+2
-2
@@ -140,7 +140,7 @@ at the end.
140
141
The number of additional commits is the number
142
of commits which would be displayed by "git log v1.0.4..parent".
143
-The hash suffix is "-g" + an unambigous abbreviation for the tip commit
143
+The hash suffix is "-g" + an unambiguous abbreviation for the tip commit
144
of parent (which was `2414721b194453f058079d897d13c4e377f92dc6`). The
145
length of the abbreviation scales as the repository grows, using the
146
approximate number of objects in the repository and a bit of math
@@ -203,7 +203,7 @@ BUGS
203
204
Tree objects as well as tag objects not pointing at commits, cannot be described.
205
When describing blobs, the lightweight tags pointing at blobs are ignored,
206
-but the blob is still described as <committ-ish>:<path> despite the lightweight
206
+but the blob is still described as <commit-ish>:<path> despite the lightweight
207
tag being favorable.
208
209
GIT
Documentation/git-format-patch.txt
+1
-1
@@ -245,7 +245,7 @@ populated with placeholder text.
245
or "--reroll-count=4rev2" are allowed), but the downside of
246
using such a reroll-count is that the range-diff/interdiff
247
with the previous version does not state exactly which
248
- version the new interation is compared against.
248
+ version the new iteration is compared against.
249
250
--to=<email>::
251
Add a `To:` header to the email headers. This is in addition
Documentation/git-ls-tree.txt
+1
-1
@@ -145,7 +145,7 @@ FIELD NAMES
145
-----------
146
147
Various values from structured fields can be used to interpolate
148
-into the resulting output. For each outputing line, the following
148
+into the resulting output. For each outputting line, the following
149
names can be used:
150
151
objectmode::
Documentation/git-mktag.txt
+1
-1
@@ -33,7 +33,7 @@ from warnings to errors (so e.g. a missing "tagger" line is an error).
33
34
Extra headers in the object are also an error under mktag, but ignored
35
by linkgit:git-fsck[1]. This extra check can be turned off by setting
36
-the appropriate `fsck.<msg-id>` varible:
36
+the appropriate `fsck.<msg-id>` variable:
37
38
git -c fsck.extraHeaderEntry=ignore mktag <my-tag-with-headers
39
Documentation/git-sparse-checkout.txt
+1
-1
@@ -286,7 +286,7 @@ patterns in non-cone mode has a number of shortcomings:
286
problem above? Also, if it suggests paths, what if the user has a
287
file or directory that begins with either a '!' or '#' or has a '*',
288
'\', '?', '[', or ']' in its name? And if it suggests paths, will
289
- it complete "/pro" to "/proc" (in the root filesytem) rather than to
289
+ it complete "/pro" to "/proc" (in the root filesystem) rather than to
290
"/progress.txt" in the current directory? (Note that users are
291
likely to want to start paths with a leading '/' in non-cone mode,
292
for the same reason that .gitignore files often have one.)
Documentation/git-stash.txt
+1
-1
@@ -366,7 +366,7 @@ only the commit ends-up being in the stash and not on the current branch.
366
# ... hack hack hack ...
367
$ git add --patch foo # add unrelated changes to the index
368
$ git stash push --staged # save these changes to the stash
369
-# ... hack hack hack, finish curent changes ...
369
+# ... hack hack hack, finish current changes ...
370
$ git commit -m 'Massive' # commit fully tested changes
371
$ git switch fixup-branch # switch to another branch
372
$ git stash pop # to finish work on the saved changes
Documentation/gitweb.txt
+1
-1
@@ -503,7 +503,7 @@ repositories, you can configure Apache like this:
503
504
The above configuration expects your public repositories to live under
505
`/pub/git` and will serve them as `http://git.domain.org/dir-under-pub-git`,
506
-both as clonable Git URL and as browseable gitweb interface. If you then
506
+both as clonable Git URL and as browsable gitweb interface. If you then
507
start your linkgit:git-daemon[1] with `--base-path=/pub/git --export-all`
508
then you can even use the `git://` URL with exactly the same path.
509
Documentation/technical/remembering-renames.txt
+1
-1
@@ -664,7 +664,7 @@ skip-irrelevant-renames optimization means we sometimes don't detect
664
renames for any files within a directory that was renamed, in which
665
case we will not have been able to detect any rename for the directory
666
itself. In such a case, we do not know whether the directory was
667
-renamed; we want to be careful to avoid cacheing some kind of "this
667
+renamed; we want to be careful to avoid caching some kind of "this
668
directory was not renamed" statement. If we did, then a subsequent
669
commit being rebased could add a file to the old directory, and the
670
user would expect it to end up in the correct directory -- something
Documentation/urls-remotes.txt
+1
-1
@@ -35,7 +35,7 @@ config file would appear like this:
35
The `<pushurl>` is used for pushes only. It is optional and defaults
36
to `<URL>`. Pushing to a remote affects all defined pushurls or to all
37
defined urls if no pushurls are defined. Fetch, however, will only
38
-fetch from the first defined url if muliple urls are defined.
38
+fetch from the first defined url if multiple urls are defined.
39
40
Named file in `$GIT_DIR/remotes`
41
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~