diff --git a/src/docbkx/tutorial/relationship.png b/src/docbkx/tutorial/relationship.png
new file mode 100644
index 000000000..f3ae47047
Binary files /dev/null and b/src/docbkx/tutorial/relationship.png differ
diff --git a/src/docbkx/tutorial/relationships.xml b/src/docbkx/tutorial/relationships.xml
index 16bb04a8c..5e5d2d187 100644
--- a/src/docbkx/tutorial/relationships.xml
+++ b/src/docbkx/tutorial/relationships.xml
@@ -5,7 +5,9 @@
     <subtitle>A convincing act</subtitle>
     <para>
         Our application was not yet very much fun, just storing movies and actors. After all,
-        the power is in the relationships between them.
+        the power is in the relationships between them. Fortunately Neo4j treats relationships as first class citizens
+        allowing them to be addressed individually and assigned properties. That allows for representing them as entities
+        if needed.
     </para>
     <section>
         <title>Creating relationships</title>
@@ -16,6 +18,13 @@
             It had to be annotated with @RelationshipEntity and the @StartNode and @EndNode had to be marked.
             So our Role looked like this:
         </para>
+        <para>
+            <mediaobject>
+                <imageobject>
+                    <imagedata fileref="relationship.png" align="center"/>
+                </imageobject>
+            </mediaobject>
+        </para>
         <para>
             <example>
                 <title>Role class</title>