diff --git a/docs/src/docbkx/reference/bootstrap.xml b/docs/src/docbkx/reference/bootstrap.xml
index 8e2a7db4..f90a4e31 100644
--- a/docs/src/docbkx/reference/bootstrap.xml
+++ b/docs/src/docbkx/reference/bootstrap.xml
@@ -453,74 +453,6 @@ redundancy. Each copy provides extra backup at the expense of extra storages.
-
- Configurating Disk Storage
-
- GemFire can use disk as a secondary storage for persisting regions or/and overflow (known as data pagination or eviction to disk). SGF allows such options to be configured
- directly from Spring through disk-store element available on both replicated-region and partitioned-region.
- A disk store defines how that particular region can use the disk and how much space it has available. Multiple directories can be defined in a disk store such as in our example below:
-
-
-
-
-
-
-
-]]>
-
- In general, for maximum efficiency, it is recommended that each region that accesses the disk uses a disk store configuration.
-
-
- For the full set of options and their meaning please refer to the and GemFire documentation.
-
-
-
-
-
- Data Persistence
-
- Both partitioned and replicated regions can be made persistent. That is:
-
- What is region persistence?
- GemFire ensures that all the data you put into a region that is configured for persistence will be written to disk in a way that it can be
- recovered the next time you create the region. This allows data to be recovered after a machine or process failure or after an orderly shutdown and
- restart of GemFire.
-
-
- With SGF, to enable persistence, simply set to true the persistent attribute on replicated-region or
- partitioned-region:
-
- ]]>
-
- Persistence for partitioned regions is supported from GemFire 6.5 onwards - configuring this option on a previous release will trigger
- an initialization exception.
-
- When persisting regions, it is recommended to configure the storage through the disk-store element for maximum efficiency.
-
-
-
- Data Eviction and Overflowing
-
- Based on various constraints, each region can have an eviction policy in place for evicting data from memory. Currently, in GemFire
- eviction applies on the least recently used entry (also known as LRU).
- Evicted entries are either destroyed or paged to disk (also known as overflow).
-
- SGF supports all eviction policies (entry count, memory and heap usage) for both partitioned-region and replicated-region
- through the nested eviction element. For example, to configure a partition to overflow to disk if its size is more then 512 MB, one could use
- the following configuration:
-
-
-
-]]>
-
- Replicas cannot use a local destroy eviction since that would invalidate them. See the GemFire docs for more information.
-
- When configuring regions for oveflow, it is recommended to configure the storage through the disk-store element for maximum efficiency.
-
- For a detailed description of eviction policies, see the GemFire documentation (such as this
- page).
-
-
Client Region
@@ -564,6 +496,76 @@ redundancy. Each copy provides extra backup at the expense of extra storages.]]>
+
+
+ Configurating Disk Storage
+
+ GemFire can use disk as a secondary storage for persisting regions or/and overflow (known as data pagination or eviction to disk). SGF allows such options to be configured
+ directly from Spring through disk-store element available on both replicated-region and partitioned-region as well as
+ client-region.
+ A disk store defines how that particular region can use the disk and how much space it has available. Multiple directories can be defined in a disk store such as in our example below:
+
+
+
+
+
+
+
+]]>
+
+ In general, for maximum efficiency, it is recommended that each region that accesses the disk uses a disk store configuration.
+
+
+ For the full set of options and their meaning please refer to the and GemFire documentation.
+
+
+
+
+
+ Data Persistence
+
+ Both partitioned and replicated regions can be made persistent. That is:
+
+ What is region persistence?
+ GemFire ensures that all the data you put into a region that is configured for persistence will be written to disk in a way that it can be
+ recovered the next time you create the region. This allows data to be recovered after a machine or process failure or after an orderly shutdown and
+ restart of GemFire.
+
+
+ With SGF, to enable persistence, simply set to true the persistent attribute on replicated-region,
+ partitioned-region or client-region:
+
+ ]]>
+
+ Persistence for partitioned regions is supported from GemFire 6.5 onwards - configuring this option on a previous release will trigger
+ an initialization exception.
+
+ When persisting regions, it is recommended to configure the storage through the disk-store element for maximum efficiency.
+
+
+
+ Data Eviction and Overflowing
+
+ Based on various constraints, each region can have an eviction policy in place for evicting data from memory. Currently, in GemFire
+ eviction applies on the least recently used entry (also known as LRU).
+ Evicted entries are either destroyed or paged to disk (also known as overflow).
+
+ SGF supports all eviction policies (entry count, memory and heap usage) for both partitioned-region and replicated-region
+ as well as client-region, through the nested eviction element.
+ For example, to configure a partition to overflow to disk if its size is more then 512 MB, one could use
+ the following configuration:
+
+
+
+]]>
+
+ Replicas cannot use a local destroy eviction since that would invalidate them. See the GemFire docs for more information.
+
+ When configuring regions for oveflow, it is recommended to configure the storage through the disk-store element for maximum efficiency.
+
+ For a detailed description of eviction policies, see the GemFire documentation (such as this
+ page).
+
Advanced Region Configuration