dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 1000
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Tue 2014-04-01 13:13:06 +0200
message:
  Docs, better title
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-03-31 08:22:31 +0000
+++ src/docbkx/en/dhis2_user_man_web_api.xml	2014-04-01 11:13:06 +0000
@@ -675,7 +675,7 @@
     <title>Events</title>
     <para>This section is about sending and reading events.</para>
   <section>
-    <title>Sending event data values</title>
+    <title>Sending events</title>
     <para>DHIS 2 supports three kinds of events: single events with no registration (also referred to as anonymous events), single event
         with registration and multiple events with registration. Registration implies that the data is linked to a tracked entity instance
         which is identified using some sort of identifier.</para>
@@ -878,7 +878,7 @@
     </para>
   </section>
   <section>
-    <title>Reading event data values</title>
+    <title>Querying and reading events</title>
     <para>This section explains how to read out the events that have been stored in the DHIS2 instance. For more advanced uses of the event
       data, please see the section on event analytics. The output format from the <emphasis role="italic">/api/events</emphasis> endpoint
       will match the format that is used to send events to it (which the analytics event api does not support). Both XML and JSON are