summaryrefslogtreecommitdiffstats
path: root/documentation/clientside/clientside-compiling.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/clientside/clientside-compiling.asciidoc')
-rw-r--r--documentation/clientside/clientside-compiling.asciidoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/clientside/clientside-compiling.asciidoc b/documentation/clientside/clientside-compiling.asciidoc
index 6a6f87f0e3..6304781d98 100644
--- a/documentation/clientside/clientside-compiling.asciidoc
+++ b/documentation/clientside/clientside-compiling.asciidoc
@@ -10,7 +10,7 @@ layout: page
A client-side module, either a Vaadin widget set or a pure client-side module, needs to be compiled to JavaScript using the Vaadin Client Compiler.
Widget set compilation is most often needed when using add-ons.
-In that case, the widget sets from different add-ons are compiled into an _application widget set_, as described in <<dummy/../../../framework/addons/addons-overview.asciidoc#addons.overview, "Using Vaadin Add-ons">>.
+In that case, the widget sets from different add-ons are compiled into an _application widget set_, as described in <<../addons/addons-overview.asciidoc#addons.overview, "Using Vaadin Add-ons">>.
When doing client-side development, you need to compile the widget set every time you modify the client-side code.
@@ -81,7 +81,7 @@ As this is not the case when developing custom widgets, you must use the `local`
Local compilation is the default mode, so you only need to enable it if you have changed the mode to use the online service.
-See <<DUMMY/../../addons/addons-maven#addons.maven.modes, "Widget Set Modes">> for more information.
+See <<../addons/addons-maven#addons.maven.modes, "Widget Set Modes">> for more information.
[[clientside.compiling.maven.compiling]]
=== Compiling