threads / patch / 48226

patch, 2 partsDocumentation: Normalize spelling of 'normalised'

Subject: [PATCH 2/2] Documentation: Normalize spelling of 'normalised'

## tl;dr

3 messages between Apr 5, 2018 and Apr 5, 2018. Diffs are folded; open one to read it.

replies: 2people: 2as markdown or json

Elijah Newren· Apr 5, 2018, 17:20 UTC · lore

[PATCH 1/2] Documentation: Fix several one-character-off spelling errors

Signed-off-by: Elijah Newren <newren@gmail.com>
---
 Documentation/diff-options.txt                    | 4 ++--
 Documentation/git-fetch-pack.txt                  | 2 +-
 Documentation/git-for-each-ref.txt                | 2 +-
 Documentation/git-send-email.txt                  | 2 +-
 Documentation/git-status.txt                      | 2 +-
 Documentation/technical/api-directory-listing.txt | 2 +-
 6 files changed, 7 insertions(+), 7 deletions(-)
Show changes to 6 files +7 −7

Documentation/diff-options.txt, Documentation/git-fetch-pack.txt, Documentation/git-for-each-ref.txt, Documentation/git-send-email.txt, Documentation/git-status.txt, Documentation/technical/api-directory-listing.txt

diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
index e3a44f03cd..f466600972 100644
--- a/Documentation/diff-options.txt
+++ b/Documentation/diff-options.txt
@@ -568,7 +568,7 @@ the normal order.
 --
 +
 Patterns have the same syntax and semantics as patterns used for
-fnmantch(3) without the FNM_PATHNAME flag, except a pathname also
+fnmatch(3) without the FNM_PATHNAME flag, except a pathname also
 matches a pattern if removing any number of the final pathname
 components matches the pattern.  For example, the pattern "`foo*bar`"
 matches "`fooasdfbar`" and "`foo/bar/baz/asdf`" but not "`foobarx`".
@@ -592,7 +592,7 @@ endif::git-format-patch[]
 	Treat all files as text.
 
 --ignore-cr-at-eol::
-	Ignore carrige-return at the end of line when doing a comparison.
+	Ignore carriage-return at the end of line when doing a comparison.
 
 --ignore-space-at-eol::
 	Ignore changes in whitespace at EOL.
diff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt
index f7ebe36a7b..c975884793 100644
--- a/Documentation/git-fetch-pack.txt
+++ b/Documentation/git-fetch-pack.txt
@@ -88,7 +88,7 @@ be in a separate packet, and the list must end with a flush packet.
 	infinite even if there is an ancestor-chain that long.
 
 --shallow-since=<date>::
-	Deepen or shorten the history of a shallow'repository to
+	Deepen or shorten the history of a shallow repository to
 	include all reachable commits after <date>.
 
 --shallow-exclude=<revision>::
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index dffa14a795..085d177d97 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -121,7 +121,7 @@ refname::
 	stripping with positive <N>, or it becomes the full refname if
 	stripping with negative <N>.  Neither is an error.
 +
-`strip` can be used as a synomym to `lstrip`.
+`strip` can be used as a synonym to `lstrip`.
 
 objecttype::
 	The type of the object (`blob`, `tree`, `commit`, `tag`).
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 71ef97ba9b..cd149e7056 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -255,7 +255,7 @@ must be used for each option.
 
 --batch-size=<num>::
 	Some email servers (e.g. smtp.163.com) limit the number emails to be
-	sent per session (connection) and this will lead to a faliure when
+	sent per session (connection) and this will lead to a failure when
 	sending many messages.  With this option, send-email will disconnect after
 	sending $<num> messages and wait for a few seconds (see --relogin-delay)
 	and reconnect, to work around such a limit.  You may want to
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index 6c230c0c72..c16e27e63d 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -113,7 +113,7 @@ The possible options are:
 	- 'matching'    - Shows ignored files and directories matching an
 			  ignore pattern.
 +
-When 'matching' mode is specified, paths that explicity match an
+When 'matching' mode is specified, paths that explicitly match an
 ignored pattern are shown. If a directory matches an ignore pattern,
 then it is shown, but not paths contained in the ignored directory. If
 a directory does not match an ignore pattern, but all contents are
diff --git a/Documentation/technical/api-directory-listing.txt b/Documentation/technical/api-directory-listing.txt
index 7fae00f44f..4f44ca24f6 100644
--- a/Documentation/technical/api-directory-listing.txt
+++ b/Documentation/technical/api-directory-listing.txt
@@ -53,7 +53,7 @@ The notable options are:
 	not be returned even if all of its contents are ignored. In
 	this case, the contents are returned as individual entries.
 +
-If this is set, files and directories that explicity match an ignore
+If this is set, files and directories that explicitly match an ignore
 pattern are reported. Implicity ignored directories (directories that
 do not match an ignore pattern, but whose contents are all ignored)
 are not reported, instead all of the contents are reported.
-- 
2.17.0.7.g0b50f94d69
Elijah Newren· Apr 5, 2018, 17:20 UTC · re: Elijah Newren · lore

This could be a localization issue, but we had about four dozen "normalize"s (or variants, e.g. normalized, renormalize, etc.), and only one "normalised" (no other variants), so normalize normalised into normalized.

Signed-off-by: Elijah Newren <newren@gmail.com>
---
 Documentation/git-mktree.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Show changes to Documentation/git-mktree.txt +1 −1
diff --git a/Documentation/git-mktree.txt b/Documentation/git-mktree.txt
index c3616e7711..27fe2b32e1 100644
--- a/Documentation/git-mktree.txt
+++ b/Documentation/git-mktree.txt
@@ -14,7 +14,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 Reads standard input in non-recursive `ls-tree` output format, and creates
-a tree object.  The order of the tree entries is normalised by mktree so
+a tree object.  The order of the tree entries is normalized by mktree so
 pre-sorting the input is not required.  The object name of the tree object
 built is written to the standard output.
 
-- 
2.17.0.7.g0b50f94d69
Stefan Beller· Apr 5, 2018, 17:49 UTC · re: Elijah Newren · lore

Re: [PATCH 2/2] Documentation: Normalize spelling of 'normalised'

On Thu, Apr 5, 2018 at 10:20 AM, Elijah Newren <newren@gmail.com> wrote:
> This could be a localization issue, but we had about four dozen
> "normalize"s (or variants, e.g. normalized, renormalize, etc.), and only
> one "normalised" (no other variants), so normalize normalised into
> normalized.
This and the previous patch are
Reviewed-by: Stefan Beller <sbeller@google.com>
Show 21 quoted lines
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
>  Documentation/git-mktree.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-mktree.txt b/Documentation/git-mktree.txt
> index c3616e7711..27fe2b32e1 100644
> --- a/Documentation/git-mktree.txt
> +++ b/Documentation/git-mktree.txt
> @@ -14,7 +14,7 @@ SYNOPSIS
>  DESCRIPTION
>  -----------
>  Reads standard input in non-recursive `ls-tree` output format, and creates
> -a tree object.  The order of the tree entries is normalised by mktree so
> +a tree object.  The order of the tree entries is normalized by mktree so
>  pre-sorting the input is not required.  The object name of the tree object
>  built is written to the standard output.
>
> --
> 2.17.0.7.g0b50f94d69
>

← back to recent threads