From 5d8311d351a751f1ac1b768c7dcd4330e1069b51 Mon Sep 17 00:00:00 2001
From: Christian Bauer <christian@hibernate.org>
Date: Fri, 4 Feb 2005 20:02:18 +0000
Subject: [PATCH] Completed rewrite

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@5555 1b8cb986-b30d-0410-93ca-fae66ebed9b2
---
 reference/en/modules/transactions.xml | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/reference/en/modules/transactions.xml b/reference/en/modules/transactions.xml
index 4173048221..06e0993a04 100644
--- a/reference/en/modules/transactions.xml
+++ b/reference/en/modules/transactions.xml
@@ -161,16 +161,6 @@
                         if a concurrent modification occured during user think time.
                     </para>
                 </listitem>
-                <listitem>
-                    <para>
-                        <emphasis>Detached Objects</emphasis> - If you decide to use the already
-                        discussed <emphasis>session-per-request</emphasis> pattern, all loaded instances
-                        will be in detached state during user think time. Hibernate allows you to
-                        reattach the objects and persist the modifications, the pattern is called
-                        <emphasis>session-per-request-with-detached-objects</emphasis>. Automatic
-                        versioning is used to isolate concurrent modifications.
-                    </para>
-                </listitem>
                 <listitem>
                     <para>
                         <emphasis>Long Session</emphasis> - The Hibernate <literal>Session</literal> may
@@ -181,6 +171,16 @@
                         concurrent modifications.
                     </para>
                 </listitem>
+                <listitem>
+                    <para>
+                        <emphasis>Detached Objects</emphasis> - If you decide to use the already
+                        discussed <emphasis>session-per-request</emphasis> pattern, all loaded instances
+                        will be in detached state during user think time. Hibernate allows you to
+                        reattach the objects and persist the modifications, the pattern is called
+                        <emphasis>session-per-request-with-detached-objects</emphasis>. Automatic
+                        versioning is used to isolate concurrent modifications.
+                    </para>
+                </listitem>
             </itemizedlist>
 
             <para>