--- openafs.xml.bak 2003-11-05 22:18:12.000000000 +0800 +++ openafs.xml 2003-11-05 20:27:29.000000000 +0800 @@ -65,7 +65,7 @@ from the cell's servers on behalf of the users. Users won't know on which server a file which they are accessing, is located. They even won't notice if a server will be located to another room, since every volume can be replicated and moved - to another server without user an user noticing. The files are always accessable. + to another server without user and user noticing. The files are always accessable. Well it's like NFS on steroids :)

@@ -125,7 +125,7 @@ Preliminary Work - All commands should be written in on line !! In this document they are + All commands should be written in one line !! In this document they are sometimes wrapped to two lines to make them easier to read. @@ -135,8 +135,8 @@ /usr/vice/cache

- You should adjust the two files CellServDB ans ThisCell before you build the - afs client. (These files are in /usr/portage/net-fs/openafs/files) + You should adjust the two files CellServDB and ThisCell before you build the + afs client. (These files are in /usr/portage/sys-fs/openafs/files) 

  CellServDB:
@@ -149,7 +149,7 @@
        

        CellServDB tells your client which server(s) he needs to contact for a 
        specific cell. ThisCell should be quite obvious. Normally you use a name
-       which is unique for your organisation. Your (official) domain might be a
+       which is unique for your organization. Your (official) domain might be a
        good choice. 
        

      
@@ -158,7 +158,7 @@
      Building the Client
      
 
-emerge net-fs/openafs
+emerge sys-fs/openafs
 

        

        After successfull compilation you're ready to go.
@@ -193,7 +193,7 @@
        and Client
        

 
-# emerge net-fs/openafs
+# emerge sys-fs/openafs