dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 722
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Sun 2013-04-07 23:25:35 +0200
message:
  Typos
modified:
  src/docbkx/en/dhis2_user_man_sharing.xml
  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_sharing.xml'
--- src/docbkx/en/dhis2_user_man_sharing.xml	2013-03-21 11:06:58 +0000
+++ src/docbkx/en/dhis2_user_man_sharing.xml	2013-04-07 21:25:35 +0000
@@ -100,9 +100,9 @@
       visible or impacting the system for other countries in the organisation.</para>
     <para>A similar approach could work for a scenario with a donor, multiple funding agencies and
       implementing partners in a country, where user groups could be set up for each of those
-      entities. That way each implementing partners could create and share their reports internally
-      within their organisation without affecting or allowing access to others. Reports could also
-      be shared with supervisors and funding agencies at the end of reporting periods.</para>
+      entities. That way each implementing partner could create and share their reports within their
+      organisation without affecting or allowing access to others. Reports could also be shared with
+      supervisors and funding agencies at the end of reporting periods.</para>
     <para>Another use-case is a country department of health with multiple health programs.
       Typically there is a need for having general reports and charts for the department while
       allowing the health programs to develop specific reports and charts for internal use. This can

=== modified file 'src/docbkx/en/dhis2_user_man_web_api.xml'
--- src/docbkx/en/dhis2_user_man_web_api.xml	2013-03-20 14:02:44 +0000
+++ src/docbkx/en/dhis2_user_man_web_api.xml	2013-04-07 21:25:35 +0000
@@ -1282,8 +1282,8 @@
         any data elements, but does include data element groups, the aggregation operator of the
         first data element in the first group will be used. The order of groups and data elements is
         undefined. This query parameter allows you to override the default and specify a specific
-        aggregaton operator. As an exmample, you can set the aggregation operator to "count" with
-        the following URL:</para>
+        aggregaton operator. As an example you can set the aggregation operator to "count" with the
+        following URL:</para>
     <screen>api/analytics?dimension=dx:fbfJHSPpUQD&amp;dimension=pe:2012Q1&amp;dimension=ou:O6uvpzGd5pu&amp;aggregationType=COUNT</screen>
     <para>The <emphasis role="italic">measureCriteria</emphasis> query parameter lets you filter out
       ranges of data records to return. You can instruct the system to return only records where the
@@ -1406,10 +1406,12 @@
       <para>The <emphasis role="italic">height</emphasis> and <emphasis role="italic"
           >width</emphasis> properties indicate how many data columns and rows are contained in the
         response, respectively.</para>
-      <para>The <emphasis role="italic">metaData</emphasis> property contains a mapping between the
-        identifiers used in the data response and the names of the objects they represent. It can be
-        used by clients to substitute the identifiers within the data response with names in order
-        to give a more meaningful view of the data table.</para>
+      <para>The <emphasis role="italic">metaData periods</emphasis> property contains a unique,
+        ordered list of the periods included in the response. The <emphasis role="italic">metaData
+          names</emphasis> property contains a mapping between the identifiers used in the data
+        response and the names of the objects they represent. It can be used by clients to
+        substitute the identifiers within the data response with names in order to give a more
+        meaningful view of the data table.</para>
       <para>The <emphasis role="italic">rows</emphasis> array contains the dimensional data table.
         It contains columns with dimension items (object or period identifiers) and a column with
         aggregated data values. The example response above has a data/indicator column, a period