aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-09-25 18:24:50 -0700
committerJunio C Hamano <gitster@pobox.com>2024-09-25 18:24:51 -0700
commit4f454e14b5bd3a15f54ae1d9303b2b4bbd6d9b80 (patch)
tree6a6b20e3ad1035aab8cc61e43a7e55df4ed34451
parentMerge branch 'ak/typofix-builtins' (diff)
parentDocumentation/technical: fix a typo (diff)
downloadgit-4f454e14b5bd3a15f54ae1d9303b2b4bbd6d9b80.tar.gz
git-4f454e14b5bd3a15f54ae1d9303b2b4bbd6d9b80.zip
Merge branch 'ak/doc-sparse-co-typofix'
Docfix. * ak/doc-sparse-co-typofix: Documentation/technical: fix a typo
-rw-r--r--Documentation/technical/sparse-checkout.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt
index fa0d01cbda..d968659354 100644
--- a/Documentation/technical/sparse-checkout.txt
+++ b/Documentation/technical/sparse-checkout.txt
@@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch
checkouts and switches write fewer things, knowing the VFS will lazily
write the rest on an as-needed basis).
-Since there is no publically available VFS-related code for folks to try,
+Since there is no publicly available VFS-related code for folks to try,
the number of folks who can test such a usecase is limited.
The primary reason to note the Behavior C usecase is that as we fix things