[docs] small changes

Author: jgrewe

docs/data_model.md

@@ -5,18 +5,18 @@ exchanged. In oder to allow interoperability we need both a common
 (meta) data model, the format in which the metadata are exchanged, and
 a common terminology.
 
-Here we briefly describe the data model of the odML. It is based on
-the idea of key-value pairs like temperature = 26°C.
+Here, we briefly describe the *odML* data model. It is based on
+the idea of key-value pairs like ``temperature = 26°C``.
 
-We tried to keep the model as simple as possible while being flexible,
-allowing interoperability, and being customizable. The model defines
-four entities (Property, Section, Value, RootSection) who's relations
-and elements are shown in the figure below.
+The model is as simple as possible while being flexible, allowing
+interoperability, and being customizable. The model defines four
+entities (Property, Section, Value, RootSection) whose relations and
+elements are shown in the figure below.
 
 ![odml_logo](./images/erModel.png "odml data model")
 
-Property and Section entities are the core of the odml. A Section
-contains Properties and can further have subsection thus building a
-tree-like structure. The model further does not control the content
-which is a risk, on the one hand, but offers the flexibility we
-consider essential.
+Property and Section are the core entities. A Section contains
+Properties and can further have subsection thus building a tree-like
+structure. The model does not constrain the content, which offers the
+flexibility essential for comprehensive annotation of neuroscience
+data.

docs/index.md

@@ -1,13 +1,13 @@
-# odml
+# odML
 
 <img src="./images/odMLLogo.png" alt="odml" style="width: 150px;"/>
 
-odML (open metadata Markup Language) is an [data model](./data_model.md) for storing
-arbitrary metadata. The underlying data model offers a way to store
-metadata in a structured human- and machine-readable way.  Well
-organized metadata management is a key component to guarantee
-reproducibility of experiments and to track provenance of performed
-analyses.
+odML (open metadata Markup Language) is a file format for storing
+arbitrary metadata. The underlying [data model](./data_model.md)
+offers a way to store metadata in a structured human- and
+machine-readable way.  Well organized metadata management is a key
+component to guarantee reproducibility of experiments and to track
+provenance of performed analyses.
 
 
 *python-odml* is the python library for reading and writing odml metadata files. It is a registered research resource with
@@ -22,16 +22,16 @@ the  [RRID:SCR_001376](https://scicrunch.org/browse/resources/SCR_001376)
 
 ## Viewer/Editor
 
-- Editor for odml files [odml-ui](https://github.com/g-node/odml-ui "odml-ui - editor for odml metadata files")
-- Converter for odml files to form or spreadsheets [odmlTables](https://github.com/INM-6/python-odmltables).
+- [odml-ui](https://github.com/g-node/odml-ui "odml-ui - editor for odml metadata files"): Graphical editor
+- [odmlTables](https://github.com/INM-6/python-odmltables) Spreadsheet interface (by INM-6 FZ JÛlich) for odml files.
 
 ## Terminologies
-
-*odml* does not enforce standardization, but welcomes it. We assembled
-definitions of terms that can be used to provide metadata,
-i.e. [odml-terminologies](https://github.com/G-Node/odml-terminologies). An odml-file
-can be based on such a terminology. In that case one does not need to
-provide definitions since they are part of the linked terminology.
+*odML* facilitates and encourages standardization by
+providing
+[terminologies](https://github.com/G-Node/odml-terminologies). An
+odml-file can be based on such a terminology. In that case one does
+not need to provide definitions since they are part of the linked
+terminology.
 
 * * *
 
@@ -68,7 +68,7 @@ This project is open source published under an MIT license-like see [license fil
 
 If you use *odml*, it would be much appreciated if you would cite it in publications with its identifier RRID:SCR_001376 and/or the reference:
 
-*Grewe J., Wachtler T., and Benda J. (2011). A bottom-up approach to data annotation in neurophysiology. Front. Neuroinform. 5:16*
+*Grewe J., Wachtler T., and Benda J. (2011). A bottom-up approach to data annotation in neurophysiology. Front. Neuroinform. 5:16, [doi:10.3389/fninf.2011.00016](https://doi.org/10.3389/fninf.2011.00016)*
 
 
 ### Referenced By