sphinx: profile-manual: convert profile-manual

Last round of manual fixes for remaining links and conversion problems
left after the automatic conversion.

(From yocto-docs rev: 071bca4573bc8c60aef1d89896d6536867fe46e5)

Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 25 insertions, 15 deletions

diff --git a/documentation/profile-manual/profile-manual-intro.rst b/documentation/profile-manual/profile-manual-intro.rst
index 5d51df74dc..994b1c5086 100644
--- a/documentation/profile-manual/profile-manual-intro.rst
+++ b/documentation/profile-manual/profile-manual-intro.rst
@@ -38,12 +38,19 @@ General Setup
 Most of the tools are available only in 'sdk' images or in images built
 after adding 'tools-profile' to your local.conf. So, in order to be able
 to access all of the tools described here, please first build and boot
-an 'sdk' image e.g. $ bitbake core-image-sato-sdk or alternatively by
-adding 'tools-profile' to the EXTRA_IMAGE_FEATURES line in your
-local.conf: EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile" If you
-use the 'tools-profile' method, you don't need to build an sdk image -
-the tracing and profiling tools will be included in non-sdk images as
-well e.g.: $ bitbake core-image-sato
+an 'sdk' image e.g. ::
+
+   $ bitbake core-image-sato-sdk
+
+or alternatively by adding 'tools-profile' to the EXTRA_IMAGE_FEATURES line in
+your local.conf: ::
+
+   EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile"
+
+If you use the 'tools-profile' method, you don't need to build an sdk image -
+the tracing and profiling tools will be included in non-sdk images as well e.g.: ::
+
+   $ bitbake core-image-sato
 
 .. note::
 
@@ -52,18 +59,21 @@ well e.g.: $ bitbake core-image-sato
 
    You can prevent that by setting the
    :term:`INHIBIT_PACKAGE_STRIP`
-   variable to "1" in your ``local.conf`` when you build the image:
+   variable to "1" in your ``local.conf`` when you build the image: ::
 
-INHIBIT_PACKAGE_STRIP = "1" The above setting will noticeably increase
-the size of your image.
+      INHIBIT_PACKAGE_STRIP = "1"
+
+   The above setting will noticeably increase the size of your image.
 
 If you've already built a stripped image, you can generate debug
 packages (xxx-dbg) which you can manually install as needed.
 
 To generate debug info for packages, you can add dbg-pkgs to
-EXTRA_IMAGE_FEATURES in local.conf. For example: EXTRA_IMAGE_FEATURES =
-"debug-tweaks tools-profile dbg-pkgs" Additionally, in order to generate
-the right type of debuginfo, we also need to set
-:term:`PACKAGE_DEBUG_SPLIT_STYLE`
-in the ``local.conf`` file: PACKAGE_DEBUG_SPLIT_STYLE =
-'debug-file-directory'
+EXTRA_IMAGE_FEATURES in local.conf. For example: ::
+
+   EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile dbg-pkgs"
+
+Additionally, in order to generate the right type of debuginfo, we also need to
+set :term:`PACKAGE_DEBUG_SPLIT_STYLE` in the ``local.conf`` file: ::
+
+   PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory'