Changes in 272484d: tried to fix wiki links

				wiki/howto/development/local-gwt.md
			
          @@ -24,7 +24,7 @@ Those tags must be put into the *.gwt.xml files e.g. "AdminConsole.gwt.xml".

           ## Debugging GWT

           ### Super dev Mode

          -To debug GWT using the super dev Mode start the SailingServer according to your environment, then launch the GWT Sailing SDM in debug mode. After the initial compile all entry points will show up in the development Mode section. Do not use these entry points. Instead, to start debugging the web application open the debug drop down and select ``Debug Configurations..``. In the newly opened menu open the node ``Launch Chrome`` and select the configuration fitting your needs. To start the debug session just press debug.

          +For further instructions look [here](./development/super-dev-mode.md). 

           ### dev Mode (deprecated)

           One of the great strengths of GWT is the use of Eclipse as a Java source-level debugging environment. To enjoy this feature, launch the SailingServer launch config appropriate for your environment (Proxy / No Proxy), then launch the SailingGWT launch configuration in debug mode. After a while it will show a "Development Mode" view that shows all entry points that have been initialized. Double-click on the one you want to debug, and your default browser (hopefully FireFox, because with other browsers the GWT debug plugin tends to be not very stable or not even present) will open.

				wiki/howto/onboarding.md
			
          @@ -152,7 +152,7 @@ Out of the box, multiple settings in Eclipse need to be changed. Go to Window 

              - Press "List Races"

           6. Further useful launch configurations

              - Use SAP JVM Profiler. If you used the script above and installed the SAPJVM instead of the jdk, you can now open the profiling perspective by clicking on Window ⇒ Perspective ⇒ Open Perspective ⇒ Profiling)

          -   - Debugging gwt: For further instructions please see [here](./development/local-gwt.md#Working-with-GET-Locally_Debugging-GWT_Super-dev-Mode)

          +   - Debugging gwt: For further instructions please see [here](./development/super-dev-mode.md)

           ### Build for deployment

           Open a shell (preferrably a git bash or a cygwin bash), cd to the git workspace's root folder and issue "./configuration/buildAndUpdateProduct.sh build". This should build the software and run all the tests. If you want to avoid the tests being executed, use the -t option. If you only want to build one GWT permutation (Chrome/English), use the -b option. When inside the SAP VPN, add the -p option for proxy use. Run the build script without arguments to get usage hints.

...	...	@@ -24,7 +24,7 @@ Those tags must be put into the *.gwt.xml files e.g. "AdminConsole.gwt.xml".
24	24
25	25	## Debugging GWT
26	26	### Super dev Mode
27		-To debug GWT using the super dev Mode start the SailingServer according to your environment, then launch the GWT Sailing SDM in debug mode. After the initial compile all entry points will show up in the development Mode section. Do not use these entry points. Instead, to start debugging the web application open the debug drop down and select ``Debug Configurations..``. In the newly opened menu open the node ``Launch Chrome`` and select the configuration fitting your needs. To start the debug session just press debug.
	27	+For further instructions look [here](./development/super-dev-mode.md).
28	28	### dev Mode (deprecated)
29	29	One of the great strengths of GWT is the use of Eclipse as a Java source-level debugging environment. To enjoy this feature, launch the SailingServer launch config appropriate for your environment (Proxy / No Proxy), then launch the SailingGWT launch configuration in debug mode. After a while it will show a "Development Mode" view that shows all entry points that have been initialized. Double-click on the one you want to debug, and your default browser (hopefully FireFox, because with other browsers the GWT debug plugin tends to be not very stable or not even present) will open.
30	30

...	...	@@ -152,7 +152,7 @@ Out of the box, multiple settings in Eclipse need to be changed. Go to Window
152	152	- Press "List Races"
153	153	6. Further useful launch configurations
154	154	- Use SAP JVM Profiler. If you used the script above and installed the SAPJVM instead of the jdk, you can now open the profiling perspective by clicking on Window ⇒ Perspective ⇒ Open Perspective ⇒ Profiling)
155		- - Debugging gwt: For further instructions please see [here](./development/local-gwt.md#Working-with-GET-Locally_Debugging-GWT_Super-dev-Mode)
	155	+ - Debugging gwt: For further instructions please see [here](./development/super-dev-mode.md)
156	156
157	157	### Build for deployment
158	158	Open a shell (preferrably a git bash or a cygwin bash), cd to the git workspace's root folder and issue "./configuration/buildAndUpdateProduct.sh build". This should build the software and run all the tests. If you want to avoid the tests being executed, use the -t option. If you only want to build one GWT permutation (Chrome/English), use the -b option. When inside the SAP VPN, add the -p option for proxy use. Run the build script without arguments to get usage hints.