Removed first slash in [[ref:libraries/...]] wiki links.

git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1612 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/trunk/eiffelstudio/eiffelstudio-how-tos/compiling/tuning-program.wiki

@@ -5,7 +5,7 @@ The best way to speed up a program is of course to improve the algorithms and da
 
 Try to keep the number of classes and objects in your system as low as possible to ensure maximum efficiency. This should never hinder the design of the system, though.
 
-You can also use the functionality provided by the [[ref:/libraries/base/reference/memory_chart|MEMORY]]  class to tweak the garbage collector behavior according to your needs. However, be careful with this, since providing erroneous parameters might lead to memory leaks, huge memory consumption, or on the contrary a dramatic slow down of the application. If you are not entirely sure what a parameter is for, avoid changing it. The default values should fit for most standard applications. 
+You can also use the functionality provided by the [[ref:libraries/base/reference/memory_chart|MEMORY]]  class to tweak the garbage collector behavior according to your needs. However, be careful with this, since providing erroneous parameters might lead to memory leaks, huge memory consumption, or on the contrary a dramatic slow down of the application. If you are not entirely sure what a parameter is for, avoid changing it. The default values should fit for most standard applications. 
 
 On top of that, EiffelStudio provides powerful optimizations, some being done automatically, others being configurable. To obtain a maximum efficiency, it is recommended to [[Generating executables|Finalize]]  your program from scratch and without using precompiled libraries. 
 

documentation/trunk/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/handling-exceptions.wiki

@@ -1,9 +1,9 @@
 [[Property:title|Handling exceptions]]
 [[Property:weight|4]]
 [[Property:uuid|43ce73b9-3ac4-4f71-34a3-f359a66d9082]]
-It is possible to raise and catch exceptions in Eiffel. Catching exceptions is done by using the rescue keyword. The [[ref:/libraries/base/reference/exceptions_chart|EXCEPTIONS]]  class provides helper features to analyze the caught exception and handle it. 
+It is possible to raise and catch exceptions in Eiffel. Catching exceptions is done by using the rescue keyword. The [[ref:libraries/base/reference/exceptions_chart|EXCEPTIONS]]  class provides helper features to analyze the caught exception and handle it. 
 
-The [[ref:/libraries/base/reference/exceptions_chart|EXCEPTIONS]] class also provides ways to raise exception, via its feature [[ref:libraries/base/reference/exceptions_flatshort|raise]] . 
+The [[ref:libraries/base/reference/exceptions_chart|EXCEPTIONS]] class also provides ways to raise exception, via its feature [[ref:libraries/base/reference/exceptions_flatshort|raise]] . 
 
 When an exception is raised while the application is being debugged, the application stops immediately and the debugger displays the context in which the exception occurred, whether or not the exception is rescued.
 

documentation/trunk/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/profiling.wiki

@@ -18,7 +18,7 @@ By default the profiler will profile the entire program. However it is possible
 * You must [[Generating executables|recompile]]  your project for the changes to take effect. 
 
 It is also possible to dynamically start and stop the profiler in a program. To do this:
-* Create an object of type [[ref:/libraries/base/reference/profiling_setting_chart|PROFILING_SETTING]] . 
+* Create an object of type [[ref:libraries/base/reference/profiling_setting_chart|PROFILING_SETTING]] . 
 * Call [[ref:libraries/base/reference/profiling_setting_flatshort|start_profiling]]  on this object to start the profiler. 
 * Call [[ref:libraries/base/reference/profiling_setting_flatshort|stop_profiling]]  on this object to stop the profiler. 
 

documentation/trunk/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/tracing.wiki

@@ -43,7 +43,7 @@ Last, here's the output when '''Trace''' is '''True''' for both the root cluster
 =Dynamic control=
 
 It is also possible to enable and disable the trace dynamically. To do this:
-* Create an object of type [[ref:/libraries/base/reference/tracing_setting_chart|TRACING_SETTING]] . 
+* Create an object of type [[ref:libraries/base/reference/tracing_setting_chart|TRACING_SETTING]] . 
 * Call [[ref:libraries/base/reference/tracing_setting_flatshort|enable_tracing]]  on this object to start the trace. 
 * Call [[ref:libraries/base/reference/tracing_setting_flatshort|disable_tracing]]  on this object to stop the trace.