Merge pull request #691 from yceruto/fixed-build-issues

Fixed build issues

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.

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