diff options
| author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2024-02-09 17:48:06 +0100 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2024-03-13 03:59:26 -1000 |
| commit | d241202fa1f02e537c29e4ec5bbba945f957ede5 (patch) | |
| tree | 416c32f0e92c44436b30a38303653d487cfc0560 /documentation/dev-manual/start.rst | |
| parent | 74ed43b221c8459613112714cb1e137712a661b5 (diff) | |
| download | poky-d241202fa1f02e537c29e4ec5bbba945f957ede5.tar.gz | |
manuals: suppress excess use of "following" word
To simplify the style, replace "Following is" and "Following are"
by "here is" and "here are", sounding more natural.
In some cases, also go further by simplifying "Here are/is xxx"
by "xxx are/is" when the "are" or "is" are not two far at
the end of the sentence.
In some cases too, completely remove the sentence, when
it's redundant with the preceding title.
(From yocto-docs rev: da1cbd7083238657aaeaea16841b24531c86298e)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
CC: Daniel Ammann <daniel.ammann@bytesatwork.ch>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'documentation/dev-manual/start.rst')
| -rw-r--r-- | documentation/dev-manual/start.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst index b108337795..8539bc0889 100644 --- a/documentation/dev-manual/start.rst +++ b/documentation/dev-manual/start.rst | |||
| @@ -36,7 +36,7 @@ particular working environment and set of practices. | |||
| 36 | equipment together and set up your development environment's | 36 | equipment together and set up your development environment's |
| 37 | hardware topology. | 37 | hardware topology. |
| 38 | 38 | ||
| 39 | Here are possible roles: | 39 | Possible roles are: |
| 40 | 40 | ||
| 41 | - *Application Developer:* This type of developer does application | 41 | - *Application Developer:* This type of developer does application |
| 42 | level work on top of an existing software stack. | 42 | level work on top of an existing software stack. |
| @@ -99,7 +99,7 @@ particular working environment and set of practices. | |||
| 99 | 99 | ||
| 100 | #. *Set up the Application Development Machines:* As mentioned earlier, | 100 | #. *Set up the Application Development Machines:* As mentioned earlier, |
| 101 | application developers are creating applications on top of existing | 101 | application developers are creating applications on top of existing |
| 102 | software stacks. Following are some best practices for setting up | 102 | software stacks. Here are some best practices for setting up |
| 103 | machines used for application development: | 103 | machines used for application development: |
| 104 | 104 | ||
| 105 | - Use a pre-built toolchain that contains the software stack | 105 | - Use a pre-built toolchain that contains the software stack |
| @@ -118,7 +118,7 @@ particular working environment and set of practices. | |||
| 118 | 118 | ||
| 119 | #. *Set up the Core Development Machines:* As mentioned earlier, core | 119 | #. *Set up the Core Development Machines:* As mentioned earlier, core |
| 120 | developers work on the contents of the operating system itself. | 120 | developers work on the contents of the operating system itself. |
| 121 | Following are some best practices for setting up machines used for | 121 | Here are some best practices for setting up machines used for |
| 122 | developing images: | 122 | developing images: |
| 123 | 123 | ||
| 124 | - Have the :term:`OpenEmbedded Build System` available on | 124 | - Have the :term:`OpenEmbedded Build System` available on |