mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Mark Rushakoff via GitGitGadget" <>
Cc: Junio C Hamano <>
Subject: [PATCH 0/1] Fix two documentation typos
Date: Fri, 02 Aug 2019 22:33:50 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)

I noticed a couple typos while reading through some manpages. 

First was "...if it is does not..." which just contained an extraneous "is".

Then I noticed a "can not" and updated that and other occurrences in
Documentation to cannot. The glossary sentence with "can not" was
"Consequently, an object can not be changed." To me, that reads like "it is
permissible to not change an object, but it is possible that an object may
be changed." Switching to "cannot" makes a stronger assertion that it is
impossible to change an object.

There are also two error messages, "can not move directory into itself" and
"Can not do reflog for '%s': %s\n", which I chose to not modify in this
patch. I am happy to s/an not/annot/ those as a separate change if it is
acceptable to change the wording on an error message like that.

Mark Rushakoff (1):
  doc: typo: s/can not/cannot/ and s/is does/does/

 Documentation/config/transfer.txt             | 2 +-
 Documentation/git-cvsserver.txt               | 2 +-
 Documentation/git-fetch.txt                   | 4 ++--
 Documentation/git-pull.txt                    | 2 +-
 Documentation/glossary-content.txt            | 2 +-
 Documentation/technical/api-ref-iteration.txt | 2 +-
 6 files changed, 7 insertions(+), 7 deletions(-)

base-commit: 7c20df84bd21ec0215358381844274fa10515017
Fetch-It-Via: git fetch pr-304/mark-rushakoff/docs-typofix-v1

             reply	other threads:[~2019-08-03  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03  5:33 Mark Rushakoff via GitGitGadget [this message]
2019-08-03  5:33 ` [PATCH 1/1] doc: typo: s/can not/cannot/ and s/is does/does/ Mark Rushakoff via GitGitGadget
2019-08-03 14:48 ` [PATCH 0/1] Fix two documentation typos Junio C Hamano
2019-08-03 23:59   ` Jeff King
2019-08-05 17:04     ` 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).