summaryrefslogtreecommitdiff
path: root/doc/hurd.texi
diff options
context:
space:
mode:
authorThomas Bushnell <thomas@gnu.org>1999-09-20 13:37:23 +0000
committerThomas Bushnell <thomas@gnu.org>1999-09-20 13:37:23 +0000
commit3051b1cdbcf8b0529c2cf90e837c4d2f0e10fad4 (patch)
tree3ee3bb552a10e0c360aff3d00c78dbafcbc3270d /doc/hurd.texi
parent4f5f89726e52017bdc9c4eb1835ce0f8b79a9aa7 (diff)
1999-09-20 Thomas Bushnell, BSG <tb@mit.edu>
* hurd.texi: Repair syntax lossage.
Diffstat (limited to 'doc/hurd.texi')
-rw-r--r--doc/hurd.texi15
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/hurd.texi b/doc/hurd.texi
index 69c2395e..da69d511 100644
--- a/doc/hurd.texi
+++ b/doc/hurd.texi
@@ -402,14 +402,13 @@ libraries they use. At that point, you should be able to study the
source code of existing Hurd servers and understand how they use the
Hurd libraries.
-The final level of mastery is learning the about RPC. If you needed to
-ask, then you've got your work cut out for you before you'll be ready
-for Hurd programming.} interfaces which the Hurd libraries implement.
-The last section of each chapter describes any Hurd interfaces used in
-that subsystem. Those sections assume that you are perusing the
-referenced interface definitions as you read. After you have understood
-a given interface, you will be in a good position to improve the Hurd
-libraries, design your own interfaces, and implement new subsystems.
+The final level of mastery is learning the about the RPC interfaces
+which the Hurd libraries implement. The last section of each chapter
+describes any Hurd interfaces used in that subsystem. Those sections
+assume that you are perusing the referenced interface definitions as you
+read. After you have understood a given interface, you will be in a
+good position to improve the Hurd libraries, design your own interfaces,
+and implement new subsystems.
@node Features