man: fix inline interpreted text without a role

sphinx became stricter when handling interpreted text without a role,
e.g. "`foo`" since [1], see [2]. This results in errors such as:

  sphinx.errors.SphinxError: cannot determine default role!

In the past, heuristics were used to determine how
to format the text (inline code, italic, ..).

In labgrid, interpreted text without a role is used inconsistently. Most
times it was actually meant to be either inline code ("``foo``"), italic
text or links to docs sections or class definitions.
Fix all such occurrences with explicit variants that actually make sense
in their respective contexts.

[1] sphinx-doc/sphinx@114093c
[2] sphinx-doc/sphinx#13904

Signed-off-by: Bastian Krause <bst@pengutronix.de>

Author: Bastian-Krause

man/labgrid-client.1

@@ -238,7 +238,7 @@ not at all.
 .sp
 If a target contains multiple Resources of the same type, named matches need to
 be used to address the individual resources. In addition to the \fImatch\fP taken by
-\fIadd\-match\fP, \fIadd\-named\-match\fP also takes a name for the resource. The other
+\fBadd\-match\fP, \fBadd\-named\-match\fP also takes a name for the resource. The other
 client commands support the name as an optional parameter and will inform the
 user that a name is required if multiple resources are found, but no name is
 given.

man/labgrid-client.rst

@@ -229,8 +229,8 @@ LABGRID-CLIENT COMMANDS
 ADDING NAMED RESOURCES
 ----------------------
 If a target contains multiple Resources of the same type, named matches need to
-be used to address the individual resources. In addition to the `match` taken by
-`add-match`, `add-named-match` also takes a name for the resource. The other
+be used to address the individual resources. In addition to the *match* taken by
+``add-match``, ``add-named-match`` also takes a name for the resource. The other
 client commands support the name as an optional parameter and will inform the
 user that a name is required if multiple resources are found, but no name is
 given.

man/labgrid-device-config.5

@@ -200,7 +200,7 @@ This is useful to load drivers and strategy which are contained in your
 testsuite, since the import is done before instantiating the targets.
 .SS IMPORTS EXAMPLE
 .sp
-Import a local \fImyfunctions.py\fP file:
+Import a local \fBmyfunctions.py\fP file:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -212,8 +212,8 @@ imports:
 .UNINDENT
 .SH EXAMPLES
 .sp
-A sample configuration with one \fImain\fP target, accessible via SerialPort
-\fI/dev/ttyUSB0\fP, allowing usage of the ShellDriver:
+A sample configuration with one \fBmain\fP target, accessible via SerialPort
+\fB/dev/ttyUSB0\fP, allowing usage of the ShellDriver:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -233,8 +233,8 @@ targets:
 .UNINDENT
 .UNINDENT
 .sp
-A sample configuration with \fIRemotePlace\fP, using the tools configuration and
-importing the local \fImystrategy.py\fP file. The \fIMyStrategy\fP strategy is contained
+A sample configuration with \fBRemotePlace\fP, using the tools configuration and
+importing the local \fBmystrategy.py\fP file. The \fBMyStrategy\fP strategy is contained
 in the loaded local python file:
 .INDENT 0.0
 .INDENT 3.5

man/labgrid-device-config.rst

@@ -196,7 +196,7 @@ testsuite, since the import is done before instantiating the targets.
 
 IMPORTS EXAMPLE
 ~~~~~~~~~~~~~~~
-Import a local `myfunctions.py` file:
+Import a local ``myfunctions.py`` file:
 
 ::
 
@@ -205,8 +205,8 @@ Import a local `myfunctions.py` file:
 
 EXAMPLES
 --------
-A sample configuration with one `main` target, accessible via SerialPort
-`/dev/ttyUSB0`, allowing usage of the ShellDriver:
+A sample configuration with one ``main`` target, accessible via SerialPort
+``/dev/ttyUSB0``, allowing usage of the ShellDriver:
 
 ::
 
@@ -222,8 +222,8 @@ A sample configuration with one `main` target, accessible via SerialPort
            login_prompt: ' login: '
            username: 'root'
 
-A sample configuration with `RemotePlace`, using the tools configuration and
-importing the local `mystrategy.py` file. The `MyStrategy` strategy is contained
+A sample configuration with ``RemotePlace``, using the tools configuration and
+importing the local ``mystrategy.py`` file. The ``MyStrategy`` strategy is contained
 in the loaded local python file:
 
 ::

man/labgrid-exporter.1

@@ -106,7 +106,7 @@ This variable can be used to set the default coordinator in the format
 \fBHOST[:PORT]\fP (instead of using the \fB\-x\fP option).
 .SH EXAMPLES
 .sp
-Start the exporter with the configuration file \fImy\-config.yaml\fP:
+Start the exporter with the configuration file \fBmy\-config.yaml\fP:
 .INDENT 0.0
 .INDENT 3.5
 .sp

man/labgrid-exporter.rst

@@ -99,7 +99,7 @@ This variable can be used to set the default coordinator in the format
 EXAMPLES
 --------
 
-Start the exporter with the configuration file `my-config.yaml`:
+Start the exporter with the configuration file ``my-config.yaml``:
 
 .. code-block:: bash