diff --git a/documentation/trunk/solutions/gui-building/eiffelvision-2/How-to-build-a-concurrent-graphical-application--EiffelVision-with-SCOOP.wiki b/documentation/trunk/solutions/gui-building/eiffelvision-2/How-to-build-a-concurrent-graphical-application--EiffelVision-with-SCOOP.wiki
index 355d9213..2fc73005 100644
--- a/documentation/trunk/solutions/gui-building/eiffelvision-2/How-to-build-a-concurrent-graphical-application--EiffelVision-with-SCOOP.wiki
+++ b/documentation/trunk/solutions/gui-building/eiffelvision-2/How-to-build-a-concurrent-graphical-application--EiffelVision-with-SCOOP.wiki
@@ -30,6 +30,6 @@ Now you can start using EiffelVision as you are used to, by sending GUI requests
 * For requests coming from the same processor just use the <eiffel>EV_APPLICATION</eiffel> object directly.
 * For requests coming from another processor, you can get the access through the feature <eiffel>ev_separate_application</eiffel> of class <eiffel>EV_SHARED_APPLICATION</eiffel>.
 
-Note that only one <eiffel>EV_APPLICATION<eiffel> object can be used, therefore all GUI objects have to be created in the region of this object.
+Note that only one <eiffel>EV_APPLICATION</eiffel> object can be used, therefore all GUI objects have to be created in the region of this object.
 
 That's all! Happy concurrent Eiffeling. 
\ No newline at end of file