mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jacob Stopak <>
Cc: Jacob Stopak <>
Subject: [PATCH 1/2] Documentation: clean up a few misspelled word typos
Date: Mon, 19 Sep 2022 19:45:56 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Used GNU "aspell check <filename>" to review various documentation
files with the default aspell dictionary. Ignored false-positives
between american and british english.

Signed-off-by: Jacob Stopak <>
 Documentation/MyFirstContribution.txt | 2 +-
 Documentation/MyFirstObjectWalk.txt   | 2 +-
 Documentation/git.txt                 | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt
index 1da15d9ad4..1a4be8ee0a 100644
--- a/Documentation/MyFirstContribution.txt
+++ b/Documentation/MyFirstContribution.txt
@@ -1160,7 +1160,7 @@ all named like `v2-000n-my-commit-subject.patch`. `-v2` will also format
 your patches by prefixing them with "[PATCH v2]" instead of "[PATCH]",
 and your range-diff will be prefaced with "Range-diff against v1".
-Afer you run this command, `format-patch` will output the patches to the `psuh/`
+After you run this command, `format-patch` will output the patches to the `psuh/`
 directory, alongside the v1 patches. Using a single directory makes it easy to
 refer to the old v1 patches while proofreading the v2 patches, but you will need
 to be careful to send out only the v2 patches. We will use a pattern like
diff --git a/Documentation/MyFirstObjectWalk.txt b/Documentation/MyFirstObjectWalk.txt
index 8d9e85566e..eee513e86f 100644
--- a/Documentation/MyFirstObjectWalk.txt
+++ b/Documentation/MyFirstObjectWalk.txt
@@ -534,7 +534,7 @@ the arguments to `traverse_commit_list()`.
 - `void *show_data`: A context buffer which is passed in turn to `show_commit`
   and `show_object`.
-In addition, `traverse_commit_list_filtered()` has an additional paramter:
+In addition, `traverse_commit_list_filtered()` has an additional parameter:
 - `struct oidset *omitted`: A linked-list of object IDs which the provided
   filter caused to be omitted.
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 0ef7f5e4ec..0c15ef3a8e 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -344,7 +344,7 @@ Repository, command and file interfaces
 This documentation discusses repository and command interfaces which
 users are expected to interact with directly. See `--user-formats` in
-linkgit:git-help[1] for more details on the critera.
+linkgit:git-help[1] for more details on the criteria.

  reply	other threads:[~2022-09-20  2:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  2:45 [PATCH 0/2] Fix various typos in regular and technical docs Jacob Stopak
2022-09-20  2:45 ` Jacob Stopak [this message]
2022-09-20  2:45 ` [PATCH 2/2] Documentation: clean up various typos in " Jacob Stopak
2022-09-20  3:38 ` [PATCH 0/2] Fix various typos in regular and " Eric Sunshine
2022-09-21 19:16   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).