linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jules Maselbas <jmaselbas@kalray.eu>, linux-kernel@vger.kernel.org
Cc: Jules Maselbas <jmaselbas@kalray.eu>,
	Randy Dunlap <rdunlap@infradead.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] Remove duplicated words across the whole documentation
Date: Mon, 29 Aug 2022 10:30:57 -0600	[thread overview]
Message-ID: <87wnarovum.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220826163458.1142-1-jmaselbas@kalray.eu>

Jules Maselbas <jmaselbas@kalray.eu> writes:

> Remove duplicated words (the, at, be ...) across the whole documentation.
> In some cases the duplicated words are replaced by something that makes
> more sense, for instance: "be be" is replaced by "can be" when possible.
>
> There are likely more duplicated words to be found.
>
> CC: Randy Dunlap <rdunlap@infradead.org>
> CC: Bagas Sanjaya <bagasdotme@gmail.com>
> CC: Jonathan Corbet <corbet@lwn.net>
> CC: linux-doc@vger.kernel.org
> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
> ---
> in v3:
>  as suggested by Randy Dunlap:
>  - remove duplicated 'The the '
>  - remove duplicated 'at at ' (some are replaced by 'at a ')
>  - remove duplicated be, is, to, we, on ...
> in v2:
>  - also remove the second 'the' in one sentence as suggested by
>    Bagas Sanjaya
>
>  Documentation/RCU/checklist.rst                               | 2 +-
>  Documentation/admin-guide/kdump/vmcoreinfo.rst                | 2 +-
>  Documentation/admin-guide/media/vivid.rst                     | 2 +-
>  Documentation/bpf/instruction-set.rst                         | 2 +-
>  Documentation/bpf/map_cgroup_storage.rst                      | 4 ++--
>  Documentation/core-api/cpu_hotplug.rst                        | 3 +--
>  Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml  | 4 ++--
>  .../devicetree/bindings/arm/tegra/nvidia,tegra20-ahb.txt      | 2 +-

When you redo the patch to reflect the other comments, please split the
devicetree changes into a separate patch.  I don't handle devicetree
stuff, so that will need to go via a separate path.

Thanks,

jon

      parent reply	other threads:[~2022-08-29 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  9:52 [PATCH] Documentation: Fix repeated words in documentation Jules Maselbas
2022-08-26 12:45 ` Bagas Sanjaya
2022-08-26 14:33 ` [PATCH v2] Remove duplicated 'the' across the whole documentation Jules Maselbas
2022-08-26 15:47   ` Randy Dunlap
2022-08-26 16:34   ` [PATCH v3] Remove duplicated words " Jules Maselbas
2022-08-26 16:40     ` Conor.Dooley
2022-08-26 16:50       ` Jules Maselbas
2022-08-26 16:56     ` [PATCH v4] " Jules Maselbas
2022-08-26 23:06       ` Randy Dunlap
2022-08-29  9:26         ` Jules Maselbas
2022-08-29  9:29       ` [PATCH v5] " Jules Maselbas
2022-08-29 17:23         ` Conor Dooley
2022-08-29 18:58         ` Randy Dunlap
2022-08-29 16:30     ` Jonathan Corbet [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=87wnarovum.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=jmaselbas@kalray.eu \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
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 NNTP newsgroup(s).