diff --git a/documentation/getting-started/getting-started-development-environment.xml b/documentation/getting-started/getting-started-development-environment.xml
index 9bbd8e062f..7bcf87ffd9 100644
--- a/documentation/getting-started/getting-started-development-environment.xml
+++ b/documentation/getting-started/getting-started-development-environment.xml
@@ -37,7 +37,7 @@
Open source projects conceptually have differing concurrent agendas,
approaches, and production.
These facets of the development process can come from anyone in the
- public (community) that has a stake in the software project.
+ public (community) who has a stake in the software project.
The open source environment contains new copyright, licensing, domain,
and consumer issues that differ from the more traditional development
environment.
diff --git a/documentation/getting-started/getting-started-yp-intro.xml b/documentation/getting-started/getting-started-yp-intro.xml
index f39cd70c74..6941db68b9 100644
--- a/documentation/getting-started/getting-started-yp-intro.xml
+++ b/documentation/getting-started/getting-started-yp-intro.xml
@@ -174,7 +174,7 @@
Binary Reproducibility:
- The Yocto Project you to be very specific about
+ The Yocto Project allows you to be very specific about
dependencies and achieves very high percentages of
binary reproducibility (e.g. 99.8% for
core-image-minimal).
@@ -186,7 +186,7 @@
License Manifest:
The Yocto Project provides a license manifest for
- review by people that need to track the use of open
+ review by people who need to track the use of open
source licenses (e.g.legal teams).
@@ -224,7 +224,7 @@
Project Workflow Could Be Confusing:
The Yocto Project workflow could be confusing if you
- used to traditional desktop and server software
+ are used to traditional desktop and server software
development.
In a desktop development environment, mechanisms exist
to easily pull and install new packages, which are
@@ -546,7 +546,7 @@
The main purpose of the system is to help you
manage the recipes you maintain and to offer a dynamic
overview of the project.
- The Recipe Reporting System tracks is built on top
+ The Recipe Reporting System is built on top
the of OpenEmbedded Metadata Index, which is a website
that indexes layers for the OpenEmbedded build system.
@@ -883,8 +883,10 @@
familiar shell of a supported Linux distribution.
For information on how to set up a Build Host on
- a system running Linux as its native operating system, see
- TBD.
+ a system running Linux as its native operating system,
+ see the
+ "Setting Up a Native Linux Host"
+ section in the Yocto Project Development Tasks Manual.
CROss PlatformS (CROPS):
@@ -909,7 +911,9 @@
on a system natively running Linux.
For information on how to set up a Build Host with
- CROPS, see TBD.
+ CROPS, see the
+ "Setting Up to Use CROss PlatformS (CROPS)"
+ section in the Yocto Project Development Tasks Manual.
Toaster:
@@ -969,12 +973,12 @@
Poky is a combined repository of BitBake, OpenEmbedded-Core
- (found in meta),
+ (which is found in meta),
meta-poky,
meta-yocto-bsp, and documentation provided
all together and known to work well together.
- You can view the Poky repository as part of the
- Source Repositories.
+ You can view these items that make up the Poky repository in the
+ Source Repositories.
If you are interested in all the contents of the
poky Git repository, see the
@@ -1250,7 +1254,7 @@
developed by the OpenEmbedded community that has been
pared down into a smaller, core set of continuously
validated recipes.
- The result is a tightly controlled and an quality-assured
+ The result is a tightly controlled and quality-assured
core set of recipes.
You can see the Metadata in the
@@ -1285,8 +1289,7 @@
Poky:
- Poky, which is pronounced Pock-ee,
- is a reference embedded distribution and a reference
+ Poky is a reference embedded distribution and a reference
test configuration.
Poky provides the following: