diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2021-05-12 11:29:20 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-05-22 12:16:40 +0100 |
commit | 4db4e4ca46e8b23d5042d925ce5ad3073de4c3ed (patch) | |
tree | 6c0f58527ff6d5929ce0e948092357efb69fc659 /documentation/ref-manual/devtool-reference.rst | |
parent | 68ee5b4bcc1098cb5a66098e65bec6c1cf69f4c2 (diff) | |
download | poky-4db4e4ca46e8b23d5042d925ce5ad3073de4c3ed.tar.gz |
ref-manual: simplify style
(From yocto-docs rev: 657a7f54856afd6fec7f2cb0b5f12b4b2d24adb7)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/devtool-reference.rst')
-rw-r--r-- | documentation/ref-manual/devtool-reference.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/ref-manual/devtool-reference.rst b/documentation/ref-manual/devtool-reference.rst index 0ce3219831..1862c481df 100644 --- a/documentation/ref-manual/devtool-reference.rst +++ b/documentation/ref-manual/devtool-reference.rst | |||
@@ -403,8 +403,8 @@ Upgrading a Recipe | |||
403 | 403 | ||
404 | As software matures, upstream recipes are upgraded to newer versions. As | 404 | As software matures, upstream recipes are upgraded to newer versions. As |
405 | a developer, you need to keep your local recipes up-to-date with the | 405 | a developer, you need to keep your local recipes up-to-date with the |
406 | upstream version releases. Several methods exist by which you can | 406 | upstream version releases. There are several ways of upgrading recipes. |
407 | upgrade recipes. You can read about them in the ":ref:`dev-manual/common-tasks:upgrading recipes`" | 407 | You can read about them in the ":ref:`dev-manual/common-tasks:upgrading recipes`" |
408 | section of the Yocto Project Development Tasks Manual. This section | 408 | section of the Yocto Project Development Tasks Manual. This section |
409 | overviews the ``devtool upgrade`` command. | 409 | overviews the ``devtool upgrade`` command. |
410 | 410 | ||
@@ -516,8 +516,8 @@ you do, the package manager is bypassed. | |||
516 | should never use it to update an image that will be used in | 516 | should never use it to update an image that will be used in |
517 | production. | 517 | production. |
518 | 518 | ||
519 | Some conditions exist that could prevent a deployed application from | 519 | Some conditions could prevent a deployed application from |
520 | behaving as expected. When both of the following conditions exist, your | 520 | behaving as expected. When both of the following conditions are met, your |
521 | application has the potential to not behave correctly when run on the | 521 | application has the potential to not behave correctly when run on the |
522 | target: | 522 | target: |
523 | 523 | ||
@@ -528,7 +528,7 @@ target: | |||
528 | - The target does not physically have the packages on which the | 528 | - The target does not physically have the packages on which the |
529 | application depends installed. | 529 | application depends installed. |
530 | 530 | ||
531 | If both of these conditions exist, your application will not behave as | 531 | If both of these conditions are met, your application will not behave as |
532 | expected. The reason for this misbehavior is because the | 532 | expected. The reason for this misbehavior is because the |
533 | ``devtool deploy-target`` command does not deploy the packages (e.g. | 533 | ``devtool deploy-target`` command does not deploy the packages (e.g. |
534 | libraries) on which your new application depends. The assumption is that | 534 | libraries) on which your new application depends. The assumption is that |