diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-05-04 14:57:51 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-05-10 12:52:34 +0100 |
commit | eae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a (patch) | |
tree | fc3b2691dece36a13abc2892aea921d1dc601466 /documentation/profile-manual | |
parent | e3d64415eddb7c0a5c13a2a91611204c8abfbedb (diff) | |
download | poky-eae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a.tar.gz |
manuals: fix name capitalization issues
- Using "BitBake" instead of "Bitbake" or "bitbake", aligning with the
title of the "BitBake User Manual".
- Using "OpenEmbedded" instead of "Openembedded"
- Using "Python" instead of "python"
(From yocto-docs rev: 0b893e2a15aefedd7100445fc9d7eeed07b6afc6)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/profile-manual')
-rw-r--r-- | documentation/profile-manual/usage.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/profile-manual/usage.rst b/documentation/profile-manual/usage.rst index fb1553d70d..0fd703d8a5 100644 --- a/documentation/profile-manual/usage.rst +++ b/documentation/profile-manual/usage.rst | |||
@@ -740,7 +740,7 @@ entry/exit events we recorded:: | |||
740 | root@crownbay:~# perf script -g python | 740 | root@crownbay:~# perf script -g python |
741 | generated Python script: perf-script.py | 741 | generated Python script: perf-script.py |
742 | 742 | ||
743 | The skeleton script simply creates a python function for each event type in the | 743 | The skeleton script simply creates a Python function for each event type in the |
744 | perf.data file. The body of each function simply prints the event name along | 744 | perf.data file. The body of each function simply prints the event name along |
745 | with its parameters. For example: | 745 | with its parameters. For example: |
746 | 746 | ||
@@ -859,7 +859,7 @@ goes a little way to support the idea mentioned previously that given | |||
859 | the right kind of trace data, higher-level profiling-type summaries can | 859 | the right kind of trace data, higher-level profiling-type summaries can |
860 | be derived from it. | 860 | be derived from it. |
861 | 861 | ||
862 | Documentation on using the `'perf script' python | 862 | Documentation on using the `'perf script' Python |
863 | binding <https://linux.die.net/man/1/perf-script-python>`__. | 863 | binding <https://linux.die.net/man/1/perf-script-python>`__. |
864 | 864 | ||
865 | System-Wide Tracing and Profiling | 865 | System-Wide Tracing and Profiling |
@@ -1149,7 +1149,7 @@ section can be found here: | |||
1149 | - The `'perf script' | 1149 | - The `'perf script' |
1150 | manpage <https://linux.die.net/man/1/perf-script>`__. | 1150 | manpage <https://linux.die.net/man/1/perf-script>`__. |
1151 | 1151 | ||
1152 | - Documentation on using the `'perf script' python | 1152 | - Documentation on using the `'perf script' Python |
1153 | binding <https://linux.die.net/man/1/perf-script-python>`__. | 1153 | binding <https://linux.die.net/man/1/perf-script-python>`__. |
1154 | 1154 | ||
1155 | - The top-level `perf(1) manpage <https://linux.die.net/man/1/perf>`__. | 1155 | - The top-level `perf(1) manpage <https://linux.die.net/man/1/perf>`__. |