README.rst: Expanding on loginctl's enable-linger. Making reference to /sys/kernel/realtime bold. Setting all Note: to bold. Removing italics around user-defined environments, to make links be displayed properly.

1 files changed, 13 insertions, 9 deletions

diff --git a/README.rst b/README.rst
index f38eefb..d932984 100644
--- a/README.rst
+++ b/README.rst
@@ -30,7 +30,11 @@ Separate tmux environments
     tmux -L <name-of-socket> attach
 
 | will attach you to that separate environment.
-| *Note*: All of these separate environments are dependant on your login. If there is no login, |systemd| will kill all of your user services! You can get around this by using |loginctl| to set *enable-linger* for your user.
+| **Note**: All of these separate environments are dependant on your login. If there is no login, |systemd| will kill all of your user services! You can get around this by using |loginctl| to enable lingering for your user.
+
+  .. code:: bash
+
+    loginctl enable-linger
 
 
 Services
@@ -44,7 +48,7 @@ ______________
 
     DefaultEnvironment=DISPLAY=:0
 
-| The compton user service is anti-dependent on the realtime kernel (i.e. it will not start, if */sys/kernel/realtime* is present and not empty).
+| The compton user service is anti-dependent on the realtime kernel (i.e. it will not start, if **/sys/kernel/realtime** is present and not empty).
 | You can start and enable it like any other systemd user service:  
 
   .. code:: bash
@@ -57,7 +61,7 @@ ___________
 | The cpupower package on |arch_linux| has been |cpupower_feature_request|, to allow easier appliance of CPU settings based on other profiles, than the system's default.
 | This is very useful, when using a real-time kernel: cpupower-rt settings will be applied **after** the general cpupower settings have been applied.  
 
-| The *cpupower-rt.service* is dependant on a realtime kernel. It will only start, if */sys/kernel/realtime* is present and not empty.  
+| The *cpupower-rt.service* is dependant on a realtime kernel. It will only start, if **/sys/kernel/realtime** is present and not empty.  
 | You can start and enable it like any other systemd service:
 
   .. code:: bash
@@ -75,7 +79,7 @@ ________________
     export GPG_TTY=$(tty)
     export GPG_AGENT_INFO=""
 
-| *Note*: These settings specifically apply to gnupg > 2.1!
+| **Note**: These settings specifically apply to gnupg > 2.1!
 | Otherwise you can start and enable it like any other systemd user service:  
 
   .. code:: bash
@@ -108,7 +112,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 +140,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
@@ -147,7 +151,7 @@ _______________
 rtorrent@
 _________
 | The systemd system service rtorrent@.service is quite similar to the user service rtorrent.service in functionality, but on top offers the possibility of dependency to a system service - like |openvpn| (the default being a profile called *secure*).
-| **Note:** In a separate configuration file (*"/etc/conf.d/rtorrent@.conf"*), the *TMUX_TMPDIR* should be set, as it otherwise defaults to using *"/tmp/"*!
+| **Note:** In a separate configuration file (*"/etc/conf.d/rtorrent@.conf"*), the *TMUX_TMPDIR* should be set, as it otherwise defaults to using */tmp/*!
 | The system service can be started and enabled like this:
 
   .. code:: bash
@@ -200,7 +204,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 +230,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