documentation: fix apostrophe usage
Diff best viewed with --color-diff. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Elijah Newren committed
Oct 8, 2023 at 06:45 UTC
dbe33c5ad02aa9a6141abccf0821b49c46df2891
8 files changed
+8
-8
Documentation/config/index.txt
+1
-1
@@ -23,7 +23,7 @@ index.threads::
23
Specifies the number of threads to spawn when loading the index.
24
This is meant to reduce index load time on multiprocessor machines.
25
Specifying 0 or 'true' will cause Git to auto-detect the number of
26
- CPU's and set the number of threads accordingly. Specifying 1 or
26
+ CPUs and set the number of threads accordingly. Specifying 1 or
27
'false' will disable multithreading. Defaults to 'true'.
28
29
index.version::
Documentation/config/pack.txt
+1
-1
@@ -74,7 +74,7 @@ pack.threads::
74
warning. This is meant to reduce packing time on multiprocessor
75
machines. The required amount of memory for the delta search window
76
is however multiplied by the number of threads.
77
- Specifying 0 will cause Git to auto-detect the number of CPU's
77
+ Specifying 0 will cause Git to auto-detect the number of CPUs
78
and set the number of threads accordingly.
79
80
pack.indexVersion::
Documentation/config/submodule.txt
+1
-1
@@ -35,7 +35,7 @@ submodule.<name>.ignore::
35
a submodule as modified. When set to "all", it will never be considered
36
modified (but it will nonetheless show up in the output of status and
37
commit when it has been staged), "dirty" will ignore all changes
38
- to the submodules work tree and
38
+ to the submodule's work tree and
39
takes only differences between the HEAD of the submodule and the commit
40
recorded in the superproject into account. "untracked" will additionally
41
let submodules with modified tracked files in their work tree show up.
Documentation/git-mktag.txt
+1
-1
@@ -14,7 +14,7 @@ SYNOPSIS
14
DESCRIPTION
15
-----------
16
17
-Reads a tag contents on standard input and creates a tag object. The
17
+Reads a tag's contents on standard input and creates a tag object. The
18
output is the new tag's <object> identifier.
19
20
This command is mostly equivalent to linkgit:git-hash-object[1]
Documentation/git-rm.txt
+1
-1
@@ -163,7 +163,7 @@ will be staged (unless --cached or -n are used).
163
164
A submodule is considered up to date when the HEAD is the same as
165
recorded in the index, no tracked files are modified and no untracked
166
-files that aren't ignored are present in the submodules work tree.
166
+files that aren't ignored are present in the submodule's work tree.
167
Ignored files are deemed expendable and won't stop a submodule's work
168
tree from being removed.
169
Documentation/gitprotocol-pack.txt
+1
-1
@@ -137,7 +137,7 @@ an absolute path in the remote filesystem.
137
v
138
ssh user@example.com "git-upload-pack '/project.git'"
139
140
-In a "user@host:path" format URI, its relative to the user's home
140
+In a "user@host:path" format URI, it's relative to the user's home
141
directory, because the Git client will run:
142
143
git clone user@example.com:project.git
Documentation/pull-fetch-param.txt
+1
-1
@@ -71,7 +71,7 @@ refspec (or `--force`).
71
Unlike when pushing with linkgit:git-push[1], any updates outside of
72
`refs/{tags,heads}/*` will be accepted without `+` in the refspec (or
73
`--force`), whether that's swapping e.g. a tree object for a blob, or
74
-a commit for another commit that's doesn't have the previous commit as
74
+a commit for another commit that doesn't have the previous commit as
75
an ancestor etc.
76
+
77
Unlike when pushing with linkgit:git-push[1], there is no
Documentation/technical/rerere.txt
+1
-1
@@ -76,7 +76,7 @@ examples would both result in the following normalized conflict:
76
Sorting hunks
77
~~~~~~~~~~~~~
78
79
-As before, lets imagine that a common ancestor had a file with line A
79
+As before, let's imagine that a common ancestor had a file with line A
80
its early part, and line X in its late part. And then four branches
81
are forked that do these things:
82