From 8fbe0a1cc633e49ac9db8068ac61c489f2b9d98c Mon Sep 17 00:00:00 2001
From: Sebastian Opriel <22075788+SebastianOpriel@users.noreply.github.com>
Date: Tue, 29 Oct 2024 18:38:26 +0100
Subject: [PATCH] Update initiating-transfer.md

Remove HTTPProxy hint
---
 docs/Frontend/Consuming/initiating-transfer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Frontend/Consuming/initiating-transfer.md b/docs/Frontend/Consuming/initiating-transfer.md
index 60de66b41..811269f73 100644
--- a/docs/Frontend/Consuming/initiating-transfer.md
+++ b/docs/Frontend/Consuming/initiating-transfer.md
@@ -56,7 +56,7 @@ For more advanced data-sink endpoints not directly supported by the UI, you can
 ```
 {% endcode %}
 
-Here, `"type": "HttpData"` indicates that the EDC will interpret the destination as a REST-API. The `baseUrl` is the endpoint receiving the data. You can also set the type to `HttpProxy`, enabling a pull-transfer over both data planes.
+Here, `"type": "HttpData"` indicates that the EDC will interpret the destination as a REST-API. The `baseUrl` is the endpoint receiving the data.
 
 #### 3. Transfer Data via Custom Transfer Process Request (JSON)