List Conversations before Endpoints to be in sync with the application.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@23671 f5534014-38df-0310-8fa8-9805f1628bb7

diff --git a/docbook/wsug_src/WSUG_chapter_statistics.xml b/docbook/wsug_src/WSUG_chapter_statistics.xml
index 3491c651fac7f1a0c8277466dcb79da98d957ded..69fbbd384c2da0c1b8b6c6e5925d32145439bd0a 100644 (file)
--- a/docbook/wsug_src/WSUG_chapter_statistics.xml
+++ b/docbook/wsug_src/WSUG_chapter_statistics.xml
@@ -27,11 +27,11 @@
        <para><command>Protocol Hierarchy</command> of the captured packets.</para>
        </listitem>
        <listitem>
-       <para><command>Endpoints</command> e.g. traffic to and from an IP 
+       <para><command>Conversations</command> e.g. traffic between specific IP 
        addresses.</para>
        </listitem>
        <listitem>
-       <para><command>Conversations</command> e.g. traffic between specific IP 
+       <para><command>Endpoints</command> e.g. traffic to and from an IP 
        addresses.</para>
        </listitem>
        <listitem>
@@ -185,6 +185,42 @@
        </note>
   </section>
 
+  <section id="ChStatConversations">
+    <title>Conversations</title>
+    <para>
+       Statistics of the captured conversations. 
+    </para>
+       <section><title>What is a Conversation?</title>
+    <para>
+       A network conversation is the traffic between two specific endpoints. For 
+       example, an IP conversation is all the traffic between two IP addresses. 
+       The description of the known endpoint types can be found in 
+       <xref linkend="ChStatEndpointDefinition"/>.
+    </para>
+       </section>
+       <section id="ChStatConversationsWindow"><title>The "Conversations" window</title>
+    <para>
+       Other than the list content, the conversations window works the same way as the 
+       endpoint Window; see <xref linkend="ChStatEndpointsWindow"/> for a 
+       description how it works.
+       <figure><title>The "Conversations" window</title>
+         <graphic entityref="WiresharkStatsConversations" format="PNG"/>
+       </figure>
+    </para>
+       </section>
+       <section id="ChStatConversationListWindow">
+       <title>The protocol specific "Conversation List" windows</title>
+    <para>
+       Before the combined window described above was available, each of its 
+       pages was shown as a separate window. Even though the combined window is 
+       much more convenient to use, these separate windows are still 
+       available. The main reason is that they might process faster for 
+       very large capture files. However, as the functionality is exactly the 
+       same as in the combined window, they won't be discussed in detail here.
+    </para>
+       </section>
+  </section>
+
   <section id="ChStatEndpoints">
     <title>Endpoints</title>
     <para>
@@ -309,42 +345,6 @@
   </section>
   </section>
   
-  <section id="ChStatConversations">
-    <title>Conversations</title>
-    <para>
-       Statistics of the captured conversations. 
-    </para>
-       <section><title>What is a Conversation?</title>
-    <para>
-       A network conversation is the traffic between two specific endpoints. For 
-       example, an IP conversation is all the traffic between two IP addresses. 
-       The description of the known endpoint types can be found in 
-       <xref linkend="ChStatEndpointDefinition"/>.
-    </para>
-       </section>
-       <section id="ChStatConversationsWindow"><title>The "Conversations" window</title>
-    <para>
-       Other than the list content, the conversations window works the same way as the 
-       endpoint Window; see <xref linkend="ChStatEndpointsWindow"/> for a 
-       description how it works.
-       <figure><title>The "Conversations" window</title>
-         <graphic entityref="WiresharkStatsConversations" format="PNG"/>
-       </figure>
-    </para>
-       </section>
-       <section id="ChStatConversationListWindow">
-       <title>The protocol specific "Conversation List" windows</title>
-    <para>
-       Before the combined window described above was available, each of its 
-       pages was shown as a separate window. Even though the combined window is 
-       much more convenient to use, these separate windows are still 
-       available. The main reason is that they might process faster for 
-       very large capture files. However, as the functionality is exactly the 
-       same as in the combined window, they won't be discussed in detail here.
-    </para>
-       </section>
-  </section>
-
   <section id="ChStatIOGraphs">
     <title>The "IO Graphs" window</title>
     <para>