Update RAM requirements, reduce wordiness, fix OpenSRF name

diff --git a/1.6/admin/requirements-configuration.xml b/1.6/admin/requirements-configuration.xml
index c1a4fb7..dd56bb4 100644 (file)
--- a/1.6/admin/requirements-configuration.xml
+++ b/1.6/admin/requirements-configuration.xml
@@ -15,7 +15,7 @@
                         <para>The following are the base requirements setting Evergreen up on a test server:</para>\r
                        <itemizedlist>\r
                                <listitem><para>An available desktop, server or virtual image</para></listitem>\r
-                               <listitem><para>512MB RAM</para></listitem>                     \r
+                               <listitem><para>1GB RAM, or more if your server also runs a graphical desktop</para></listitem>                 \r
                                <listitem><para>Linux Operating System</para></listitem>\r
                        </itemizedlist>\r
                        <tip><para>Debian and Ubuntu are the most widely used Linux distributions for installing Evergreen and most development takes place on Debian based systems. If you are new \r
@@ -26,7 +26,7 @@
                        <info>\r
                                <title>Server Hardware Configurations and Clustering</title>\r
                        </info>\r
-                       <para>As apparent in the previous section, the base hardware requirements for running a functional Evergreen server are extremely minimal. It is also possible\r
+                       <para>The hardware requirements for running a functional Evergreen server are minimal. It is also possible\r
                        to scale up your evergreen configuration to be spread your Evergreen resources and services over several or even many servers in a clustered approach for the purpose \r
                        of system redundancy, load balancing and downtime reduction. This allows very large \r
                        consortia to share one Evergreen system with hundreds of libraries with millions of records and millions of users, making the scalability of Evergreen almost infinite.</para>\r
@@ -41,7 +41,7 @@
                                <listitem><para>A large library consortium with several public library systems and/or academic libraries with millions of users and items could run an Evergreen \r
                                system over many servers with clusters for Evergreen services as well as a cluster for the Postgresql Database.</para></listitem>\r
                        </itemizedlist>\r
-                       <para>The key to Evergreen scalability is in the openSRF configuration files <filename>/openils/conf/opensrf.xml</filename> and \r
+                       <para>The key to Evergreen scalability is in the OpenSRF configuration files <filename>/openils/conf/opensrf.xml</filename> and \r
                        <filename>/openils/conf/opensrf_core.xml</filename>. \r
                        By configuring these files, an administrator could cluster evergreen services over multiple hosts, change the host running a specific service \r
                        or change the host of the PostgreSQL database.</para> \r