From ab66a12426391ca26749db993ec1f598b83bcd9c Mon Sep 17 00:00:00 2001 From: WouterJ Date: Fri, 9 Jan 2015 02:04:25 +0100 Subject: [PATCH] Fix markup --- components/options_resolver.rst | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/components/options_resolver.rst b/components/options_resolver.rst index ef9a0f18bd2..3f274b672d1 100644 --- a/components/options_resolver.rst +++ b/components/options_resolver.rst @@ -361,10 +361,9 @@ In sub-classes, you can use :method:`Symfony\\Component\\OptionsResolver\\Option to add additional allowed types without erasing the ones already set. .. versionadded:: 2.6 - Before Symfony 2.6, `setAllowedTypes()` and `addAllowedTypes()` expected - the values to be given as an array mapping option names to allowed types:: - - $resolver->setAllowedTypes(array('port' => array('null', 'int'))); + Before Symfony 2.6, ``setAllowedTypes()`` and ``addAllowedTypes()`` expected + the values to be given as an array mapping option names to allowed types:: + ``$resolver->setAllowedTypes(array('port' => array('null', 'int')));`` Value Validation ~~~~~~~~~~~~~~~~ @@ -413,12 +412,9 @@ In sub-classes, you can use :method:`Symfony\\Component\\OptionsResolver\\Option to add additional allowed values without erasing the ones already set. .. versionadded:: 2.6 - Before Symfony 2.6, `setAllowedValues()` and `addAllowedValues()` expected + Before Symfony 2.6, ``setAllowedValues()`` and ``addAllowedValues()`` expected the values to be given as an array mapping option names to allowed values: - - .. code-block:: php - - $resolver->setAllowedValues(array('transport' => array('sendmail', 'mail', 'smtp'))); + ``$resolver->setAllowedValues(array('transport' => array('sendmail', 'mail', 'smtp')));`` Option Normalization ~~~~~~~~~~~~~~~~~~~~