user: Remove nit-picky warnings.

4 files changed, 13 insertions, 13 deletions

diff --git a/user/tracing/captureengine.rst b/user/tracing/captureengine.rst
index fab8bed..d04b8a4 100644
--- a/user/tracing/captureengine.rst
+++ b/user/tracing/captureengine.rst
@@ -98,7 +98,7 @@ traces the context switches between these tasks. ``cwceil`` and ``cwfloor`` are
 set to a narrow range of task priorities to avoid creating noise from a large
 number of context switches between tasks we are not interested in.
 
-.. code:: shell
+.. code-block:: shell
 
   *** BEGIN OF TEST CAPTURE ENGINE ***
   *** TEST VERSION: 5.0.0.de9b7d712bf5da6593386fd4fbca0d5f8b8431d8
diff --git a/user/tracing/examples.rst b/user/tracing/examples.rst
index d847533..c44daff 100644
--- a/user/tracing/examples.rst
+++ b/user/tracing/examples.rst
@@ -46,7 +46,7 @@ has been stored) run the following commands to generate traces:
 
 BSP is configured with the following command -
 
-.. code:: shell
+.. code-block:: shell
 
   ../rtems/configure --target=sparc-rtems5 --prefix=/development/rtems/5 \
   --enable-networking --enable-tests --enable-rtemsbsp=erc32 --enable-cxx
@@ -58,7 +58,7 @@ following commands according to your installation. Also confirm the path of the
 fileio's executable and object files in the last line of the command according
 to your installation.
 
-.. code:: shell
+.. code-block:: shell
 
   sparc-rtems5-gcc -Bsparc-rtems5/erc32/lib/ \
   -specs bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections \
@@ -72,7 +72,7 @@ the application. The link command follows the escape sequence "--". "-C" option
 denotes the name of the user configuration file and "-W" specifies the name of
 the wrapper c file.
 
-.. code:: shell
+.. code-block:: shell
 
   rtems-tld -C fileio-trace.ini -W fileio-wrapper -- -Bsparc-rtems5/erc32/lib/ \
   -specs bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections \
@@ -88,13 +88,13 @@ display the contents of the trace buffer and save the buffer to disk in the form
 of binary files. Use `rtrace -l` to list the availalble options for commands
 with `rtrace`.
 
-.. code:: shell
+.. code-block:: shell
 
   sparc-rtems5-run sparc-rtems5/c/erc32/testsuites/samples/fileio.exe
 
 The output from the above commands will be as follows:
 
-.. code:: shell
+.. code-block:: shell
 
   *** BEGIN OF TEST FILE I/O ***
   *** TEST VERSION: 5.0.0.de9b7d712bf5da6593386fd4fbca0d5f8b8431d8
diff --git a/user/tracing/introduction.rst b/user/tracing/introduction.rst
index d6f249f..a2e635d 100644
--- a/user/tracing/introduction.rst
+++ b/user/tracing/introduction.rst
@@ -2,7 +2,7 @@
 
 .. Copyright (C) 2016 Chris Johns <chrisj@rtems.org>
 
-.. _introduction:
+.. _IntroductionToTracing:
 
 Introduction to Tracing
 ***********************
diff --git a/user/tracing/tracelinker.rst b/user/tracing/tracelinker.rst
index 8aad20f..b1e60fd 100644
--- a/user/tracing/tracelinker.rst
+++ b/user/tracing/tracelinker.rst
@@ -92,7 +92,7 @@ used to include other INI files using the include key name. This is shown in the
 following example where the values indicate rtems and rtld-base configuration
 files:
 
-.. code-block:: shell
+.. code-block:: ini
 
   include = rtems.ini, rtld-base.ini
 
@@ -100,7 +100,7 @@ The trace linker also uses values in keys to specify other sections. In this
 example the functions name lists `test-trace-funcs` and that section contains a
 headers key that further references a section called `test-headers`:
 
-.. code-block:: shell
+.. code-block:: ini
 
   functions = test-trace-funcs, rtems-api
 
@@ -143,7 +143,7 @@ following keys:
 The tracer section of the file:`test-trace.ini` is shown below with explanatory
 comments.
 
-.. code-block:: shell
+.. code-block:: ini
 
   ;
   ; RTEMS Trace Linker Test Configuration.
@@ -212,7 +212,7 @@ general options section can contain following sets of keys:
 The options section of the file: `test-trace.ini` uses two of the aforementioned
 keys as shown below:
 
-.. code-block:: shell
+.. code-block:: ini
 
   ;
   ; Options can be defined here or on the command line.
@@ -250,7 +250,7 @@ The trace section of the file: `test-trace.ini` is shown below. A trace section
 can reference other trace sections of a specific type. This allows a trace
 sections to build on other trace sections.
 
-.. code:: shell
+.. code-block:: ini
 
   ; User application trace example.
   ;
@@ -421,7 +421,7 @@ The file: `test-trace.ini` specifies ``printf-generator`` as its generator. This
 section can be found in the file: `rtld-print.ini` in the rtems-tools directory
 and is shown below:
 
-.. code:: shell
+.. code:: ini
 
   ;
   ; A printf generator prints to stdout the trace functions.