From 91af895aaabfa954caa6c20488b9e8fb1d3e477a Mon Sep 17 00:00:00 2001 From: Yonel Ceruto Date: Fri, 8 Jan 2016 10:42:11 -0500 Subject: [PATCH 1/2] Fixed indent --- Resources/doc/configuration.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Resources/doc/configuration.rst b/Resources/doc/configuration.rst index a6e9254d3..b0ee9c91c 100644 --- a/Resources/doc/configuration.rst +++ b/Resources/doc/configuration.rst @@ -56,10 +56,10 @@ There are several configuration options available: * ``data_loader`` - name of a custom data loader. Default value: ``filesystem`` (which means the standard filesystem loader is used). * ``controller`` - * ``filter_action`` - name of the controller action to use in the route loader. - Default value: ``liip_imagine.controller:filterAction`` - * ``filter_runtime_action`` - name of the controller action to use in the route - loader for runtimeconfig images. Default value: ``liip_imagine.controller:filterRuntimeAction`` + * ``filter_action`` - name of the controller action to use in the route loader. + Default value: ``liip_imagine.controller:filterAction`` + * ``filter_runtime_action`` - name of the controller action to use in the route + loader for runtimeconfig images. Default value: ``liip_imagine.controller:filterRuntimeAction`` * ``driver`` - one of the three drivers: ``gd``, ``imagick``, ``gmagick``. Default value: ``gd`` * ``filter_sets`` - specify the filter sets that you want to define and use. From cc8c1b764ac40acf2cc11890ea07ceb458837465 Mon Sep 17 00:00:00 2001 From: Yonel Ceruto Date: Fri, 8 Jan 2016 10:42:30 -0500 Subject: [PATCH 2/2] Fixed typo --- Resources/doc/filters.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Resources/doc/filters.rst b/Resources/doc/filters.rst index 60a516614..7307d1119 100644 --- a/Resources/doc/filters.rst +++ b/Resources/doc/filters.rst @@ -237,7 +237,7 @@ To tell the bundle about your new filter loader, register it in the service container and apply the ``liip_imagine.filter.loader`` tag to it (example here in XML): -.. contiguration-block:: +.. configuration-block:: .. code-block:: yaml @@ -322,7 +322,7 @@ should return the ``BinaryInterface`` as well. To tell the bundle about your post-processor, register it in the service container and apply the ``liip_imagine.filter.post_processor`` tag to it: -.. contiguration-block:: +.. configuration-block:: .. code-block:: yaml