Fixing various broken or redirecting (because of permanent moves) links throughout the docs

Author: weaverryan

book/http_fundamentals.rst

@@ -538,7 +538,7 @@ sensible defaults. For more advanced users, the sky is the limit.
 .. _`xkcd`: http://xkcd.com/
 .. _`HTTP 1.1 RFC`: http://www.w3.org/Protocols/rfc2616/rfc2616.html
 .. _`HTTP Bis`: http://datatracker.ietf.org/wg/httpbis/
-.. _`Live HTTP Headers`: https://addons.mozilla.org/en-US/firefox/addon/3829/
+.. _`Live HTTP Headers`: https://addons.mozilla.org/en-US/firefox/addon/live-http-headers/
 .. _`List of HTTP status codes`: http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
 .. _`List of HTTP header fields`: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields
 .. _`List of common media types`: http://en.wikipedia.org/wiki/Internet_media_type#List_of_common_media_types

book/templating.rst

@@ -1347,4 +1347,4 @@ Learn more from the Cookbook
 .. _`Output Escaping`: http://twig.sensiolabs.org/doc/api.html#escaper-extension
 .. _`tags`: http://twig.sensiolabs.org/doc/tags/index.html
 .. _`filters`: http://twig.sensiolabs.org/doc/filters/index.html
-.. _`add your own extensions`: http://twig.sensiolabs.org/doc/extensions.html
+.. _`add your own extensions`: http://twig.sensiolabs.org/doc/advanced.html#creating-an-extension

components/http_foundation/introduction.rst

@@ -366,7 +366,7 @@ Downloading Files
 When uploading a file, you must add a ``Content-Disposition`` header to your
 response. While creating this header for basic file downloads is easy, using
 non-ASCII filenames is more involving. The
-:method:`:Symfony\\Component\\HttpFoundation\\Response:makeDisposition`
+:method:`Symfony\\Component\\HttpFoundation\\Response::makeDisposition`
 abstracts the hard work behind a simple API::
 
     use Symfony\Component\HttpFoundation\ResponseHeaderBag;

components/templating.rst

@@ -26,9 +26,9 @@ Usage
 
 The :class:`Symfony\\Component\\Templating\\PhpEngine` class is the entry point
 of the component. It needs a template name parser
-(:class:`Symfony\\Component\\templating\\TemplateNameParserInterface`) to
+(:class:`Symfony\\Component\\Templating\\TemplateNameParserInterface`) to
 convert a template name to a template reference and template loader
-(:class:`Symfony\\Component\\templating\\Loader\\LoaderInterface`) to find the
+(:class:`Symfony\\Component\\Templating\\Loader\\LoaderInterface`) to find the
 template associated to a reference.
 
     use Symfony\Component\Templating\PhpEngine;
@@ -66,7 +66,7 @@ The template inheritance is designed to share layouts with many templates.
         </body>
     </html>
 
-The :method:`Symfony\\Templating\\PhpEngine::extend` method is called in the
+The :method:`Symfony\\Component\\Templating\\PhpEngine::extend` method is called in the
 sub-template to set its parent template.
 
 .. code-block:: php
@@ -83,7 +83,7 @@ sub-template to set its parent template.
         <?php echo $page->body ?>
     </p>
 
-To use template inheritance, the :class:`Symfony\\Templating\\Helper\\SlotsHelper`
+To use template inheritance, the :class:`Symfony\\Component\\Templating\\Helper\\SlotsHelper`
 helper must be registered.
 
     use Symfony\Templating\Helper\SlotsHelper;

cookbook/email/email.rst

@@ -130,4 +130,4 @@ of `Creating Messages`_ in great detail in its documentation.
     * :doc:`spool`
 
 .. _`Swiftmailer`: http://www.swiftmailer.org/
-.. _`Creating Messages`: http://swiftmailer.org/docs/messages
+.. _`Creating Messages`: http://swiftmailer.org/docs/messages.html

reference/constraints/UniqueEntity.rst

@@ -14,7 +14,7 @@ using an email address that already exists in the system.
 +----------------+-------------------------------------------------------------------------------------+
 | Class          | :class:`Symfony\\Bridge\\Doctrine\\Validator\\Constraints\\UniqueEntity`            |
 +----------------+-------------------------------------------------------------------------------------+
-| Validator      | :class:`Symfony\\Bridge\\Doctrine\\Validator\\Constraints\\UniqueEntity\\Validator` |
+| Validator      | :class:`Symfony\\Bridge\\Doctrine\\Validator\\Constraints\\UniqueEntityValidator`   |
 +----------------+-------------------------------------------------------------------------------------+
 
 Basic Usage

reference/dic_tags.rst

@@ -77,7 +77,7 @@ A form type extension can modify any part of any field in your form. To create
 a form type extension, first create a class that implements the
 :class:`Symfony\\Component\\Form\\FormTypeExtensionInterface` interface.
 For simplicity, you'll often extend an
-:class:`Symfony\\Component\\Form\\AbstractTypeExtension`` class instead of
+:class:`Symfony\\Component\\Form\\AbstractTypeExtension` class instead of
 the interface directly::
 
     // src/Acme/MainBundle/Form/Type/MyFormTypeExtension.php
@@ -667,7 +667,7 @@ Then, tag it with the ``validator.initializer`` tag (it has no options).
 
 For an example, see the ``EntityInitializer`` class inside the Doctrine Bridge.
 
-.. _`Twig's documentation`: http://twig.sensiolabs.org/doc/extensions.html
+.. _`Twig's documentation`: http://twig.sensiolabs.org/doc/advanced.html#creating-an-extension
 .. _`Twig official extension repository`: http://github.com/fabpot/Twig-extensions
 .. _`KernelEvents`: https://github.com/symfony/symfony/blob/2.0/src/Symfony/Component/HttpKernel/KernelEvents.php
 .. _`SwiftMailer's Plugin Documentation`: http://swiftmailer.org/docs/plugins.html