From 6bffdc53c207c177c2cedf1c1432c696bd6c4a7a Mon Sep 17 00:00:00 2001
From: juhopiirainen <49151232+juhopiirainen@users.noreply.github.com>
Date: Wed, 15 May 2019 09:27:58 +0300
Subject: Fix the broken links in the documentation

---
 .../articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc')

diff --git a/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc b/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
index dd00b9fc00..77c4963f92 100644
--- a/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
+++ b/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
@@ -8,12 +8,12 @@ layout: page
 = Integrating a JavaScript library as an extension
 
 JavaScript can also be used for creating Extensions e.g. for integrating
-existing JavaScript libraries. See link:CreatingAUIExtension.asciidoc[Creating a UI extension] for general information about Extensions. The main
+existing JavaScript libraries. See <<CreatingAUIExtension#, Creating a UI extension>> for general information about Extensions. The main
 difference when using JavaScript is that you extend
 `AbstractJavaScriptExtension`, that your shared state class should
 extend `JavaScriptExtensionState` and then of course that your
-client-side implementation is written in JavaScript. See link:IntegratingAJavaScriptComponent.asciidoc[Integrating a
-JavaScript component] for basic information about how to use JavaScript
+client-side implementation is written in JavaScript. See <<IntegratingAJavaScriptComponent#, Integrating a
+JavaScript component>> for basic information about how to use JavaScript
 for your client-side logic.
 
 This tutorial will create a simple Extension for integrating
-- 
cgit v1.2.3

