]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
dev-manual: Updated "Creating a Team Development Environment"
authorScott Rifenbark <srifenbark@gmail.com>
Thu, 15 Aug 2019 18:36:29 +0000 (11:36 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 6 Sep 2019 10:59:45 +0000 (11:59 +0100)
This section needed the wording updated.

(From yocto-docs rev: dd9e09273e9e5d5b6b43bf508f50d4d57e0dc569)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation/dev-manual/dev-manual-start.xml

index 5625dfcdd454e6fde2724087fc1774aee88fd376..59ffa49bb623cce06d07a726fe569488affcf658 100644 (file)
@@ -23,9 +23,8 @@
         It might not be immediately clear how you can use the Yocto
         Project in a team development environment, or how to scale it for a
         large team of developers.
-        One of the strengths of the Yocto Project is that it is extremely
-        flexible.
-        Thus, you can adapt it to many different use cases and scenarios.
+        You can adapt the Yocto Project to many different use cases and
+        scenarios.
         However, this flexibility could cause difficulties if you are trying
         to create a working setup that scales across a large team.
     </para>