Address code review feedback: use Sphinx directives and remove duplication

Co-authored-by: nijel <[email protected]>

Author: Copilot

docs/pipeline.rst

@@ -50,6 +50,8 @@ Pipeline functions can return three types of values, each with different behavio
                # Interrupt pipeline and redirect user
                return redirect('/some-form/')
 
+.. _common-function-parameters:
+
 Common Function Parameters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -167,8 +169,10 @@ A pipeline that won't create users, just accepts already registered ones would l
         'social_core.pipeline.user.user_details',
     )
 
-**Note:** This example removes ``get_username`` and ``create_user`` steps, so only 
-users who have previously authenticated can log in.
+.. note::
+
+   This example removes ``get_username`` and ``create_user`` steps, so only 
+   users who have previously authenticated can log in.
 
 **Example 2: Custom User Loading**
 
@@ -279,7 +283,9 @@ Here's a simple example of collecting additional user information::
         # No email yet - interrupt pipeline and show form
         return strategy.render_html('email_form.html')
 
-In your template, the form should POST to ``/complete/<backend>/``::
+In your template, the form should POST to ``/complete/<backend>/``.
+
+**Django example**::
 
     <form method="post" action="{% url 'social:complete' backend %}">
         {% csrf_token %}
@@ -409,9 +415,11 @@ Steps to Add a Custom Pipeline Function
 2. **Place it in an importable location** in your project
 3. **Add it to the pipeline** in your settings at the appropriate position
 
-**Important:** Function placement matters! The order determines what data is available.
-For example, placing your function after ``create_user`` ensures you receive a ``user`` 
-instance rather than ``None``.
+.. important::
+
+   Function placement matters! The order determines what data is available.
+   For example, placing your function after ``create_user`` ensures you receive a ``user`` 
+   instance rather than ``None``.
 
 Writing Custom Pipeline Functions
 ----------------------------------
@@ -425,48 +433,12 @@ Your function should accept the common parameters and ``**kwargs``::
         # Your code here
         pass
 
-**Tip:** Always include ``**kwargs`` to handle additional parameters from other 
-pipeline functions or future versions.
-
-Common Parameters Available
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Depending on where you place your function in the pipeline, these parameters may be available:
-
-``strategy``
-    The current strategy instance.
-
-``backend``
-    The current backend instance.
-
-``uid``
-    User ID in the provider, this ``uid`` should identify the user in the
-    current provider.
-
-``response = {} or object()``
-    The server user-details response, it depends on the protocol in use (and
-    sometimes the provider implementation of such protocol), but usually it's
-    just a ``dict`` with the user profile details from the provider. Lots of
-    information related to the user is provided here, sometimes the ``scope``
-    will increase the amount of information in this response on OAuth
-    providers.
-
-``details = {}``
-    Basic user details generated by the backend, used to create/update the user
-    model details (this ``dict`` will contain values like ``username``,
-    ``email``, ``first_name``, ``last_name`` and ``fullname``).
-
-``user = None``
-    The user instance (or ``None`` if not yet created or retrieved).
-
-``social = None``
-    The ``UserSocialAuth`` instance for the user (or ``None`` if not yet created).
+.. tip::
 
-``is_new``
-    Boolean flag indicating if the user was just created (``True``) or already existed (``False``).
+   Always include ``**kwargs`` to handle additional parameters from other 
+   pipeline functions or future versions.
 
-``request``
-    The current HTTP request object.
+See :ref:`common-function-parameters` for details on the parameters available to pipeline functions.
 
 Practical Example: Saving User Profile Data
 --------------------------------------------