diff options
Diffstat (limited to 'git-checkout.html')
| -rw-r--r-- | git-checkout.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/git-checkout.html b/git-checkout.html index 0f72e0a44..d9e0cf9bb 100644 --- a/git-checkout.html +++ b/git-checkout.html @@ -791,7 +791,7 @@ exactly one remote (call it <code><remote></code>) with a matching name an <div class="paragraph"><p>You could omit <code><branch></code>, in which case the command degenerates to
"check out the current branch", which is a glorified no-op with
rather expensive side-effects to show only the tracking information,
-if exists, for the current branch.</p></div>
+if it exists, for the current branch.</p></div>
</dd>
<dt class="hdlist1">
<em>git checkout</em> -b|-B <new-branch> [<start-point>]
@@ -1594,7 +1594,7 @@ checkout.workers all commands that perform checkout. E.g. checkout, clone, reset,
sparse-checkout, etc.
</p>
-<div class="paragraph"><p>Note: parallel checkout usually delivers better performance for repositories
+<div class="paragraph"><p>Note: Parallel checkout usually delivers better performance for repositories
located on SSDs or over NFS. For repositories on spinning disks and/or machines
with a small number of cores, the default sequential checkout often performs
better. The size and compression level of a repository might also influence how
@@ -1607,7 +1607,7 @@ checkout.thresholdForParallelism <p>
When running parallel checkout with a small number of files, the cost
of subprocess spawning and inter-process communication might outweigh
- the parallelization gains. This setting allows to define the minimum
+ the parallelization gains. This setting allows you to define the minimum
number of files for which parallel checkout should be attempted. The
default is 100.
</p>
@@ -1633,7 +1633,7 @@ checkout.thresholdForParallelism <div id="footer">
<div id="footer-text">
Last updated
- 2023-10-02 12:46:05 PDT
+ 2023-10-23 14:43:46 PDT
</div>
</div>
</body>
|