symfony
diff --git a/‎book/forms.rst
Copy file name to clipboardExpand all lines: book/forms.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎book/forms.rst
Copy file name to clipboardExpand all lines: book/forms.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎cookbook/bundles/override.rst
Copy file name to clipboardExpand all lines: cookbook/bundles/override.rst
+3-1Lines changed: 3 additions & 1 deletion b/‎cookbook/bundles/override.rst
Copy file name to clipboardExpand all lines: cookbook/bundles/override.rst
+3-1Lines changed: 3 additions & 1 deletion
diff --git a/‎reference/forms/types/repeated.rst
Copy file name to clipboardExpand all lines: reference/forms/types/repeated.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎reference/forms/types/repeated.rst
Copy file name to clipboardExpand all lines: reference/forms/types/repeated.rst
+1-1Lines changed: 1 addition & 1 deletion
@@ -1519,7 +1519,7 @@ file, you can see every block needed to render a form and every default field
 type.
 
 In PHP, the fragments are individual template files. By default they are located in
-the `Resources/views/Form` directory of the framework bundle (`view on GitHub`_).
+the ``Resources/views/Form`` directory of the framework bundle (`view on GitHub`_).
 
 Each fragment name follows the same basic pattern and is broken up into two pieces,
 separated by a single underscore character (``_``). A few examples are:
 
@@ -34,6 +34,8 @@ is almost always the case), you can easily override controllers via bundle
 inheritance. For more information, see :doc:`/cookbook/bundles/inheritance`.
 If the controller is a service, see the next section on how to override it.
 
+.. _override-services-configuration:
+
 Services & Configuration
 ------------------------
 
@@ -107,7 +109,7 @@ Forms
 
 In order to override a form type, it has to be registered as a service (meaning
 it is tagged as ``form.type``). You can then override it as you would override any
-service as explained in `Services & Configuration`_. This, of course, will only
+service as explained in :ref:`override-services-configuration`. This, of course, will only
 work if the type is referred to by its alias rather than being instantiated,
 e.g.::
 
 
@@ -158,7 +158,7 @@ second_options
 
 **type**: ``array`` **default**: ``array()``
 
-Additional options (will be merged into `options` above) that should be passed
+Additional options (will be merged into ``options`` above) that should be passed
 *only* to the second field. This is especially useful for customizing the
 label (see `first_options`_).