public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "quentin.schulz@theobroma-systems.com"
	<quentin.schulz@theobroma-systems.com>,
	"than.matos+bitbake@gmail.com" <than.matos+bitbake@gmail.com>,
	"bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: RE: [docs] [bitbake-devel] Typo on the BitBake Documentation
Date: Tue, 3 Jan 2023 17:04:29 +0000	[thread overview]
Message-ID: <4ddb01e14e304e96b10598b72ae05911@axis.com> (raw)
In-Reply-To: <10502f22-575d-3917-374a-8c60a7e9bf32@theobroma-systems.com>

> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Quentin Schulz via lists.yoctoproject.org
> Sent: den 3 januari 2023 16:03
> To: than.matos+bitbake@gmail.com; bitbake-devel@lists.openembedded.org
> Cc: YP docs mailing list <docs@lists.yoctoproject.org>
> Subject: Re: [docs] [bitbake-devel] Typo on the BitBake Documentation
> 
> Hi,
> 
> On 12/27/22 22:00, than.matos+bitbake@gmail.com wrote:
> > I'm not sure if this is the right place to report and if I'm writing in
> > the wrong place, please feel free to remove this post.
> 
> This is actually quite a good guess, just adding the yocto-docs ML to Cc
> recipients to notify people generally interested in docs.
> 
> > I'm also not a native of English, but I think there is a typo on the
> > BitBake documentation page.
> >
> >> You can obtain BitBake several different ways:
> >
> > I feel like there is a missing `in` before the word `several`.
> 
> Both feel odd to me, your suggestion more than the current phrasing
> though. I'm not a native speaker either you'd have guessed :)
> 
> > Sorry to bother you!
> 
> Thanks for taking the time to report this, I'll let native speakers
> chime in and decide for us :)

Well, I am not a native English speaker either, but I agree with Than 
that "in several" would improve the sentence. Alternatively, it can be 
rewritten as:

  There are several different ways that BitBake can be obtained:

> 
> Cheers,
> Quentin

//Peter


  reply	other threads:[~2023-01-03 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bWm9.1672174859052782246.2l5k@lists.openembedded.org>
2023-01-03 15:03 ` [bitbake-devel] Typo on the BitBake Documentation Quentin Schulz
2023-01-03 17:04   ` Peter Kjellerstedt [this message]
     [not found] ` <dee6ed9a3beabd5cd18042c61b0dfd31c2c4ff8e.camel@linuxfoundation.org>
2023-01-04  9:09   ` Michael Opdenacker

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=4ddb01e14e304e96b10598b72ae05911@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=than.matos+bitbake@gmail.com \
    /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