Minor edits

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 1e2b5adb300d01c3ee89a4921c56a2d2fa94d642..61cc6c37b8758b9ccf060c4a147eb906722e2f31 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Operating System Environment
@@ -663,6 +663,26 @@ psql: could not connect to server: No such file or directory
 
 
     
+     
+      AIX
+      AIXIPC configuration
+      
+       
+        At least as of version 5.1, it should not be necessary to do
+        any special configuration for such parameters as
+        SHMMAX, as it appears this is configured to
+        allow all memory to be used as shared memory.  That is the
+        sort of configuration commonly used for other databases such
+        as DB/2.
+
+        It might , however, be necessary to modify the global
+       ulimit information in
+       /etc/security/limits, as the default hard
+       limits for file sizes (fsize) and numbers of
+       files (nofiles) might be too low.
+       
+      
+           
 
      
       BSD/OS
@@ -846,10 +866,10 @@ options        SEMMAP=256
       
        
         The default settings are only suitable for small installations 
-        (the default max segment size is 32 MB). However the remaining
+        (the default maximum segment size is 32 MB). However, the remaining
         defaults are quite generously sized, and usually do not require
-        changes. The max segment size can be changed via the 
-        sysctl interface. For example, to allow 128 MB, 
+        changes. The maximum shared memory segment size can be changed via the 
+        sysctl interface.  For example, to allow 128 MB, 
         and explicitly set the maximum total shared memory size to 2097152 
         pages (the default):
 
@@ -958,26 +978,6 @@ kern.sysv.shmall=1024
       
      
 
-     
-      AIX
-      AIXIPC configuration
-      
-       
-        At least as of version 5.1, it should not be necessary to do
-        any special configuration for such parameters as
-        SHMMAX, as it appears this is configured to
-        allow all memory to be used as shared memory.  That is the
-        sort of configuration commonly used for other databases such
-        as DB/2.
-
-        It might , however, be necessary to modify the global
-       ulimit information in
-       /etc/security/limits, as the default hard
-       limits for file sizes (fsize) and numbers of
-       files (nofiles) might be too low.
-       
-      
-           
 
      
       Solaris
@@ -1068,12 +1068,12 @@ set semsys:seminfo_semmsl=32
 
       
        
-       8300 (assuming 8K BLCKSZ)
+       8300 (assuming 8 kB BLCKSZ)
       
 
       
        
-       8200 (assuming 8K XLOG_BLCKSZ)
+       8200 (assuming 8 kB XLOG_BLCKSZ)