Updated the references to the Symfony Profiler documentation

Author: javiereguiluz

cookbook/email/testing.rst

@@ -8,7 +8,7 @@ Sending e-mails with Symfony is pretty straightforward thanks to the
 SwiftmailerBundle, which leverages the power of the `Swift Mailer`_ library.
 
 To functionally test that an email was sent, and even assert the email subject,
-content or any other headers, you can use :ref:`the Symfony Profiler <internals-profiler>`.
+content or any other headers, you can use :doc:`the Symfony Profiler </cookbook/profiler>`.
 
 Start with an easy controller action that sends an e-mail::
 

cookbook/profiler/data_collector.rst

@@ -4,7 +4,7 @@
 How to Create a custom Data Collector
 =====================================
 
-The Symfony :ref:`Profiler <internals-profiler>` delegates data collecting to
+:doc:`The Symfony Profiler </cookbook/profiler>` delegates data collecting to
 data collectors. Symfony comes bundled with a few of them, but you can easily
 create your own.
 

cookbook/testing/profiling.rst

@@ -9,7 +9,7 @@ you write functional tests that monitor your production servers, you might
 want to write tests on the profiling data as it gives you a great way to check
 various things and enforce some metrics.
 
-The Symfony :ref:`Profiler <internals-profiler>` gathers a lot of data for
+:doc:`The Symfony Profiler </cookbook/profiler>` gathers a lot of data for
 each request. Use this data to check the number of database calls, the time
 spent in the framework, etc. But before writing assertions, enable the profiler
 and check that the profiler is indeed available (it is enabled by default in