X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/059ffba3002aa86e17392c7f2c884095ab64591b..8ef37a2e313de8c48edbd49a643d500dd76cebc1:/doc/gtut-tour-10-rpc.doc

diff --git a/doc/gtut-tour-10-rpc.doc b/doc/gtut-tour-10-rpc.doc
index 6591c0fe74..46c962b337 100644
--- a/doc/gtut-tour-10-rpc.doc
+++ b/doc/gtut-tour-10-rpc.doc
@@ -9,7 +9,7 @@
    - \ref GRAS_tut_tour_rpc_use_a2i_cb
    - \ref GRAS_tut_tour_rpc_use_rest
  - \ref GRAS_tut_tour_rpc_recap
-   
+
 <hr>
 
 \section GRAS_tut_tour_rpc_intro Introduction
@@ -44,7 +44,7 @@ message. In our example, we accept one string in input, and a long in
 output for the a2i conversion (a=char 2=to i=integer), and the contrary in
 the other direction.
 
-\don'tinclude 10-rpc.c
+\dontinclude 10-rpc.c
 \skip gras_msgtype_declare_rpc
 \until long
 \until string
@@ -58,11 +58,11 @@ sending back the result (we must use callbacks when doing network
 communication to avoid deadlocks and such issues). The second argument is
 the callback context that the callback got as first argument. It denotes how
 to reach the caller and such. The last argument is a pointer to a variable
-containing the result to pass to the caller. 
+containing the result to pass to the caller.
 
 Having the callee explicitly returning data to the caller allows to free
 data that were allocated to do the job asked by the client, as in this
-example. 
+example.
 
 \skip server_convert_i2a_cb
 \until end_of_convert_callback
@@ -98,7 +98,7 @@ Which produces the expected output:
 \include 10-rpc.output
 
 Now, you know how to send messages, attach callbacks and do RPCs. The next
-lesson will learn you the last missing part of the messaging library: 
+lesson will learn you the last missing part of the messaging library:
 \ref GRAS_tut_tour_explicitwait
 
 */