Re: [PATCH 1/3] Documentation/technical: fix a typo

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 20, 2024, 20:12 UTC
Message-ID: <xmqqbk0if5jv.fsf@gitster.g>
In-Reply-To: <20240920082815.8192-1-algonell@gmail.com>

Andrew Kreimer <algonell@gmail.com> writes:

Show 17 quoted lines

> Fix a typo in documentation.
>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> ---
>  Documentation/technical/sparse-checkout.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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,

As a general rule, unless we are doing codewide sweep to use a single word in our glossary to refer to the same thing, or something, we should honor author's preference, when it is already written and it is not blatantly wrong.

  https://www.collinsdictionary.com/us/dictionary/english/publically

I am inclined to say that we should keep it as written, but I am not a native speaker, so please cite a source that tells what is written is blatantly wrong to help me accept this patch.

Thanks.