From 3da37792cf5de631be6bf43d06f08d2545a295e9 Mon Sep 17 00:00:00 2001
From: Michael Steinert <133106264+MichaelSteinert@users.noreply.github.com>
Date: Fri, 20 Oct 2023 09:40:44 +0200
Subject: [PATCH] fix: add missing edc-control-plane-api-client dependency
 (#134) (#138)

add missing edc-control-plane-api-client dependency
---
 transfer/transfer-07-provider-push-http/README.md      | 10 +++++-----
 .../http-push-connector/build.gradle.kts               |  1 +
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/transfer/transfer-07-provider-push-http/README.md b/transfer/transfer-07-provider-push-http/README.md
index f70fc3b9..a6769761 100644
--- a/transfer/transfer-07-provider-push-http/README.md
+++ b/transfer/transfer-07-provider-push-http/README.md
@@ -1,12 +1,12 @@
 # Implement a simple "Provider Push" Http transfer flow
 
-The purpose of this example is to show a data exchange between 2 connectors, one representing the
-data provider and the other, the consumer. It's based on a provider push usecase that you can find
+The purpose of this example is to show a data exchange between two connectors, one representing the
+data provider and the other, the consumer. It's based on a provider push use case that you can find
 more details
-on [Transfer data plane documentation](https://github.com/eclipse-edc/Connector/tree/main/extensions/control-plane/transfer/transfer-data-plane)
+on [Transfer data plane documentation](https://github.com/eclipse-edc/Connector/tree/main/extensions/control-plane/transfer/transfer-data-plane).
 For the sake of simplicity, the provider and the consumer
 will be on the same machine, but in a real world configuration, they will likely be on different
-machines. The final goal of this example is to present the steps through which the 2 connectors will
+machines. The final goal of this example is to present the steps through which the two connectors will
 have to pass so that the consumer can have access to the data, held by the provider.
 
 Those steps are the following:
@@ -297,7 +297,7 @@ looks as follows:
    reference
 
 Of course, this is the simplest possible negotiation sequence. Later on, both connectors can also
-send counter offers in addition to just confirming or declining an offer.
+send counteroffers in addition to just confirming or declining an offer.
 
 ```bash
 curl -d '{
diff --git a/transfer/transfer-07-provider-push-http/http-push-connector/build.gradle.kts b/transfer/transfer-07-provider-push-http/http-push-connector/build.gradle.kts
index 2961bee7..86bc1e6b 100644
--- a/transfer/transfer-07-provider-push-http/http-push-connector/build.gradle.kts
+++ b/transfer/transfer-07-provider-push-http/http-push-connector/build.gradle.kts
@@ -24,6 +24,7 @@ repositories {
 
 dependencies {
     implementation(libs.edc.control.plane.core)
+    implementation(libs.edc.control.plane.api.client)
     implementation(libs.edc.dsp)
     implementation(libs.edc.configuration.filesystem)
     implementation(libs.edc.vault.filesystem)