diff --git a/topics/operating-mode/domain-example.adoc b/topics/operating-mode/domain-example.adoc
index 50148ef67a..a288df10aa 100755
--- a/topics/operating-mode/domain-example.adoc
+++ b/topics/operating-mode/domain-example.adoc
@@ -3,4 +3,33 @@
 As noted in the <<domain.adoc#,domain mode>> chapter, {{book.project.name}} comes with a mostly pre-configured clustered domain
 setup.  This chapter walks you through this out of the box configuration highlighting each aspect of each configuration
 file you need to touch and manage.  At the end, the chapter discusses what changes you'll need to make to this out of the
-box configuration to have it work in a real cluster.
\ No newline at end of file
+box configuration to have it work in a real cluster.
+
+The default +profile+ XML block is where you are going to make the bulk of your configuration decisions.  You can edit this file
+directly prior to booting the domain controller, but you should use the {{book.appserver.name}} web console or command line interface
+to modify it at runtime.
+
+.profile
+[source,xml]
+----
+    <profiles>
+        <profile name="default">
+           ...
+        </profile>
+----
+
+The definition of the server group for {{book.project.name}} resides in the +server-groups+ XML block.  It specifies the domain profile
+that is used (+default+) and also so default boot arguments for the Java VM when the host controller boots an instance.
+
+.server group
+[source,xml]
+----
+    <server-groups>
+        <server-group name="main-server-group" profile="default">
+            <jvm name="default">
+                <heap size="64m" max-size="512m"/>
+            </jvm>
+            <socket-binding-group ref="standard-sockets"/>
+        </server-group>
+    </server-groups>
+----
diff --git a/topics/operating-mode/domain.adoc b/topics/operating-mode/domain.adoc
index 93e0a612fa..67ebcf5c95 100755
--- a/topics/operating-mode/domain.adoc
+++ b/topics/operating-mode/domain.adoc
@@ -49,35 +49,6 @@ aspect of this pre-configured _domain.xml_ file.
 .domain.xml
 image:../../{{book.images}}/domain-file.png[]
 
-The default +profile+ XML block is where you are going to make the bulk of your configuration decisions.  You can edit this file
-directly prior to booting the domain controller, but you should use the {{book.appserver.name}} web console or command line interface
-to modify it at runtime.
-
-.profile
-[source,xml]
-----
-    <profiles>
-        <profile name="default">
-           ...
-        </profile>
-----
-
-The definition of the server group for {{book.project.name}} resides in the +server-groups+ XML block.  It specifies the domain profile
-that is used (+default+) and also so default boot arguments for the Java VM when the host controller boots an instance.
-
-.server group
-[source,xml]
-----
-    <server-groups>
-        <server-group name="main-server-group" profile="default">
-            <jvm name="default">
-                <heap size="64m" max-size="512m"/>
-            </jvm>
-            <socket-binding-group ref="standard-sockets"/>
-        </server-group>
-    </server-groups>
-----
-
 NOTE: Any changes you make to this file while the domain controller is running will not take effect and may even be overwritten
       by the server.  Instead use the the command line scripting or the web console of {{book.appserver.name}}.  See
       the link:{{book.appserver.admindoc.link}}[{{book.appserver.admindoc.name}}] for more information.