hurd-l4/doc hurd-on-l4.tex

[Marcus Brinkmann]

CVSROOT:        /cvsroot/hurd
Module name:    hurd-l4
Branch:         
Changes by:     Marcus Brinkmann <address@hidden>       03/08/31 14:42:31

Modified files:
        doc            : hurd-on-l4.tex 

Log message:
        Use European style parskip and parindent.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/doc/hurd-on-l4.tex.diff?tr1=1.14&tr2=1.15&r1=text&r2=text

Patches:
Index: hurd-l4/doc/hurd-on-l4.tex
diff -u hurd-l4/doc/hurd-on-l4.tex:1.14 hurd-l4/doc/hurd-on-l4.tex:1.15
--- hurd-l4/doc/hurd-on-l4.tex:1.14     Sun Aug 31 12:04:05 2003
+++ hurd-l4/doc/hurd-on-l4.tex  Sun Aug 31 14:42:31 2003
@@ -13,6 +13,8 @@
 \newpage
 \tableofcontents
 \newpage
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{1ex plus 0.5ex minus 0.2ex}
 
 \section{Introduction}
 
@@ -347,10 +349,10 @@
 
 The Hurd implements the capability system locally in each task.  A
 common default implementation will be shared by all programs.
-However, a malicious untrusted program could do nothing to disturb the
-communication of other tasks.  A capability will be identified in the
-client task by a the server thread and a local identifier (which can
-be different from client to client).  The server thread will receive
+However, a malicious untrusted program can do nothing to disturb the
+communication of other tasks.  A capability is identified in the
+client task by the server thread and a local identifier (which can be
+different from client to client).  The server thread will receive
 messages for the capabilities.  The first argument in the message is
 the capability identifier.  Although every task can get different IDs
 for the same capability, a well-behaving server will give the same ID