diff mbox series

doc: user-manual: intro: reword a sentence

Message ID 20230103-typo-202301-v1-0-bb5014c684d0@theobroma-systems.com
State New
Headers show
Series doc: user-manual: intro: reword a sentence | expand

Commit Message

Quentin Schulz Jan. 3, 2023, 5:59 p.m. UTC
It's been reported this sentence is a bit odd, so let's reword it.

Reported-by: than.matos+bitbake@gmail.com
Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Quentin Schulz <foss+yocto@0leil.net>
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
---
reword odd sentence

Cc: docs@lists.yoctoproject.org
Cc: bitbake-devel@lists.openembedded.org
---
 doc/bitbake-user-manual/bitbake-user-manual-intro.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


---
base-commit: 367a83ed46c7fbcdd06579b6cc3a6e48a89ca7fb
change-id: 20230103-typo-202301-c5f8f3571209

Best regards,
-- 
Quentin Schulz <quentin.schulz@theobroma-systems.com>

Comments

Michael Opdenacker Jan. 3, 2023, 6:49 p.m. UTC | #1
Am 03.01.23 um 18:59 schrieb Quentin Schulz via lists.yoctoproject.org:
> It's been reported this sentence is a bit odd, so let's reword it.
>
> Reported-by: than.matos+bitbake@gmail.com
> Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: Quentin Schulz <foss+yocto@0leil.net>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> ---
> reword odd sentence
>
> Cc: docs@lists.yoctoproject.org
> Cc: bitbake-devel@lists.openembedded.org
> ---
>   doc/bitbake-user-manual/bitbake-user-manual-intro.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> index 35ffb88b0..797feb516 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> @@ -275,7 +275,7 @@ simple as ``busybox_%.bbappend`` to be entirely version independent.
>   Obtaining BitBake
>   =================
>   
> -You can obtain BitBake several different ways:
> +There are several different ways that BitBake can be obtained:
>   
>   -  **Cloning BitBake:** Using Git to clone the BitBake source code
>      repository is the recommended method for obtaining BitBake. Cloning
>
> ---
> base-commit: 367a83ed46c7fbcdd06579b6cc3a6e48a89ca7fb
> change-id: 20230103-typo-202301-c5f8f3571209
>
> Best regards,


Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Thanks for the patch!
Cheers
Michael.
diff mbox series

Patch

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
index 35ffb88b0..797feb516 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
@@ -275,7 +275,7 @@  simple as ``busybox_%.bbappend`` to be entirely version independent.
 Obtaining BitBake
 =================
 
-You can obtain BitBake several different ways:
+There are several different ways that BitBake can be obtained:
 
 -  **Cloning BitBake:** Using Git to clone the BitBake source code
    repository is the recommended method for obtaining BitBake. Cloning