changed RST single backtick to double

Author: robfrawley

Diff for: Resources/doc/basic-usage.rst

@@ -1,12 +1,11 @@
 
-.. default-role:: code
 
 Basic Usage
 ===========
 
 Generally, this bundle works by applying filter sets to images from inside
 a template. Your filter sets are defined within the application's configuration
-file (often `app/config/config.yml`) and are comprised of a collection of
+file (often ``app/config/config.yml``) and are comprised of a collection of
 filters, post-processors, and other optional parameters.
 
 We'll learn more about post-processors and other available parameters later,
@@ -52,7 +51,7 @@ to have the following transformations applied to them:
 * Adjust the image quality to 75.
 
 Adding onto our boilerplate from above, we need to define a filter set (which we'll
-name `my_thumb`) with two filters configured: the `thumbnail` and `background`
+name ``my_thumb``) with two filters configured: the ``thumbnail`` and ``background``
 filters.
 
 .. code-block:: yaml
@@ -84,10 +83,10 @@ filters.
                     # 4px larger to create a 2px border around the final image
                     background: { size: [124, 94], position: center, color: '#000000' }
 
-You've now created a filter set called `my_thumb` that performs a thumbnail
-transformation. The `thumbnail` filter sizes the image to the desired width
-and height (120x90px), and its `mode: outbound` option causes
-the resulting image to be cropped if the input ratio differs. The `background`
+You've now created a filter set called ``my_thumb`` that performs a thumbnail
+transformation. The ``thumbnail`` filter sizes the image to the desired width
+and height (120x90px), and its ``mode: outbound`` option causes
+the resulting image to be cropped if the input ratio differs. The ``background``
 filter results in a 2px black border by creating a black canvas 124x94px in size,
 and positioning the thumbnail at its center.
 
@@ -98,7 +97,7 @@ and positioning the thumbnail at its center.
     transformations can have any number of filters defined for them.
 
 There are a number of additional :doc:`filters <filters>`, but for now you can use
-your newly defined `my_thumb` filter set immediately within a template.
+your newly defined ``my_thumb`` filter set immediately within a template.
 
 .. configuration-block::
 
@@ -113,13 +112,13 @@ your newly defined `my_thumb` filter set immediately within a template.
 Behind the scenes, the bundle applies the filter(s) to the image on-the-fly
 when the first page request is served. The transformed image is then cached
 for subsequent requests. The final cached image path would be similar to
-`/media/cache/my_thumb/relative/path/to/image.jpg`.
+``/media/cache/my_thumb/relative/path/to/image.jpg``.
 
 .. note::
 
-    Using the `dev` environment you might find that images are not properly
+    Using the ``dev`` environment you might find that images are not properly
     rendered via the template helper. This is often caused by having
-    `intercept_redirect` enabled in your application configuration. To ensure
+    ``intercept_redirect`` enabled in your application configuration. To ensure
     images are rendered, it is strongly suggested to disable this option:
 
     .. code-block:: yaml
@@ -171,15 +170,15 @@ Resolve with the Console
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can resolve an image URL using the console command
-`liip:imagine:cache:resolve`. The only required argument is one or more
+``liip:imagine:cache:resolve``. The only required argument is one or more
 relative image paths (which must be separated by a space).
 
 .. code-block:: bash
 
     $ php app/console liip:imagine:cache:resolve relative/path/to/image1.jpg relative/path/to/image2.jpg
 
-Additionally, you can use the `--filters` option to specify which filter
-you want to resolve for (if the `--filters` option is omitted, all
+Additionally, you can use the ``--filters`` option to specify which filter
+you want to resolve for (if the ``--filters`` option is omitted, all
 available filters will be resolved).
 
 .. code-block:: bash
@@ -190,9 +189,9 @@ available filters will be resolved).
 Resolve Pragmatically
 ~~~~~~~~~~~~~~~~~~~~~
 
-You can resolve the image URL in your code using the `getBrowserPath`
-method of the `liip_imagine.cache.manager` service. Assuming you already
-have the service assigned to a variable called `$imagineCacheManager`,
+You can resolve the image URL in your code using the ``getBrowserPath``
+method of the ``liip_imagine.cache.manager`` service. Assuming you already
+have the service assigned to a variable called ``$imagineCacheManager``,
 you would run:
 
 .. code-block:: php
@@ -201,8 +200,8 @@ you would run:
 
 Often, you need to perform this operation in a controller. Assuming your
 controller inherits from the base Symfony controller, you can take advantage
-of the inherited `get` method to request the `liip_imagine.cache.manager`
-service, from which you can call `getBrowserPath` on a relative image
+of the inherited ``get`` method to request the ``liip_imagine.cache.manager``
+service, from which you can call ``getBrowserPath`` on a relative image
 path to get its resolved location.
 
 .. code-block:: php

Diff for: Resources/doc/cache-manager.rst

@@ -1,5 +1,4 @@
 
-.. default-role:: code
 
 Cache Manager
 =============

Diff for: Resources/doc/cache-resolver/amazons3.rst

@@ -1,11 +1,10 @@
 
-.. default-role:: code
 .. _cache-resolver-amazon-s3:
 
 Amazon S3 Resolver
 ==================
 
-The `AmazonS3Resolver` resolver enables cache resolution using Amazon S3.
+The ``AmazonS3Resolver`` resolver enables cache resolution using Amazon S3.
 
 Dependencies
 ------------
@@ -65,8 +64,8 @@ Next, you must define the required services.
 Usage
 -----
 
-After configuring `AmazonS3Resolver`, you can set it as the default cache resolver
-for `LiipImagineBundle` using the following configuration.
+After configuring ``AmazonS3Resolver``, you can set it as the default cache resolver
+for ``LiipImagineBundle`` using the following configuration.
 
 .. code-block:: yaml
 
@@ -79,7 +78,7 @@ for `LiipImagineBundle` using the following configuration.
 Usage on a Specific Filter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Alternatively, you can set `AmazonS3Resolver` as the cache resolver for a specific
+Alternatively, you can set ``AmazonS3Resolver`` as the cache resolver for a specific
 filter set using the following configuration.
 
 .. code-block:: yaml

Diff for: Resources/doc/cache-resolver/aws_s3.rst

@@ -1,11 +1,10 @@
 
-.. default-role:: code
 .. _cache-resolver-aws-s3:
 
 AWS S3 Resolver
 ===============
 
-The `AwsS3Resolver` resolver enables cache resolution using Amazon S3.
+The ``AwsS3Resolver`` resolver enables cache resolution using Amazon S3.
 
 
 Dependencies
@@ -69,8 +68,8 @@ Create Resolver from a Factory
 
 .. tip::
 
-    If using `aws-sdk-php`_ < `3.0.0`, you must omit the `credentials` key and instead
-    place the `key` and `secret` keys at the same level as `region` and `bucket`.
+    If using `aws-sdk-php`_ < ``3.0.0``, you must omit the ``credentials`` key and instead
+    place the ``key`` and ``secret`` keys at the same level as ``region`` and ``bucket``.
 
     .. code-block:: yaml
 
@@ -117,8 +116,8 @@ You have to set up the services required:
 
 .. tip::
 
-    If using `aws-sdk-php`_ < `3.0.0`, you must omit the `credentials` key and instead
-    place the `key` and `secret` keys at the same level as `region` and `bucket`.
+    If using `aws-sdk-php`_ < ``3.0.0``, you must omit the ``credentials`` key and instead
+    place the ``key`` and ``secret`` keys at the same level as ``region`` and ``bucket``.
 
     .. code-block:: yaml
 
@@ -137,8 +136,8 @@ You have to set up the services required:
 Usage
 -----
 
-After configuring `AwsS3Resolver`, you can set it as the default cache resolver
-for `LiipImagineBundle` using the following configuration.
+After configuring ``AwsS3Resolver``, you can set it as the default cache resolver
+for ``LiipImagineBundle`` using the following configuration.
 
 .. code-block:: yaml
 
@@ -151,7 +150,7 @@ for `LiipImagineBundle` using the following configuration.
 Usage on a Specific Filter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Alternatively, you can set `AmazonS3Resolver` as the cache resolver for a specific
+Alternatively, you can set ``AmazonS3Resolver`` as the cache resolver for a specific
 filter set using the following configuration.
 
 .. code-block:: yaml
@@ -247,11 +246,11 @@ for the list of available options.
 Note, that the following options are configured automatically and will be
 ignored, even if you configure it via ObjectOptions:
 
-* `ACL`
-* `Bucket`
-* `Key`
-* `Body`
-* `ContentType`
+* ``ACL``
+* ``Bucket``
+* ``Key``
+* ``Body``
+* ``ContentType``
 
 
 In order to make use of the object PUT options, you can simply add a call to the

Diff for: Resources/doc/cache-resolver/cache.rst

@@ -1,11 +1,10 @@
 
-.. default-role:: code
 .. _cache-resolver-cache:
 
 Cache Resolver
 ==============
 
-The `CacheResolver` cannot be used by itself. Instead, it is a "wrapper" for
+The ``CacheResolver`` cannot be used by itself. Instead, it is a "wrapper" for
 another resolver.
 
 
@@ -28,7 +27,7 @@ Configuration
 -------------
 
 First, you need to setup the required services. In this example we're wrapping an
-instance of `AmazonS3Resolver` inside this resolver.
+instance of ``AmazonS3Resolver`` inside this resolver.
 
 .. code-block:: yaml
 
@@ -69,19 +68,19 @@ instance of `AmazonS3Resolver` inside this resolver.
 
 There are three options available:
 
-* `global_prefix`: A prefix for all keys within the cache. This is useful to
+* ``global_prefix``: A prefix for all keys within the cache. This is useful to
   avoid colliding keys when using the same cache for different systems.
-* `prefix`: A "local" prefix for this wrapper. This is useful when re-using the
+* ``prefix``: A "local" prefix for this wrapper. This is useful when re-using the
   same resolver for multiple filters. This mainly affects the clear method.
-* `index_key`: The name of the index key being used to save a list of created
+* ``index_key``: The name of the index key being used to save a list of created
   cache keys regarding one image and filter pairing.
 
 
 Usage
 -----
 
-After configuring `CacheResolver`, you can set it as the default cache resolver
-for `LiipImagineBundle` using the following configuration.
+After configuring ``CacheResolver``, you can set it as the default cache resolver
+for ``LiipImagineBundle`` using the following configuration.
 
 .. code-block:: yaml
 
@@ -94,7 +93,7 @@ for `LiipImagineBundle` using the following configuration.
 Usage on a Specific Filter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Alternatively, you can set `CacheResolver` as the cache resolver for a specific
+Alternatively, you can set ``CacheResolver`` as the cache resolver for a specific
 filter set using the following configuration.
 
 .. code-block:: yaml

Diff for: Resources/doc/cache-resolver/flysystem.rst

@@ -1,11 +1,10 @@
 
-.. default-role:: code
 .. _cache-resolver-flysystem:
 
 Flysystem Resolver
 ==================
 
-The `FlysystemResolver` resolver enabled cache resolution using the `Flysystem`_
+The ``FlysystemResolver`` resolver enabled cache resolution using the `Flysystem`_
 filesystem abstraction layer.
 
 Dependencies
@@ -26,8 +25,8 @@ can be installed by executing the following command in your project directory:
 Configuration
 -------------
 
-The value of the `filesystem_service` property must be a service that returns an
-instance of `League\\Flysystem\\Filesystem`.
+The value of the ``filesystem_service`` property must be a service that returns an
+instance of ``League\\Flysystem\\Filesystem``.
 
 The following implementation uses `OneupFlysystemBundle`_.
 
@@ -56,24 +55,24 @@ The following implementation uses `OneupFlysystemBundle`_.
 
 There are several configuration options available:
 
-* `root_url`: must be a valid url to the target system the flysystem adapter
+* ``root_url``: must be a valid url to the target system the flysystem adapter
   points to. This is used to determine how the url should be generated upon request.
-  Default value: `null`
-* `cache_prefix`: this is used for the image path generation. This will be the
+  Default value: ``null``
+* ``cache_prefix``: this is used for the image path generation. This will be the
   prefix inside the given Flysystem.
-  Default value: `media/cache`
-* `visibility`: one of the two predefined flysystem visibility constants
-  (`AdapterInterface::VISIBILITY_PUBLIC` [`public`] / `AdapterInterface::VISIBILITY_PRIVATE` [`private`])
+  Default value: ``media/cache``
+* ``visibility``: one of the two predefined flysystem visibility constants
+  (``AdapterInterface::VISIBILITY_PUBLIC`` [``public``] / ``AdapterInterface::VISIBILITY_PRIVATE`` [``private``])
   The visibility is applied, when the objects are stored on a flysystem filesystem.
-  You will most probably want to leave the default or explicitly set `public`.
-  Default value: `public`
+  You will most probably want to leave the default or explicitly set ``public``.
+  Default value: ``public``
 
 
 Usage
 -----
 
-After configuring `FlysystemResolver`, you can set it as the default cache resolver
-for `LiipImagineBundle` using the following configuration.
+After configuring ``FlysystemResolver``, you can set it as the default cache resolver
+for ``LiipImagineBundle`` using the following configuration.
 
 .. code-block:: yaml
 

Diff for: Resources/doc/cache-resolver/proxy.rst

@@ -1,11 +1,10 @@
 
-.. default-role:: code
 .. _cache-resolver-proxy:
 
 ProxyResolver
 =============
 
-The `ProxyResolver` cannot be used by itself. Instead, it is a "decorator" for
+The ``ProxyResolver`` cannot be used by itself. Instead, it is a "decorator" for
 another resolver. It add the ability to use "Proxy Hosts" for your assets. If no
 "Proxy Domains" are set, it behaves like the  underlying cache resolver.
 
@@ -35,16 +34,16 @@ and the cache resolver service to decorate.
                 - { name: "liip_imagine.cache.resolver", resolver: "proxy" }
 
 With this configuration, the cache resolver will generate paths such as
-`//images0.domain.com/.../image.jpg`, `//images1.domain.com/.../image.jpg`, and
-`//images2.domain.com/.../image.jpg` (instead of the original path
+``//images0.domain.com/.../image.jpg``, ``//images1.domain.com/.../image.jpg``, and
+``//images2.domain.com/.../image.jpg`` (instead of the original path
 returned from the decorated cache resolver, in this example using AWS,
-`//bucket.s3.awsamazoncloud.com/.../image.jpg`).
+``//bucket.s3.awsamazoncloud.com/.../image.jpg``).
 
 Usage
 -----
 
-After configuring `ProxyResolver`, you can set it as the default cache resolver
-for `LiipImagineBundle` using the following configuration.
+After configuring ``ProxyResolver``, you can set it as the default cache resolver
+for ``LiipImagineBundle`` using the following configuration.
 
 .. code-block:: yaml
 
@@ -57,7 +56,7 @@ for `LiipImagineBundle` using the following configuration.
 Usage on a Specific Filter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Alternatively, you can set `ProxyResolver` as the cache resolver for a specific
+Alternatively, you can set ``ProxyResolver`` as the cache resolver for a specific
 filter set using the following configuration.
 
 .. code-block:: yaml