dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 1090
committer: Lars Helge Overland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Fri 2014-05-30 20:30:37 +0200
message:
  Fixed markup error
modified:
  src/docbkx/en/dhis2_user_man_web_api.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription

=== modified file 'src/docbkx/en/dhis2_user_man_web_api.xml'
--- src/docbkx/en/dhis2_user_man_web_api.xml	2014-05-28 09:19:08 +0000
+++ src/docbkx/en/dhis2_user_man_web_api.xml	2014-05-30 18:30:37 +0000
@@ -1474,9 +1474,9 @@
             <entry>APPROVED_ELSEWHERE</entry>
             <entry>Data is approved, but was not approved here (so cannot be unapproved here.) This covers the following cases:
               <itemizedlist>
-                <listitem>Data is approved at a higher level.</listitem>
-                <listitem>Data is approved for wider scope of category options.</listitem>
-                <listitem>Data is approved for all sub-periods in selected period.</listitem>
+                <listitem><para>Data is approved at a higher level.</para></listitem>
+                <listitem><para>Data is approved for wider scope of category options.</para></listitem>
+                <listitem><para>Data is approved for all sub-periods in selected period.</para></listitem>
               </itemizedlist>
                    In the first two cases, there is a single data approval object that covers the selection. In the third case there is not.
             </entry>
@@ -1497,16 +1497,16 @@
     For example:</para>
     <itemizedlist>
       <listitem>
-        The organisation unit might not be at an approval level. The approval status is determined by
-        whether data is approved at an approval level for an ancestor of the organisation unit.      
-      </listitem>
-      <listitem>
-        You may specify individual attribute category options. The approval status is determined by whether
-        data is approved for an attribute category option combination that includes one or more of these options.
-      </listitem>
-      <listitem>
-        You may specify a time period that is longer than the period for the data set at which the data is entered and approvede.
-        The approval status is determined by whether the data is approved for all the data set periods within the period you specify.
+        <para>The organisation unit might not be at an approval level. The approval status is determined by
+          whether data is approved at an approval level for an ancestor of the organisation unit.</para>
+      </listitem>
+      <listitem>
+        <para>You may specify individual attribute category options. The approval status is determined by whether
+          data is approved for an attribute category option combination that includes one or more of these options.</para>
+      </listitem>
+      <listitem>
+        <para>You may specify a time period that is longer than the period for the data set at which the data is entered and approvede.
+          The approval status is determined by whether the data is approved for all the data set periods within the period you specify.</para>
       </listitem>
     </itemizedlist>
     <para>To approve data you can issue a <emphasis role="italic">POST</emphasis> request to the
@@ -1557,17 +1557,17 @@
           In particular, all of the following must be true:</para>
     <itemizedlist>
       <listitem>
-        The organisation unit's level must be specified by an approval level.      
-      </listitem>
-      <listitem>
-        The category option group (if specified) must be a member of an approval level's category option group set (if specified)
-        for an approval level with the same organisation unit level.
-      </listitem>
-      <listitem>
-        The time period specified must match the period type of the data set.
-      </listitem>
-      <listitem>
-        The data set must specify that data can be approved for this data set.
+        <para>The organisation unit's level must be specified by an approval level.</para>      
+      </listitem>
+      <listitem>
+        <para>The category option group (if specified) must be a member of an approval level's category option group set (if specified)
+        for an approval level with the same organisation unit level.</para>
+      </listitem>
+      <listitem>
+        <para>The time period specified must match the period type of the data set.</para>
+      </listitem>
+      <listitem>
+        <para>The data set must specify that data can be approved for this data set.</para>
       </listitem>
     </itemizedlist>
   </section>