From a4cf8881dd90e62016ee891d2d9190f9440b95b0 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Cl=C3=A9ment=20B=C3=A9nier?= Date: Tue, 16 Apr 2019 16:47:40 +0200 Subject: [PATCH] afb-migration-to-binding-v3: fix broken links MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit - fix broken link to the same section Change-Id: I5e104c5527fae29ff51b6208f43ed0eb3c5f8c04 Signed-off-by: Clément Bénier --- docs/afb-migration-to-binding-v3.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/afb-migration-to-binding-v3.md b/docs/afb-migration-to-binding-v3.md index 29ea1790..4a8096d7 100644 --- a/docs/afb-migration-to-binding-v3.md +++ b/docs/afb-migration-to-binding-v3.md @@ -177,8 +177,8 @@ of the context and event subscriptions. The new design allows you to specify: - whether the caller or the service or both or none will receive the eventually events during the subcall. -See [calls](reference-v3/func-api/#calls-and-job-functions) and -[subcalls](reference-v3/func-req/#subcall-functions). +See [calls](reference-v3/func-api.html#calls-and-job-functions) and +[subcalls](reference-v3/func-req.html#subcall-functions). The table below list the changes to apply: @@ -197,4 +197,4 @@ Consider use of event handlers Binding V3 brings new ways of handling event in services. You can register functions that will handle specific events and that accept closure arguments. -See [**afb_api_event_handler_add** and **afb_api_event_handler_del**](reference-v3/func-api/#event-functions) +See [**afb_api_event_handler_add** and **afb_api_event_handler_del**](reference-v3/func-api.html#event-functions) -- 2.16.6