SGF-16

+ fixed ordering chapters
+ fixed incorrect expression
+ renamed SGI to SGF

docs/src/docbkx/preface.xml

@@ -6,7 +6,7 @@
 	<para>
 	Spring GemFire Integration focuses on integrating Spring Framework's powerful, non-invasive programming model
 	and concepts with Gemstone's GemFire Enterprise Fabric, providing easier configuration, use and high-level abstractions.
-	This document assumes the reader is already has a basic familiarity with the Spring Framework and GemFire concepts 
+	This document assumes the reader already has a basic familiarity with the Spring Framework and GemFire concepts 
 	and APIs.  
 	</para>
 	

docs/src/docbkx/reference/bootstrap.xml

@@ -166,7 +166,7 @@
       <interfacename>Region</interfacename></title>
 
       <para>For scenarios where a <emphasis>CacheServer</emphasis> is used and
-      <emphasis>clients</emphasis> need to be configured, SGI offers a
+      <emphasis>clients</emphasis> need to be configured, SGF offers a
       dedicated configuration class named:
       <classname>ClientRegionFactoryBean</classname>. This allows client
       <emphasis>interests</emphasis> to be registered in both key and regex
@@ -190,7 +190,7 @@
       <title>Advanced configuration through a <interfacename>Region</interfacename>'s <emphasis>attributes</emphasis></title>
       
       <para>Users that need fine control over a region, can configure it in Spring by using the <literal>attributes</literal> property. To ease declarative configuration in Spring,
-      SGI provides two <interfacename>FactoryBean</interfacename>s for creating <interfacename>RegionAttributes</interfacename> and <interfacename>PartitionAttributes</interfacename>,
+      SGF provides two <interfacename>FactoryBean</interfacename>s for creating <interfacename>RegionAttributes</interfacename> and <interfacename>PartitionAttributes</interfacename>,
       namely <classname>RegionAttributesFactory</classname> and <classname>PartitionAttributesFactory</classname>. See below an example of configuring a partitioned region through Spring
       XML:</para>
  

docs/src/docbkx/reference/data.xml

@@ -79,7 +79,7 @@
     transparently across multiple APIs that can be configured either
     programmatically or declaratively (the most popular choice).</para>
 
-    <para>For Gemfire, SGI provides a dedicated, per-cache, transaction
+    <para>For Gemfire, SGF provides a dedicated, per-cache, transaction
     manager that once declared, allows actions on the
     <interfacename>Region</interfacename>s to be grouped and executed
     atomically through Spring:</para>
@@ -151,7 +151,7 @@
 &lt;/cache-loader&gt;</programlisting>
 
     <para>To simplify the task of parsing, converting the parameters and
-    initializing the object, SGI offers a base class
+    initializing the object, SGF offers a base class
     (<classname>WiringDeclarableSupport</classname>) that allows GemFire user
     objects to be wired through a <emphasis>template</emphasis> bean
     definition or, in case that is missing perform autowiring through the

docs/src/docbkx/reference/introduction.xml

@@ -6,16 +6,16 @@
 
    <para><xref linkend="bootstrap"/> describes the configuration support provided for
    bootstrapping, initializing and accessing a GemFire cache or region.</para>
-   
-   <para><xref linkend="serialization"/> describes the enhancements for GemFire 
-   (de)serialization process and management of associated objects.
-   </para>
 
    <para><xref linkend="apis"/> explains the integration between GemFire API and
    the various "data" features available in Spring, such as transaction management
    and exception translation.
    </para>
 
+   <para><xref linkend="serialization"/> describes the enhancements for GemFire 
+   (de)serialization process and management of associated objects.
+   </para>
+
    <para><xref linkend="samples"/> describes the samples provided with the distribution
    for showcasing the various features available in Spring GemFire.
    </para>

docs/src/docbkx/reference/serialization.xml

@@ -13,7 +13,7 @@
   url="http://community.gemstone.com/display/gemfire/Serialization+in+Java">Java</ulink>,
   <ulink
   url="http://community.gemstone.com/display/gemfire/Serialization+in+.NET">.NET</ulink>
-  and C++). This chapter discusses the various ways in which SGI simplifies
+  and C++). This chapter discusses the various ways in which SGF simplifies
   and improves GemFire custom serialization in Java.</para>
 
   <section id="serialization:wiring">
@@ -23,7 +23,7 @@
     Transient data is often dependent on the node or environment where it
     lives at a certain point in time, for example a DataSource. Serializing
     such information is useless (and potentially even dangerous) since it is
-    local to a certain VM/machine. For such cases, SGI offers a special <ulink
+    local to a certain VM/machine. For such cases, SGF offers a special <ulink
     url="http://www.gemstone.com/docs/6.0.1/product/docs/japi/com/gemstone/gemfire/Instantiator.html"><classname>Instantiator</classname></ulink>
     that performs wiring for each new instance created by GemFire during
     deserialization.</para>
@@ -65,7 +65,7 @@
     be created on each machine as data flows in. Out of the box, GemFire uses
     reflection to create new types but for some scenarios, this might prove to
     be expensive. As always, it is good to perform profiling to quantify
-    whether this is the case or not. For such cases, SGI allows the automatic
+    whether this is the case or not. For such cases, SGF allows the automatic
     generation of <classname>Instatiator</classname> classes which instantiate
     a new type (using the default constructor) without the use of
     reflection:</para>