README.rst: Replacing markdown italics with rest italics.

1 files changed, 6 insertions, 6 deletions

diff --git a/README.rst b/README.rst
index 44c7db3..f38eefb 100644
--- a/README.rst
+++ b/README.rst
@@ -67,7 +67,7 @@ ___________
 
 gpg-agent --user
 ________________
-| The systemd user service *gpg-agent.service* starts the gpg-agent and thus makes it independent of a certain session the user runs. The `homedir` for GnuPG is set to be in `~/.gnupg` (default).
+| The systemd user service *gpg-agent.service* starts the gpg-agent and thus makes it independent of a certain session the user runs. The *homedir* for GnuPG is set to be in *~/.gnupg* (default).
 | Therefore make sure to set your *GPG_TTY* and *GPG_AGENT_INFO* |environment_variable| for your |bash| or |zsh| (or whatever you run) to the following
 
   .. code:: bash
@@ -96,7 +96,7 @@ ____________
 jack@ --user
 ____________
 JACK2 comes with a dbus interface. Unfortunately systemd's efforts regarding [kdbus](https://en.wikipedia.org/wiki/Kdbus) and integrating kernel CPU [cgroups](https://www.kernel.org/doc/Documentation/cgroups/) (and thereby also real-time scheduling) is still somewhat in limbo.  
-The included jack@.service starts JACK using */usr/bin/jackd"* (so no dbus), according to a profile. The name of that profile follows after the *@* on starting/ activating the unit and must be found in either `/etc/jack/` or `~/.config/jack/`.  
+The included jack@.service starts JACK using */usr/bin/jackd"* (so no dbus), according to a profile. The name of that profile follows after the *@* on starting/ activating the unit and must be found in either */etc/jack/* or *~/.config/jack/*.  
 
   .. code:: bash
 
@@ -108,7 +108,7 @@ This service is dependant on the real-time kernel command line option. It will o
 monitoring --user
 _________________
 | The systemd user service *monitoring.service* is just a useful tool for monitoring.
-| Currently it starts |htop|, |glances| and asks loginctl for the current user processes in a `separate |tmux| environment`.
+| Currently it starts |htop|, |glances| and asks loginctl for the current user processes in a *separate |tmux| environment*.
 | To connect to it after starting the service, just do  
 
   .. code:: bash
@@ -136,7 +136,7 @@ ___________________________
 
 rtorrent --user
 _______________
-| rtorrent doesn't really come with any systemd service. Here it is started within a `separate |tmux| environment`. It will automatically create *~/Downloads/rtorrent/{tmp,session}*, if non-existent and set its working directory to *~/Downloads*.
+| rtorrent doesn't really come with any systemd service. Here it is started within a *separate |tmux| environment*. It will automatically create *~/Downloads/rtorrent/{tmp,session}*, if non-existent and set its working directory to *~/Downloads*.
 | The systemd user service is started/ enabled like this:
 
   .. code:: bash
@@ -200,7 +200,7 @@ ____________________
 
 tmux --user
 ___________
-| The systemd user service *tmux.service* starts a `separate |tmux| environment`.
+| The systemd user service *tmux.service* starts a *separate |tmux| environment*.
 | To start/enable it, just do:
 
   .. code:: bash
@@ -226,7 +226,7 @@ _________________
 
 weechat --user
 ______________
-| The systemd user service *weechat.service* starts the |irc| client |weechat| in a `separate |tmux| environment` for the current user.
+| The systemd user service *weechat.service* starts the |irc| client |weechat| in a *separate |tmux| environment* for the current user.
 | To start/enable it, just do:
 
   .. code:: bash