Documentation: fix various repeat word typos
Inspired by 24966cd982 ("doc: fix repeated words", 08-09-2019), I ran "egrep -R "\<([a-zA-Z]+)\> \<\1\>" ./Documentation/*" to find current cases of repeated words such as "the the" that were quite clearly typos. There were many false positives reported, such as "really really" or valid uses of "that that" which I left alone. Signed-off-by: Jacob Stopak <jacob@initialcommit.io> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jacob Stopak committed
Sep 11, 2022 at 03:23 UTC
c9dba103dd1dc75a27edca3e2420be5a1b266e17
6 files changed
+6
-6
Documentation/CodingGuidelines
+1
-1
@@ -606,7 +606,7 @@ Writing Documentation:
606
avoidance of gendered pronouns.
607
608
- When it becomes awkward to stick to this style, prefer "you" when
609
- addressing the the hypothetical user, and possibly "we" when
609
+ addressing the hypothetical user, and possibly "we" when
610
discussing how the program might react to the user. E.g.
611
612
You can use this option instead of --xyz, but we might remove
Documentation/config/transfer.txt
+1
-1
@@ -13,7 +13,7 @@ Note that this is currently limited to detecting credentials in
13
You might want to enable this to prevent inadvertent credentials
14
exposure, e.g. because:
15
+
16
-* The OS or system where you're running git may not provide way way or
16
+* The OS or system where you're running git may not provide a way or
17
otherwise allow you to configure the permissions of the
18
configuration file where the username and/or password are stored.
19
* Even if it does, having such data stored "at rest" might expose you
Documentation/git-bundle.txt
+1
-1
@@ -42,7 +42,7 @@ BUNDLE FORMAT
42
Bundles are `.pack` files (see linkgit:git-pack-objects[1]) with a
43
header indicating what references are contained within the bundle.
44
45
-Like the the packed archive format itself bundles can either be
45
+Like the packed archive format itself bundles can either be
46
self-contained, or be created using exclusions.
47
See the "OBJECT PREREQUISITES" section below.
48
Documentation/git-update-index.txt
+1
-1
@@ -420,7 +420,7 @@ as `switch`, `pull`, `merge`) will avoid writing these files.
420
However, these commands will sometimes write these files anyway in
421
important cases such as conflicts during a merge or rebase. Git
422
commands will also avoid treating the lack of such files as an
423
-intentional deletion; for example `git add -u` will not not stage a
423
+intentional deletion; for example `git add -u` will not stage a
424
deletion for these files and `git commit -a` will not make a commit
425
deleting them either.
426
Documentation/git-upload-pack.txt
+1
-1
@@ -40,7 +40,7 @@ OPTIONS
40
Used by linkgit:git-http-backend[1] to serve up
41
`$GIT_URL/info/refs?service=git-upload-pack` requests. See
42
"Smart Clients" in linkgit:gitprotocol-http[5] and "HTTP
43
- Transport" in in the linkgit:gitprotocol-v2[5]
43
+ Transport" in the linkgit:gitprotocol-v2[5]
44
documentation. Also understood by
45
linkgit:git-receive-pack[1].
46
Documentation/technical/remembering-renames.txt
+1
-1
@@ -20,7 +20,7 @@ Outline:
20
3. Why any rename on MERGE_SIDE1 in any given pick is _almost_ always also
21
a rename on MERGE_SIDE1 for the next pick
22
23
- 4. A detailed description of the the counter-examples to #3.
23
+ 4. A detailed description of the counter-examples to #3.
24
25
5. Why the special cases in #4 are still fully reasonable to use to pair
26
up files for three-way content merging in the merge machinery, and why