[GNUnet-SVN] r32935 - gnunet-java/doc

[gnunet]

Author: dold
Date: 2014-04-07 17:20:45 +0200 (Mon, 07 Apr 2014)
New Revision: 32935

Modified:
   gnunet-java/doc/gnunet-java-tutorial.pdf
   gnunet-java/doc/gnunet-java-tutorial.tex
Log:
typos

Modified: gnunet-java/doc/gnunet-java-tutorial.pdf
===================================================================
(Binary files differ)

Modified: gnunet-java/doc/gnunet-java-tutorial.tex
===================================================================
--- gnunet-java/doc/gnunet-java-tutorial.tex    2014-04-07 15:05:15 UTC (rev 
32934)
+++ gnunet-java/doc/gnunet-java-tutorial.tex    2014-04-07 15:20:45 UTC (rev 
32935)
@@ -269,7 +269,7 @@
 You can define a new type of message in GNUnet-Java by annotating a
 class with information on how to represent its members in binary format.
 
-Additionaly, you have to register your new message type with
+Additionally, you have to register your new message type with
 GNUnet-Java, giving it a unique message type number.  Here is an example:
 
 \begin{lstlisting}[language=java]
@@ -306,7 +306,7 @@
 Other useful annotations can be found in the package {\tt
   org.gnunet.construct}. Among them are annotations for arrays of
 fixed or variable size ({\tt @VariableSizeArray, @FixedSizeArray}),
-for embeding other messages in your message ({\tt @NestedMessage} and
+for embedding other messages in your message ({\tt @NestedMessage} and
 for implementing your own message unions.
 
 \exercise{Define a message that contains a 32-bit signed integer.}
@@ -343,7 +343,7 @@
 }
 \end{lstlisting}
 
-After specifing your message handler, the {\tt init} method has to be
+After specifying your message handler, the {\tt init} method has to be
 called with a callback object.  This starts the handshake with the
 CORE service, and once done the callback object's {\tt onInit} method will
 be called with your peer's identity.
@@ -529,7 +529,7 @@
 \subsection{The service configuration}
 Each service has its own configuration, specifying basic information like the
 executable file of the service (used by ARM), the port or socket used to reach 
it,
-as well as configuation options specific to the service.
+as well as configuration options specific to the service.
 
 \exercise{%
   Look at the configuration file for the example service {\tt 
config/greeting.conf}
@@ -562,7 +562,7 @@
 public class MyService {
     public static void main(String... argv) {
         new Service(
-            "greeting", // name of the service, for chosing the right 
configuration
+            "greeting", // name of the service, for choosing the right 
configuration
             RelativeTime.MINUTE, // timeout for disconnecting idle clients
             true, // disallow messages of unknown type
             argv) { // command line arguments parsed by Service