X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/66b0686fe441796325c3b5738b1b880d15ce1ea6..c53d0aac5a5ab41701f3320d95f1cd2b0f3fd005:/doc/gtut-tour-08-exceptions.doc?ds=sidebyside

diff --git a/doc/gtut-tour-08-exceptions.doc b/doc/gtut-tour-08-exceptions.doc
index 057e9bf7fd..a91771d12f 100644
--- a/doc/gtut-tour-08-exceptions.doc
+++ b/doc/gtut-tour-08-exceptions.doc
@@ -62,7 +62,7 @@ CATCH(e) {
 Another strange thing is that you should actually free the memory allocated
 to the exception with xbt_ex_fres() if you manage to deal with them. There
 is a bit more than this on the picture (#TRY_CLEANUP blocks, for example), and
-you should check the section \ref XBT_ex for more details.
+you should check the section \ref XBT_ex for more details.
 
 You should be <b>very carfull</b> when using the exceptions. They work great
 when used correctly, but there is a few golden rules you should never break.
@@ -109,7 +109,7 @@ have to find from itself. For this, it will try to open socket and send the
 kill message to each ports of the search range. If it manage to close the
 socket after sending the message without being interrupted by an exception,
 it can assume that it killed the server and stop searching.
-\dontinclude 08-exceptions.c
+\don'tinclude 08-exceptions.c
 \skip port=3000
 \until end_of_loop
 
@@ -117,7 +117,7 @@ To make the game a bit more fun (and to show you what an exception actually
 look like when it's not catched), we add a potential command line argument
 to the server, asking it to cheat and to not open its port within the search
 range but elsewhere:
-\dontinclude 08-exceptions.c
+\don'tinclude 08-exceptions.c
 \skip strcmp
 \until gras_socket_my_port
 \until }