All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 2/4] doc: Fix typos and grammar
Date: Mon, 1 Jun 2026 15:57:33 +0200	[thread overview]
Message-ID: <20260601135733.GC3391768@pevik> (raw)
In-Reply-To: <20260601-doc_update-v1-2-b0f59834fbae@suse.com>

Hi Andrea,

> Fix typos (reStructedText, ignorcing, clonned, likehood,
> evironment, asses, effected) and grammar (setup -> set up,
> permits to, it's -> its, be ran -> be run, will works,
> "be be" -> "be", result to -> resort to, yielded into ->
> led to, does not exists, has to be -> have to be) across
> the documentation tree.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

Good catch, thank you!

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-06-01 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  9:52 [LTP] [PATCH 0/4] Fix documentation issues Andrea Cervesato
2026-06-01  9:52 ` [LTP] [PATCH 1/4] doc: Fix broken references and outdated content Andrea Cervesato
2026-06-01 11:58   ` Cyril Hrubis
2026-06-01 13:55   ` Petr Vorel
2026-06-01  9:52 ` [LTP] [PATCH 2/4] doc: Fix typos and grammar Andrea Cervesato
2026-06-01 12:10   ` Cyril Hrubis
2026-06-01 13:57   ` Petr Vorel [this message]
2026-06-01  9:52 ` [LTP] [PATCH 3/4] include: Fix kernel-doc warnings in header comments Andrea Cervesato
2026-06-01 14:09   ` Petr Vorel
2026-06-02  9:04     ` Cyril Hrubis
2026-06-02  9:16       ` Andrea Cervesato via ltp
2026-06-01  9:52 ` [LTP] [PATCH 4/4] doc: Fix incorrect struct tst_test field references Andrea Cervesato
2026-06-01 14:10   ` Petr Vorel
2026-06-02  9:31 ` [LTP] [PATCH 0/4] Fix documentation issues Andrea Cervesato via ltp

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=20260601135733.GC3391768@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.