Fix all broken links

Author: wouterj

book/doctrine.rst

@@ -362,7 +362,7 @@ see the :ref:`book-doctrine-field-types` section.
     `Reserved SQL keywords documentation`_ on how to properly escape these
     names. Alternatively, if you're free to choose your database schema,
     simply map to a different table name or column name. See Doctrine's
-    `Persistent classes`_ and `Property Mapping`_ documentation.
+    `Creating Classes for the Database`_ and `Property Mapping`_ documentation.
 
 .. note::
 
@@ -1429,7 +1429,7 @@ For more information about Doctrine, see the *Doctrine* section of the
 .. _`Property Mapping`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/basic-mapping.html#property-mapping
 .. _`Lifecycle Events documentation`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/events.html#lifecycle-events
 .. _`Reserved SQL keywords documentation`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/basic-mapping.html#quoting-reserved-words
-.. _`Persistent classes`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/basic-mapping.html#persistent-classes
+.. _`Creating Classes for the Database`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/basic-mapping.html#creating-classes-for-the-database
 .. _`DoctrineMongoDBBundle`: https://symfony.com/doc/current/bundles/DoctrineMongoDBBundle/index.html
 .. _`migrations`: https://symfony.com/doc/current/bundles/DoctrineMigrationsBundle/index.html
 .. _`DoctrineFixturesBundle`: https://symfony.com/doc/current/bundles/DoctrineFixturesBundle/index.html

book/http_fundamentals.rst

@@ -578,6 +578,6 @@ sensible defaults. For more advanced users, the sky is the limit.
 .. _`Live HTTP Headers`: https://addons.mozilla.org/en-US/firefox/addon/live-http-headers/
 .. _`List of HTTP status codes`: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
 .. _`List of HTTP header fields`: https://en.wikipedia.org/wiki/List_of_HTTP_header_fields
-.. _`List of common media types`: https://en.wikipedia.org/wiki/Internet_media_type#List_of_common_media_types
+.. _`List of common media types`: https://www.iana.org/assignments/media-types/media-types.xhtml
 .. _`Validator`: https://github.com/symfony/Validator
 .. _`Swift Mailer`: http://swiftmailer.org/

book/templating.rst

@@ -1025,9 +1025,9 @@ but Symfony provides a more dynamic option via the ``asset`` Twig function:
         <link href="<?php echo $view['assets']->getUrl('css/blog.css') ?>" rel="stylesheet" />
 
 The ``asset`` function's main purpose is to make your application more portable.
-If your application lives at the root of your host (e.g. http://example.com),
+If your application lives at the root of your host (e.g. ``http://example.com``),
 then the rendered paths should be ``/images/logo.png``. But if your application
-lives in a subdirectory (e.g. http://example.com/my_app), each asset path
+lives in a subdirectory (e.g. ``http://example.com/my_app``), each asset path
 should render with the subdirectory (e.g. ``/my_app/images/logo.png``). The
 ``asset`` function takes care of this by determining how your application is
 being used and generating the correct paths accordingly.

cookbook/deployment/heroku.rst

@@ -326,7 +326,7 @@ This is also very useful to build assets on the production system, e.g. with Ass
 
 .. _`the original article`: https://devcenter.heroku.com/articles/getting-started-with-symfony2
 .. _`sign up with Heroku`: https://signup.heroku.com/signup/dc
-.. _`Heroku Toolbelt`: https://devcenter.heroku.com/articles/getting-started-with-php#local-workstation-setup
+.. _`Heroku Toolbelt`: https://devcenter.heroku.com/articles/getting-started-with-php#set-up
 .. _`getting Started with PHP on Heroku`: https://devcenter.heroku.com/articles/getting-started-with-php
 .. _`ephemeral file system`: https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem
 .. _`Logplex`: https://devcenter.heroku.com/articles/logplex

cookbook/form/data_transformers.rst

@@ -48,7 +48,7 @@ Suppose you have a Task form with a description ``textarea`` type::
 But, there are two complications:
 
 #. Your users are allowed to use *some* HTML tags, but not others: you need a way
-   to call :phpfunction:`striptags` after the form is submitted;
+   to call :phpfunction:`strip_tags` after the form is submitted;
 
 #. To be friendly, you want to convert ``<br/>`` tags into line breaks (``\n``) before
    rendering the field so the text is easier to edit.

cookbook/form/unit_testing.rst

@@ -263,4 +263,4 @@ easily testing against multiple sets of data.
 You can also pass another argument, such as a boolean if the form has to
 be synchronized with the given set of data or not etc.
 
-.. _`data providers`: http://www.phpunit.de/manual/current/en/writing-tests-for-phpunit.html#writing-tests-for-phpunit.data-providers
+.. _`data providers`: https://phpunit.de/manual/current/en/writing-tests-for-phpunit.html#writing-tests-for-phpunit.data-providers

cookbook/templating/PHP.rst

@@ -353,4 +353,4 @@ instance, to output something in a JavaScript script, use the ``js`` context::
 
     <?php echo $view->escape($var, 'js') ?>
 
-.. _`@Template`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/view`
+.. _`@Template`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/view

cookbook/web_server/built_in.rst

@@ -74,4 +74,4 @@ you have to pass the correct location using the ``--docroot`` option:
     $ php app/console server:run --docroot=public_html
 
 .. _`built-in web server`: http://www.php.net/manual/en/features.commandline.webserver.php
-.. _`php.net`: http://php.net/manual/en/features.commandline.webserver.php#example-401
+.. _`php.net`: http://php.net/manual/en/features.commandline.webserver.php#example-411

create_framework/dependency-injection.rst

@@ -239,5 +239,5 @@ micro-framework, and especially its `Application`_ class.
 Have fun!
 
 .. _`Pimple`: https://github.com/fabpot/Pimple
-.. _`Silex`: https://silex.sensiolabs.org/
+.. _`Silex`: http://silex.sensiolabs.org/
 .. _`Application`: https://github.com/fabpot/Silex/blob/master/src/Silex/Application.php

create_framework/http-foundation.rst

@@ -301,7 +301,7 @@ component is the start of better interoperability between all frameworks and
 applications using it (like `Symfony`_, `Drupal 8`_, `phpBB 4`_, `ezPublish
 5`_, `Laravel`_, `Silex`_, and `more`_).
 
-.. _`Twig`: http://twig.sensiolabs.com/
+.. _`Twig`: http://twig.sensiolabs.org/
 .. _`Symfony versus Flat PHP`: http://symfony.com/doc/current/book/from_flat_php_to_symfony2.html
 .. _`HTTP specification`: http://tools.ietf.org/wg/httpbis/
 .. _`audited`: http://symfony.com/blog/symfony2-security-audit