[GNUnet-SVN] r5371 - GNUnet/doc/manual

[gnunet]

Author: durner
Date: 2007-07-29 04:31:33 -0600 (Sun, 29 Jul 2007)
New Revision: 5371

Modified:
   GNUnet/doc/manual/manual.texi
Log:
minor improvements

Modified: GNUnet/doc/manual/manual.texi
===================================================================
--- GNUnet/doc/manual/manual.texi       2007-07-29 08:53:23 UTC (rev 5370)
+++ GNUnet/doc/manual/manual.texi       2007-07-29 10:31:33 UTC (rev 5371)
@@ -216,7 +216,7 @@
 @node Binary packages
 @section Binary packages
 
-A binary package is ready-to-run software which just has to be installed and
+A @dfn{binary} package is ready-to-run software which just has to be installed 
and
 configured. This is the usual way of obtaining GNUnet. Some operating system
 vendors include GNUnet in their distribution or make it
 available for download. The installer for Microsoft Windows is an
@@ -238,8 +238,8 @@
 @node Source
 @section Source
 
-"Source code" can be best described as "recipe" and "ingredients" of a
-particular piece of software. Just as a cake is baked, source code source code
address@hidden code} can be best described as "recipe" and "ingredients" of a
+particular piece of software. Just as a cake is baked, source code
 must be translated to machine code ("compiled") in order to get
 actual software which can be executed. Compiling GNUnet from source is
 usually not difficult, but it is certainly not as easy as installing a
@@ -252,7 +252,7 @@
 @node Virtual appliance
 @section Virtual appliance
 
-Virtual appliances are complete software environments including an operating
address@hidden appliances} are complete software environments including an 
operating
 system which run through virtualization software like 
address@hidden@uref{http://fabrice.bellard.free.fr/qemu/}}
 or address@hidden@uref{http://vmware.com/}}. Virtual appliances require no
 installation on the host system and little additional configuration effort.