From: https://www.google.com/accounts/o8/id?id=AItOawk_GD3B2YRV5t7ZM5GOh2nD2jfC6Rihqvg <Michael@web>
Date: Sun, 13 Mar 2011 00:31:26 +0000 (-0800)
Subject: (no commit message)
X-Git-Url: http://git.openafs.org/?p=openafs-wiki.git;a=commitdiff_plain;h=b6b01fe28b3a14d9923c94297b019c6cddd5a7d0;hp=d1dfd09b3cb60a24c40438fc385434de0defca92

---

diff --git a/AFSLore/HowToBuildOpenAFSFromSource.mdwn b/AFSLore/HowToBuildOpenAFSFromSource.mdwn
index 539c393..a213350 100644
--- a/AFSLore/HowToBuildOpenAFSFromSource.mdwn
+++ b/AFSLore/HowToBuildOpenAFSFromSource.mdwn
@@ -27,11 +27,11 @@ See the end of this page for instructions on how to build RPM packages.
 
 ## The Longer Story
 
-Building and packaging OpenAFS is not difficult on most modern unix-like
+Building and packaging OpenAFS is not difficult on current unix-like
 systems. A small number of fairly common libraries and tools are required. The
 kernel headers and a compiler capable of building a kernel module is needed to
-build the OpenAFS kernel module needed for the AFS client (and for legacy so
-called inode fileservers.) The gnu autoconf and automake tools are used to
+build the OpenAFS kernel module (used by the cache manager and for
+inode-backend fileservers.) The gnu autoconf and automake tools are used to
 configure the build system, so should be familiar to most people accustomed to
 building binaries on unix-like systems.