1 files changed, 19 insertions, 4 deletions

diff --git a/manual/nss.texi b/manual/nss.texi
index cd1f4af0ec..45cbf46110 100644
--- a/manual/nss.texi
+++ b/manual/nss.texi
@@ -17,7 +17,7 @@ scheme @dfn{Name Service Switch} (NSS).
 
 Though the interface might be similar to Sun's version there is no
 common code.  We never saw any source code of Sun's implementation and
-so the internal interface are incompatible.  This is also manifest in the
+so the internal interface is incompatible.  This is also manifests in the
 file names we use as we will see later.
 
 
@@ -158,9 +158,9 @@ The second item in the specification gives the user much finer control
 on the lookup process.  Action items are placed between two service
 names and are written within brackets.  The general form is
 
-@smallexample
-[ @r{(}!@r{?} @var{status} = @var{action}@r{)+} ]
-@end smallexample
+@display
+@t{[} ( @t{!}? @var{status} @t{=} @var{action} )+ @t{]}
+@end display
 
 @noindent
 where
@@ -331,6 +331,21 @@ access them.  If a function is not available it is simply treated as if
 the function would return @code{unavail}
 (@pxref{Actions in the NSS configuration}).
 
+The file name @file{libnss_files.so.1} would be on a @w{Solaris 2}
+system @file{nss_files.so.1}.  This is the difference mentioned above.
+Sun's NSS modules are usable as modules which get indirectly loaded
+only.
+
+The NSS modules in the GNU C Library are prepared to be used as normal
+libraries itself.
+@comment Fix me if necessary.
+This is @emph{not} true in the moment, though.  But the different
+organization of the name space in the modules does not make it
+impossible like it is for Solaris.  Now you can see why the modules are
+still libraries.@footnote{There is a second explanation: we were too
+lazy to change the Makefiles to allow the generation of shared objects
+not starting with @file{lib} but do not tell this anybody.}
+
 
 @node NSS Modules Interface,  , NSS Module Names, NSS Module Internals
 @subsection The Interface of the Function in NSS Modules