diff --git a/Doc/Sd1/objectsClasses.xml b/Doc/Sd1/objectsClasses.xml
index 9dc27cf2f0691c21aab3e040b16cb98deaefdaf4..37248b85ddbd86c87a44fc2d07e3aa95ffb82dae 100644
--- a/Doc/Sd1/objectsClasses.xml
+++ b/Doc/Sd1/objectsClasses.xml
@@ -82,6 +82,30 @@
       </listitem>
     </itemizedlist>
 
+    <section xml:id="sd1SectMiMavenCmdline">
+      <title>Using MI Maven archetypes from the command line</title>
+
+      <para>You may as well create a project based on an MI Maven archetype
+      from the command line. This requires the configuration of the
+      non-standard MI archetype catalog:</para>
+
+      <programlisting language="none">mvn archetype:generate -DarchetypeGroupId=de.hdm-stuttgart.mi  -DarchetypeArtifactId=mi-maven-archetype-quickstart \
+-DarchetypeVersion=1.1 -DgroupId=de.mi.hdm_stuttgart -DartifactId=hello -DinteractiveMode=false \
+-DarchetypeCatalog=https://maven.mi.hdm-stuttgart.de</programlisting>
+
+      <para>This will create a corresponding Maven based <xref
+      linkend="glo_Java"/> project in a sub folder
+      <filename>hello</filename>.</para>
+
+      <note>
+        <para>Like with <xref linkend="glo_Soft_Eclipse"/> Maven will use the
+        <uri
+        xlink:href="https://maven.mi.hdm-stuttgart.de">https://maven.mi.hdm-stuttgart.de</uri>
+        property value to implicitly access <uri
+        xlink:href="https://maven.mi.hdm-stuttgart.de/archetype-catalog.xml">https://maven.mi.hdm-stuttgart.de/archetype-catalog.xml</uri>.</para>
+      </note>
+    </section>
+
     <section xml:id="sd1SectOwncloud">
       <title>Working at HdM and at home seamlessly</title>
 
@@ -91,21 +115,33 @@
 
       <para>Fortunately <xref linkend="glo_Maven"/> allows for developing
       <xref linkend="glo_Java"/> software in a cross-platform (Windows,
-      Mac-OS, Linux) manner. For the current lecture the following
+      Mac-OS, Linux) manner. With respect to the current lecture the following
       preconditions must be met:</para>
 
       <itemizedlist>
         <listitem>
-          <para>Use a 1.8 SDK. Both parts matter: Do not use version 1.7 (or
-          lower) and do not use just a <xref linkend="glo_JRE"/>. If installed
-          correctly you should be able to execute the <xref
-          linkend="glo_Java"/> compiler and see:</para>
+          <para>Use a 1.8 JDK. Both parts matter:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Do not use version 1.7 (or lower).</para>
+            </listitem>
+
+            <listitem>
+              <para>Do not use just a <xref linkend="glo_JRE"/> rather than a
+              JDK. The latter (among other components) does not contain the
+              compiler.</para>
+            </listitem>
+          </itemizedlist>
+
+          <para> If installed correctly you should be able to execute the
+          <xref linkend="glo_Java"/> compiler:</para>
 
           <programlisting language="none">goik@pdc1:~$ javac -version
-javac 1.8.0_66</programlisting>
+javac 1.8.0_91</programlisting>
 
           <para>The above output shows a <xref linkend="glo_Java"/> 8 compiler
-          having release level 0_66. See <uri
+          having release level 0_91. See <uri
           xlink:href="https://www.java.com/en/download/faq/release_dates.xml">https://www.java.com/en/download/faq/release_dates.xml</uri>
           for details.</para>
         </listitem>
@@ -340,8 +376,7 @@ javac 1.8.0_66</programlisting>
 
     <glosslist>
       <glossentry>
-        <glossterm><command>mvn</command> <option>compile</option>
-        </glossterm>
+        <glossterm><command>mvn</command> <option>compile</option></glossterm>
 
         <glossdef>
           <programlisting language="none">goik@mi-ESPRIMO-P910 gettingstarted&gt; mvn compile