From eae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 4 May 2022 14:57:51 +0200 Subject: 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 Signed-off-by: Richard Purdie --- documentation/profile-manual/usage.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation/profile-manual') 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:: root@crownbay:~# perf script -g python generated Python script: perf-script.py -The skeleton script simply creates a python function for each event type in the +The skeleton script simply creates a Python function for each event type in the perf.data file. The body of each function simply prints the event name along with its parameters. For example: @@ -859,7 +859,7 @@ goes a little way to support the idea mentioned previously that given the right kind of trace data, higher-level profiling-type summaries can be derived from it. -Documentation on using the `'perf script' python +Documentation on using the `'perf script' Python binding `__. System-Wide Tracing and Profiling @@ -1149,7 +1149,7 @@ section can be found here: - The `'perf script' manpage `__. -- Documentation on using the `'perf script' python +- Documentation on using the `'perf script' Python binding `__. - The top-level `perf(1) manpage `__. -- cgit v1.2.3-54-g00ecf