From 4c3ce84a46e44e569407e4354e0e2fe58b5c4acd Mon Sep 17 00:00:00 2001 From: Guangdong Liu <804167098@qq.com> Date: Thu, 12 Dec 2024 20:26:25 +0800 Subject: [PATCH] fix dead link (#36) * fix dead link * Update content/en/documentation/for-adopters/_index.md Co-authored-by: andrea bertagnolli --------- Co-authored-by: andrea bertagnolli --- content/en/documentation/for-adopters/_index.md | 2 +- .../for-contributors/data-plane/data-plane-signaling/_index.md | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/documentation/for-adopters/_index.md b/content/en/documentation/for-adopters/_index.md index e868453..a9ded01 100644 --- a/content/en/documentation/for-adopters/_index.md +++ b/content/en/documentation/for-adopters/_index.md @@ -47,7 +47,7 @@ The Data Plane is responsible for executing data transfers, which are managed by data using specialized technology such as a messaging system or data integration platform. EDC includes the *Data Plane Framework (DPF)* for building custom Data Planes. Alternatively, a Data Plane can be built using other languages or technologies and integrated with the EDC Control Plane by implementing -the [Data Plane Signaling API](https://github.com/eclipse-edc/Connector/blob/main/docs/developer/data-plane-signaling/data-plane-signaling.md). +the [Data Plane Signaling API](/documentation/for-contributors/data-plane/data-plane-signaling/). ### Federated Catalog diff --git a/content/en/documentation/for-contributors/data-plane/data-plane-signaling/_index.md b/content/en/documentation/for-contributors/data-plane/data-plane-signaling/_index.md index a9ee441..b1fb067 100644 --- a/content/en/documentation/for-contributors/data-plane/data-plane-signaling/_index.md +++ b/content/en/documentation/for-contributors/data-plane/data-plane-signaling/_index.md @@ -4,7 +4,6 @@ weight: 20 --- -* [The Data Plane Signaling interface](#the-data-plane-signaling-interface) * [1. `DataAddress` and `EndpointDataReference`](#1-dataaddress-and-endpointdatareference) * [2. Signaling protocol messages and API endpoints](#2-signaling-protocol-messages-and-api-endpoints) * [2.1 `START`](#21-start)