Update http_multipart.rst

Author: magicmark

docs/transports/http_multipart.rst

@@ -17,9 +17,8 @@ Reference: :class:`gql.transport.http_multipart_transport.HTTPMultipartTransport
 
 .. note::
 
-    This transport is specifically designed for GraphQL subscriptions. While it can handle
-    queries and mutations via the ``execute()`` method, standard HTTP transports like
-    :ref:`AIOHTTPTransport <aiohttp_transport>` are more efficient for those operations.
+    This transport is specifically designed for GraphQL subscriptions. It does not support
+    mutations or queries.
 
 .. literalinclude:: ../code_examples/http_multipart_async.py
 
@@ -40,21 +39,7 @@ with GraphQL execution results.
 Protocol Details
 ----------------
 
-**Message Format**
-
-Each message part follows this structure:
-
-.. code-block:: text
-
-    --graphql
-    Content-Type: application/json
-
-    {"payload": {"data": {...}, "errors": [...]}}
-
-**Heartbeats**
-
-Servers may send empty JSON objects (``{}``) as heartbeat messages to keep the
-connection alive. These are automatically filtered out by the transport.
+See https://www.apollographql.com/docs/graphos/routing/operations/subscriptions/multipart-protocol
 
 **Error Handling**
 
@@ -63,14 +48,6 @@ The protocol distinguishes between two types of errors:
 - **GraphQL errors**: Returned within the ``payload`` property alongside data
 - **Transport errors**: Returned with a top-level ``errors`` field and ``null`` payload
 
-**End of Stream**
-
-The subscription ends when the server sends the final boundary marker:
-
-.. code-block:: text
-
-    --graphql--
-
 Authentication
 --------------