defaultlabel qandaset

Doc/course.xml

@@ -697,7 +697,7 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
       </figure>
       <figure xml:id="fig_SqlDdlEmployee">
-        <title>Relational database implementation of employees </title>
+        <title>Relational database implementation of employees</title>
         <programlisting language="sql">CREATE TABLE EMPLOYEE
 (
@@ -711,17 +711,17 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
 );</programlisting>
       </figure>
-      <qandaset>
+      <qandaset defaultlabel="qanda">
         <title>Implicit model parameters</title>
         <qandadiv>
           <qandaentry>
             <question>
-              <para> <xref linkend="fig_SqlDdlEmployee"/> shows an
+              <para><xref linkend="fig_SqlDdlEmployee"/> shows an
               implementation of <xref linkend="fig_ModelEmployee"/>. But it
               does contain additional integrity constraints of two different
               categories not being stated in <xref
-              linkend="fig_ModelEmployee"/>. </para>
+              linkend="fig_ModelEmployee"/>.</para>
             </question>
             <answer>
@@ -744,7 +744,7 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
       </qandaset>
       <para>We may as well represent our current physical SQL model
-      graphically: </para>
+      graphically:</para>
       <figure xml:id="fig_GraphModelEmployee">
         <title>Graphical representation of employees' model.</title>
@@ -759,8 +759,8 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
       <para>Some SQL data types are quite appropriate. We may however add
       further restrictions to enhance data integrity. The attribute
       <code>SEX</code> for example may be restricted to allow only 'm' and
-      'f'. SQL enables us to do so by adding a <code>CHECK</code> constraint:
-      </para>
+      'f'. SQL enables us to do so by adding a <code>CHECK</code>
+      constraint:</para>
     </chapter>
     <chapter xml:id="xmlIntro">