1 files changed, 7 insertions, 5 deletions

diff --git a/hurd/networking.mdwn b/hurd/networking.mdwn
index 82a7a199..ad0bff95 100644
--- a/hurd/networking.mdwn
+++ b/hurd/networking.mdwn
@@ -10,16 +10,18 @@ is included in the section entitled [[GNU Free Documentation
 License|/fdl]]."]]"""]]
 
 For each supported `PF_*` protocol family (domain), there is a file `/servers/socket/N`
-where `N` is the numberic value for the `PF_*` symbol.  Right now
+where `N` is the numeric value for the `PF_*` symbol.  Right now
 [[`PF_LOCAL`|translator/pflocal]] (a.k.a. `PF_UNIX` or `AF_UNIX`) `N=1`,
 [[`PF_INET`|translator/pfinet]] (a.k.a `AF_INET`) `N=2` and
 [[`PF_INET6`|translator/pfinet/ipv6]] (a.k.a `AF_INET6`) `N=26` are supported.
 
 Depending on the socket domain used the libc function `_hurd_socket_server`
-is called from the calling function socket/socketpair, resolving the socket
-server to use `/hurd/pflocal` or `/hurd/pfinet`. In case of problems to find
-out which server is called rpctrace can be of use: The server is found with the
-`dir_lookup` RPC.
+is called from the calling function socket/socketpair, resolving to
+`/servers/socket/`. The files in that directory are then used by the translators
+`/hurd/pflocal` or `/hurd/pfinet`: HOW?
+
+In case of problems to find out which server is called rpctrace can be of use:
+search for the output `dir_lookup ("servers/socket/N" ...)`
 
 User programs open those files, and use the `socket_create` [[RPC]] to make a
 new socket.  With that socket, they can use the other `socket_*` RPCs and also