Transform all code titles to literals

Author: wouterj

reference/configuration/assetic.rst

@@ -6,7 +6,7 @@ Assetic Configuration Reference (AsseticBundle)
 
 .. include:: /assetic/_standard_edition_warning.rst.inc
 
-You can get the full Asstic configuration reference as follows:
+You can get the full Assetic configuration reference as follows:
 
 .. code-block:: terminal
 

reference/configuration/debug.rst

@@ -32,16 +32,20 @@ Configuration
 * `min_depth`_
 * `max_string_length`_
 
-max_items
-~~~~~~~~~
+``max_items``
+~~~~~~~~~~~~~
 
 **type**: ``integer`` **default**: ``2500``
 
 This is the maximum number of items to dump. Setting this option to ``-1``
 disables the limit.
 
-min_depth
-~~~~~~~~~
+``min_depth``
+~~~~~~~~~~~~~
+
+.. versionadded:: 3.4
+
+    The ``min_depth`` option was introduced in Symfony 3.4.
 
 **type**: ``integer`` **default**: ``1``
 
@@ -50,20 +54,16 @@ be cloned. After this depth is reached, only ``max_items`` items will be
 cloned. The default value is ``1``, which is consistent with older Symfony
 versions.
 
-.. versionadded:: 3.4
-
-    The ``min_depth`` option was introduced in Symfony 3.4.
-
-max_string_length
-~~~~~~~~~~~~~~~~~
+``max_string_length``
+~~~~~~~~~~~~~~~~~~~~~
 
 **type**: ``integer`` **default**: ``-1``
 
 This option configures the maximum string length before truncating the
 string. The default value (``-1``) means that strings are never truncated.
 
-dump_destination
-~~~~~~~~~~~~~~~~
+``dump_destination``
+~~~~~~~~~~~~~~~~~~~~
 
 **type**: ``string`` **default**: ``null``
 

reference/configuration/doctrine.rst

@@ -247,39 +247,39 @@ Explicit definition of all the mapped entities is the only necessary
 configuration for the ORM and there are several configuration options that
 you can control. The following configuration options exist for a mapping:
 
-type
-....
+``type``
+........
 
 One of ``annotation``, ``xml``, ``yml``, ``php`` or ``staticphp``. This
 specifies which type of metadata type your mapping uses.
 
-dir
-...
+``dir``
+.......
 
 Path to the mapping or entity files (depending on the driver). If this path
 is relative, it is assumed to be relative to the bundle root. This only works
 if the name of your mapping is a bundle name. If you want to use this option
 to specify absolute paths you should prefix the path with the kernel parameters
 that exist in the DIC (for example ``%kernel.project_dir%``).
 
-prefix
-......
+``prefix``
+..........
 
 A common namespace prefix that all entities of this mapping share. This
 prefix should never conflict with prefixes of other defined mappings otherwise
 some of your entities cannot be found by Doctrine. This option defaults
 to the bundle namespace + ``Entity``, for example for an application bundle
 called AcmeHelloBundle prefix would be ``Acme\HelloBundle\Entity``.
 
-alias
-.....
+``alias``
+.........
 
 Doctrine offers a way to alias entity namespaces to simpler, shorter names
 to be used in DQL queries or for Repository access. When using a bundle
 the alias defaults to the bundle name.
 
-is_bundle
-.........
+``is_bundle``
+.............
 
 This option is a derived value from ``dir`` and by default is set to ``true``
 if dir is relative proved by a ``file_exists()`` check that returns ``false``.
@@ -437,7 +437,7 @@ Default Value of Dir
 
 If ``dir`` is not specified, then its default value depends on which configuration
 driver is being used. For drivers that rely on the PHP files (annotation,
-staticphp) it will be ``[Bundle]/Entity``. For drivers that are using
+``staticphp``) it will be ``[Bundle]/Entity``. For drivers that are using
 configuration files (XML, YAML, ...) it will be
 ``[Bundle]/Resources/config/doctrine``.