diff --git a/src/doc/Data-Model.md b/src/doc/Data-Model.md
index 1819a8c67d84286400e542ef8437e977b90e1b0a..d11a88f67141e366a28ed84895903df7ff062822 100644
--- a/src/doc/Data-Model.md
+++ b/src/doc/Data-Model.md
@@ -1,7 +1,7 @@
# CaosDB Data Model
-The data structure is build from some basic building blocks which are
+The data structure is built from some basic building blocks which are
shown in the following picture:
@@ -29,8 +29,8 @@ class defined by its Record Type. These classes can contain Abstract
Properties which define key-value relationships for properties of the
things along with the expected data type and possibly the default
unit, a default value, or a range of permitted values. As files on the
-back-end file system are a major focus of this database management
-system, there is a special entity File that encapsulates typical file
+backend file system are a major focus of this database management
+system, there is a special File entity that encapsulates typical file
properties like path, size and checksum.
## Entities
@@ -49,8 +49,8 @@ Each Entity has a list of Entity Properties, or in short just
triple of an Abstract Property, a value or Null, and an
Importance. The values can be numerals, strings, dates, any other
valid value that fits into one of several builtin data types, or, most
-notably, references to other Entities. The importance is either
-*obligatory*, *recommended*, *suggested*, or *fix*. A valid child of
+notably, references to other Entities. The Importance is either
+`obligatory`, `recommended`, `suggested`, or `fix`. A valid child of
an Entity implicitly inherits its parent’s Properties according to
their Importance, which means that it is obliged, recommended or only
suggested to have a Property with the same Abstract Property (or any
@@ -58,7 +58,7 @@ subtype thereof). As opposed to Properties with other priorities,
**Fixed Properties** have no effect on the Entity’s children.
During the creation or update of Entities, the importances of the
-parents are being checked by the Server. Missing obligatory Properties
+parents are checked by the server. Missing obligatory Properties
invalidate the transaction and result in an error, by default. Missing
Properties, when they are recommended, result in a warning, but the
transaction is considered valid. Entities with missing suggested
diff --git a/src/doc/specification/AbstractProperty.md b/src/doc/specification/AbstractProperty.md
index 559b4df2fe404258c9b4dc75a3548f0dee133c8e..dee88e665c1609224bdab185ea147b91c49dc8f3 100644
--- a/src/doc/specification/AbstractProperty.md
+++ b/src/doc/specification/AbstractProperty.md
@@ -1,7 +1,7 @@
-.. note ::
+# Note #
- This document has not been updated for a long time. Although it is concerned with the mostly
- stable API, its content may no longer reflect the actual CaosDB behavior.
+> This document has not been updated for a long time. Although it is concerned with the mostly
+> stable API, its content may no longer reflect the actual CaosDB behavior.
# AbstractProperty Specification
diff --git a/src/doc/specification/RecordType.rst b/src/doc/specification/RecordType.rst
index bb885bc4338cc8aaa43ef252022722e1cdab207b..b37c5dabf6b9388628b44aa5ff6e6beaa1823105 100644
--- a/src/doc/specification/RecordType.rst
+++ b/src/doc/specification/RecordType.rst
@@ -4,12 +4,12 @@ RecordType
Overview
--------
-RecordTypes function as templates for :doc:`Records <Record>`. They
+RecordTypes act as templates for :doc:`Records <Record>`. They
provide a description for a type of Record and define which
:doc:`Properties <AbstractProperty>` could, should, or must be
present. Properties come with an `importance` attribute which tells
the user or client program how strongly necessary the Property is. (As
-all other entities,) RecordTypes can be inherited from other
+all other entities,) RecordTypes can inherit from other
RecordTypes (or any Entities). When RecordTypes inherit from other
RecordTypes, the `inheritance` flag tells which properties shall be
inherited from the parents to the children.
@@ -17,8 +17,8 @@ inherited from the parents to the children.
Importance
~~~~~~~~~~
-The importance value of a Property states whether it may, should, or
-has to be present in all children of this Entity. The table below
+The `importance` value of a Property states whether it may, should, or
+must be present in all children of this Entity. The table below
lists the possible importances, together with the default behavior of
the server when the property is not present in a child.
@@ -45,19 +45,17 @@ the server when the property is not present in a child.
- Property is not present in any child
- ---
-The default behavior can be overridden for individual transaction by
-setting the `force-missing-obligatory` flag to `ERROR`, `WARN`, or
-`IGNORE`, in which case a transaction that would lead to an entity
-without (at least) an obligatory property causes an error, is executed
-with a warning, or is executed without a warning, respectively. The
-importance value ``FIX`` is used for properties that are specific to
-the Entity itself and is explained below.
+The default behavior can be overridden for individual transaction by setting the
+`force-missing-obligatory` flag to ``ERROR`` (the default), ``WARN``, or ``IGNORE``. These flags
+cause a transaction that would result in an entity with a missing `obligatory` property to return an
+error, a warning, or to execute without a warning, respectively. The importance value ``FIX`` is
+used for properties that are specific to the Entity itself and is explained below.
.. note::
Note that in contrast to RecordTypes, all properties of a
- :doc:`Record` have importance ``FIX`` since in general, even in the
- rare case of a Record having children, its properties are not
+ :doc:`Record` have the importance ``FIX`` since in general, even in the
+ case of a Record having children, its properties are not
inherited.
Inheritance
@@ -74,23 +72,23 @@ child.
* - Inheritance
- Meaning
* - `None` (default)
- - Nothing is being inherited
+ - Nothing is inherited
* - ``OBLIGATORY``
- Properties of importance ``OBLIGATORY`` and above
* - ``RECOMMENDED``
- Properties of importance ``RECOMMENDED`` and above
* - ``SUGGESTED``
- - Properteis of importance ``SUGGESTED`` and above
+ - Properties of importance ``SUGGESTED`` and above
* - ``ALL``
- Copy everything from the parent.
-Note that inheritance ``All`` is essentially the same as ``SUGGESTED``
+Note that inheritance ``ALL`` is essentially the same as ``SUGGESTED``
right now, but this behavior might change in the future. Also note
that properties of importance ``FIX`` are never inherited this
way. This is precisely what this importance level is meant for:
properties that are specific to the parent entity and are not
inherited by default. You can still add this property to the child
-manually if you wish to, though, but this is not covered by the
+manually if you wish, though, but this is not covered by the
automatic inheritance.
.. note::