From: Scott Rifenbark Date: Thu, 15 Aug 2019 18:36:29 +0000 (-0700) Subject: dev-manual: Updated "Creating a Team Development Environment" X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7f04f85f71f3a07be093625fb789547240dd4dc8;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git dev-manual: Updated "Creating a Team Development Environment" This section needed the wording updated. (From yocto-docs rev: dd9e09273e9e5d5b6b43bf508f50d4d57e0dc569) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 5625dfcdd45..59ffa49bb62 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -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.