Fix doc markup

Author: Matthias Koeppe

src/doc/en/installation/source.rst

@@ -123,9 +123,9 @@ Fortran and compiler suites
 
 Sage installation also needs a Fortran compiler.  It is determined
 automatically whether Sage's GCC package, or just its part containing
-Fortran compiler `gfortran` needs to be installed. This can be
-overwritten by running `./configure` with option
-`--without-system-gcc`.
+Fortran compiler ``gfortran`` needs to be installed. This can be
+overwritten by running ``./configure`` with option
+``--without-system-gcc``.
 
 Officially we support
 gfortran from `GNU Compiler Collection (GCC) <https://gcc.gnu.org/>`_.
@@ -191,10 +191,10 @@ some registration on Apple's developer site; see
 :ref:`section_macprereqs`.
 
 On Redhat-derived systems not all perl components are installed by
-default and you might have to install the **perl-ExtUtils-MakeMaker**
+default and you might have to install the ``perl-ExtUtils-MakeMaker``
 package.
 
-On Cygwin, the **lapack** and **liblapack-devel** packages are required to
+On Cygwin, the ``lapack`` and ``liblapack-devel`` packages are required to
 provide ATLAS support as the Sage package for ATLAS is not built by default.
 
 Installing prerequisites

src/doc/en/installation/troubles.rst

@@ -9,18 +9,18 @@ proposed at the end of :ref:`installation-guide`.
 
 If you have any problems building or running Sage, please take a look
 at the Installation FAQ in the `Sage Release Tour
-<https://wiki.sagemath.org/ReleaseTours>` corresponding to the version
+<https://wiki.sagemath.org/ReleaseTours>`_ corresponding to the version
 that you are installing.  It may offer version-specific installation
 help that has become available after the release was made and is
 therefore not covered by this manual.
 
 Also please do not hesitate to ask for help in the `SageMath forum
-<https://ask.sagemath.org/questions/>`_ or the `sage-support mailing
-list <https://groups.google.com/forum/#!forum/sage-support>`_.
+<https://ask.sagemath.org/questions/>`_ or the sage-support mailing
+list at https://groups.google.com/forum/#!forum/sage-support.
 
 Also note the following. Each separate component of Sage is
-contained in an SPKG; these are stored in `build/pkgs/`. As each one
-is built, a build log is stored in `logs/pkgs/`, so you can browse these
+contained in an SPKG; these are stored in ``build/pkgs/``. As each one
+is built, a build log is stored in ``logs/pkgs/``, so you can browse these
 to find error messages. If an SPKG fails to build, the whole build
 process will stop soon after, so check the most recent log files
 first, or run::
@@ -29,7 +29,7 @@ first, or run::
 
 from the top-level Sage directory to find log files with error
 messages in them.  Send the file ``config.log`` as well as (a small
-part of) the relevant log file to the `sage-support mailing list
-<https://groups.google.com/group/sage-support>`_, making sure to
+part of) the relevant log file to the sage-support mailing list
+at https://groups.google.com/group/sage-support, making sure to
 include at least some of the error messages; probably someone there
 will have some helpful suggestions.