PHPTR Edit 2. More to come.

(This used to be commit bc4d2f60cefa126415b06440280761d19e8c0d21)

1 files changed, 22 insertions, 25 deletions

diff --git a/docs/Samba3-HOWTO/TOSHARG-Portability.xml b/docs/Samba3-HOWTO/TOSHARG-Portability.xml
index a5455a6c67..28f32702e0 100644
--- a/docs/Samba3-HOWTO/TOSHARG-Portability.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-Portability.xml
@@ -9,7 +9,7 @@
 
 <title>Portability</title>
 
-<para>Samba works on a wide range of platforms but the interface all the 
+<para>Samba works on a wide range of platforms, but the interface all the 
 platforms provide is not always compatible. This chapter contains 
 platform-specific information about compiling and using Samba.</para>
 
@@ -17,14 +17,14 @@ platform-specific information about compiling and using Samba.</para>
 <title>HPUX</title>
 
 <para>
-HP's implementation of supplementary groups is non-standard (for
+Hewlett-Packard's implementation of supplementary groups is nonstandard (for
 historical reasons). There are two group files, <filename>/etc/group</filename> and
 <filename>/etc/logingroup</filename>; the system maps UIDs to numbers using the former, but
-initgroups() reads the latter. Most system Admins who know the ropes
+initgroups() reads the latter. Most system admins who know the ropes
 symlink <filename>/etc/group</filename> to <filename>/etc/logingroup</filename>
-(hard link does not work for reasons too obtuse to go into here). initgroups() will complain if one of the
-groups you're in in <filename>/etc/logingroup</filename> has what it considers to be an invalid
-ID, which means outside the range <constant>[0..UID_MAX]</constant>, where <constant>UID_MAX</constant> is (I think)
+(hard-link does not work for reasons too obtuse to go into here). initgroups() will complain if one of the
+groups you're in, in <filename>/etc/logingroup</filename>, has what it considers to be an invalid
+ID, which means outside the range <constant>[0..UID_MAX]</constant>, where <constant>UID_MAX</constant> is
 60000 currently on HP-UX. This precludes -2 and 65534, the usual <constant>nobody</constant>
 GIDs.
 </para>
@@ -56,14 +56,14 @@ encounter corrupt data transfers using Samba.
 
 <para>
 The patch you need is UOD385 Connection Drivers SLS. It is available from
-SCO (<ulink noescape="1" url="ftp://ftp.sco.com/">ftp.sco.com</ulink>, directory SLS,
+SCO <ulink noescape="1" url="ftp://ftp.sco.com/">ftp.sco.com</ulink>, directory SLS,
 files uod385a.Z and uod385a.ltr.Z).
 </para>
 
 <para>
 The information provided here refers to an old version of SCO UNIX. If you require
 binaries for more recent SCO UNIX products, please contact SCO to obtain packages that are
-ready to install. You should also verify with SCO that your platform is up-to-date for the
+ready to install. You should also verify with SCO that your platform is up to date for the
 binary packages you will install. This is important if you wish to avoid data corruption
 problems with your installation. To build Samba for SCO UNIX products  may
 require significant patching of Samba source code. It is much easier to obtain binary
@@ -128,7 +128,7 @@ _seteuid:
 </programlisting></para>
 
 <para>
-After creating the above files, you then assemble them using
+After creating the files, you then assemble them using
 </para>
 
 <screen>
@@ -137,13 +137,13 @@ After creating the above files, you then assemble them using
 </screen>
 
 <para>
-that should produce the files <filename>seteuid.o</filename> and 
-<filename>setegid.o</filename>
+which should produce the files <filename>seteuid.o</filename> and 
+<filename>setegid.o</filename>.
 </para>
 
 <para>
-Then you need to add these to the LIBSM line in the DNIX section of
-the Samba Makefile. Your LIBSM line will then look something like this:
+Next you need to add these to the LIBSM line in the DNIX section of
+the Samba Makefile. Your LIBSM line will look something like this:
 </para>
 
 <para><programlisting>
@@ -181,21 +181,18 @@ is the master browse list holder and who is the master browser.
 </para>
 
 <para>
-Corrective Action: Delete the entry after the word "loopback"
+Corrective action: Delete the entry after the word "loopback"
 in the line starting 127.0.0.1.
 </para>
 </sect1>
 
 <sect1>
-<title>AIX</title>
-<sect2>
-<title>Sequential Read Ahead</title>
+<title>AIX: Sequential Read Ahead</title>
 <!-- From an email by William Jojo <jojowil@hvcc.edu> -->
 <para>
-Disabling Sequential Read Ahead using <userinput>vmtune -r 0</userinput> improves 
+Disabling sequential read ahead using <userinput>vmtune -r 0</userinput> improves 
 Samba performance significantly.
 </para>
-</sect2>
 </sect1>
 
 <sect1>
@@ -205,13 +202,13 @@ Samba performance significantly.
 <title>Locking Improvements</title>
 
 <para>Some people have been experiencing problems with F_SETLKW64/fcntl 
-when running Samba on Solaris. The built-in file locking mechanism was
+when running Samba on Solaris. The built-in file-locking mechanism was
 not scalable. Performance would degrade to the point where processes would
 get into loops of trying to lock a file. It would try a lock, then fail,
 then try again. The lock attempt was failing before the grant was
-occurring. So the visible manifestation of this would be a handful of
-processes stealing all of the CPU, and when they were truss-ed they would
-be stuck if F_SETLKW64 loops.
+occurring. The visible manifestation of this was a handful of
+processes stealing all of the CPU, and when they were trussed, they would
+be stuck in F_SETLKW64 loops.
 </para>
 
 <para>
@@ -220,11 +217,11 @@ has not been released yet.
 </para>
 
 <para>
-The patch revision for 2.6 is 105181-34, for 8 is 108528-19 and for 9 is 112233-04.
+The patch revision for 2.6 is 105181-34, for 8 is 108528-19, and for 9 is 112233-04.
 </para>
 
 <para>
-After the install of these patches, it is recommended to reconfigure
+After the installation of these patches, it is recommended to reconfigure
 and rebuild Samba.
 </para>