7 files changed, 14 insertions, 14 deletions
diff --git a/documentation/gwt/gwt-connector.asciidoc b/documentation/gwt/gwt-connector.asciidoc
index f8fcb5dbe3..b0c276d41a 100644
--- a/documentation/gwt/gwt-connector.asciidoc
+++ b/documentation/gwt/gwt-connector.asciidoc
@@ -13,7 +13,7 @@ the widget state and events to the server-side.
 
 A connector normally gets the state of the server-side component by the __shared
 state__, described later in
-<<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
+<<gwt-shared-state#gwt.shared-state,"Shared
 State">>.
 
 [[gwt.connector.basic]]
@@ -56,7 +56,7 @@ method that is called when any of the state properties is changed. A finer and
 simpler handling is achieved by using the [classname]#@OnStateChange# annotation
 on a handler method for each property, or by [classname]#@DelegateToWidget# on a
 shared state property, as described later in
-<<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
+<<../gwt/gwt-shared-state#gwt.shared-state,"Shared
 State">>.
 
 
@@ -69,7 +69,7 @@ to the widget.
 
 Server-to-client communication is normally done using a __shared state__, as
 described in
-<<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
+<<gwt-shared-state#gwt.shared-state,"Shared
 State">>, as well as RPC calls. The serialization of the state data is handled
 completely transparently.
 
@@ -77,7 +77,7 @@ ifdef::web[]
 Once the client-side engine receives the changes from the server, it reacts to
 them by creating and notifying connectors that in turn manage widgets. This is
 described in
-<<dummy/../../../framework/gwt/gwt-advanced#gwt.advanced.phases,"Client-Side
+<<gwt-advanced#gwt.advanced.phases,"Client-Side
 Processing Phases">> in more
 detail.
 endif::web[]
@@ -85,7 +85,7 @@ endif::web[]
 For client-to-server communication, a connector can make remote procedure calls
 (RPC) to the server-side. Also, the server-side component can make RPC calls to
 the connector. For a thorough description of the RPC mechanism, refer to
-<<dummy/../../../framework/gwt/gwt-rpc#gwt.rpc,"RPC Calls Between Client- and
+<<gwt-rpc#gwt.rpc,"RPC Calls Between Client- and
 Server-Side">>.
 
 
diff --git a/documentation/gwt/gwt-eclipse.asciidoc b/documentation/gwt/gwt-eclipse.asciidoc
index adbaf9fea1..1f3ed106f6 100644
--- a/documentation/gwt/gwt-eclipse.asciidoc
+++ b/documentation/gwt/gwt-eclipse.asciidoc
@@ -90,7 +90,7 @@ using the new widget set. The compilation result is written under the
 [filename]#WebContent/VAADIN/widgetsets# folder. When you need to recompile the
 widget set in Eclipse, see <<gwt.eclipse.compiling>>. For detailed information
 on compiling widget sets, see
-<<dummy/../../../framework/clientside/clientside-compiling#clientside.compiling,"Compiling
+<<../clientside/clientside-compiling#clientside.compiling,"Compiling
 a Client-Side Module">>.
 
 The following setting is inserted in the [filename]#web.xml# deployment
@@ -146,12 +146,12 @@ You can speed up the compilation significantly by compiling the widget set only
 for your browser during development. The generated [filename]#.gwt.xml#
 descriptor stub includes a disabled element that specifies the target browser.
 See
-<<dummy/../../../framework/clientside/clientside-module#gwt.module.compilation-limiting,"Limiting
+<<../clientside/clientside-module#gwt.module.compilation-limiting,"Limiting
 Compilation Targets">> for more details on setting the [literal]#++user-agent++#
 property.
 
 For more information on compiling widget sets, see
-<<dummy/../../../framework/clientside/clientside-compiling#clientside.compiling,"Compiling
+<<../clientside/clientside-compiling#clientside.compiling,"Compiling
 a Client-Side Module">>. Should you compile a widget set outside Eclipse, you
 need to refresh the project by selecting it in [guilabel]#Project Explorer# and
 pressing F5.
diff --git a/documentation/gwt/gwt-javascript.asciidoc b/documentation/gwt/gwt-javascript.asciidoc
index a46dbfc3c4..2dead86f07 100644
--- a/documentation/gwt/gwt-javascript.asciidoc
+++ b/documentation/gwt/gwt-javascript.asciidoc
@@ -233,7 +233,7 @@ mechanism, as described in the next section.
 User interaction with the JavaScript component has to be passed to the
 server-side using an RPC (Remote Procedure Call) mechanism. The JavaScript RPC
 mechanism is almost equal to regular client-side widgets, as described in
-<<dummy/../../../framework/gwt/gwt-rpc#gwt.rpc,"RPC Calls Between Client- and
+<<gwt-rpc#gwt.rpc,"RPC Calls Between Client- and
 Server-Side">>.
 
 [[gwt.javascript.rpc.handling]]
diff --git a/documentation/gwt/gwt-overview.asciidoc b/documentation/gwt/gwt-overview.asciidoc
index 16841ab791..c2e31cac68 100644
--- a/documentation/gwt/gwt-overview.asciidoc
+++ b/documentation/gwt/gwt-overview.asciidoc
@@ -53,7 +53,7 @@ event to the server-side using RPC.
 == Project Structure
 
 Widget set compilation, as described in
-<<dummy/../../../framework/clientside/clientside-module#clientside.module,"Client-Side
+<<../clientside/clientside-module#clientside.module,"Client-Side
 Module Descriptor">>, requires using a special project structure, where the
 client-side classes are located under a [filename]#client# package under the
 package of the module descriptor. Any static resources, such as stylesheets and
@@ -68,7 +68,7 @@ The basic project structure is illustrated in <<figure.gwt.overview.project>>.
 image::img/gwt-widget-files-hi.png[]
 
 The Eclipse wizard, described in
-<<dummy/../../../framework/gwt/gwt-eclipse#gwt.eclipse,"Starting It Simple With
+<<gwt-eclipse#gwt.eclipse,"Starting It Simple With
 Eclipse">>, creates a widget integration skeleton with the above structure.
 
 
diff --git a/documentation/gwt/gwt-server-side.asciidoc b/documentation/gwt/gwt-server-side.asciidoc
index 9abf389a5e..8d2d12ee5e 100644
--- a/documentation/gwt/gwt-server-side.asciidoc
+++ b/documentation/gwt/gwt-server-side.asciidoc
@@ -16,7 +16,7 @@ client-side, in addition to any server-side logic.
 == Basic Server-Side Component
 
 The component state is usually managed by a __shared state__, described later in
-<<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
+<<gwt-shared-state#gwt.shared-state,"Shared
 State">>.
 
 [source, java]
diff --git a/documentation/gwt/gwt-shared-state.asciidoc b/documentation/gwt/gwt-shared-state.asciidoc
index 422ef43e1e..2b7c919a6d 100644
--- a/documentation/gwt/gwt-shared-state.asciidoc
+++ b/documentation/gwt/gwt-shared-state.asciidoc
@@ -122,7 +122,7 @@ by delegating the property value directly to the widget, as described in
 
 ifdef::web[]
 The processing phases of state changes are described in more detail in
-<<dummy/../../../framework/gwt/gwt-advanced#gwt.advanced.phases,"Client-Side
+<<gwt-advanced#gwt.advanced.phases,"Client-Side
 Processing Phases">>.
 endif::web[]
 
diff --git a/documentation/gwt/gwt-styling.asciidoc b/documentation/gwt/gwt-styling.asciidoc
index 6a903b6524..f9c2bc0e11 100644
--- a/documentation/gwt/gwt-styling.asciidoc
+++ b/documentation/gwt/gwt-styling.asciidoc
@@ -60,7 +60,7 @@ as well.
 A client-side module, which is normally a widget set, can include stylesheets.
 They must be placed under the [filename]#public# folder under the folder of the
 widget set, a described in
-<<dummy/../../../framework/clientside/clientside-module#clientside.module.stylesheet,"Specifying
+<<../clientside/clientside-module#clientside.module.stylesheet,"Specifying
 a Stylesheet">>.
 
 For example, you could style the widget described above as follows: