doc updates

doc/concepts/data-and-document.md

@@ -91,13 +91,9 @@ for more details.
 Notus documents are represented as a tree of nodes. There are 3 main
 types of nodes:
 
-* `LeafNode` - a leaf node which represents a segment of styled text
-  within a document. There are two kinds of leaf nodes - text and
-  embeds.
-* `LineNode` - represents an individual line of text within a document.
-  Line nodes are containers for leaf nodes.
-* `Block` - represents a group of adjacent lines which share the same
-  style. Examples of blocks include lists, quotes or code blocks.
+* `LeafNode` - a leaf node which represents a segment of styled text within a document. There are two kinds of leaf nodes - text and embeds.
+* `LineNode` - represents an individual line of text within a document. Line nodes are containers for leaf nodes.
+* `Block` - represents a group of adjacent lines which share the same style. Examples of blocks include lists, quotes or code blocks.
 
 Given above description, here is ASCII-style visualization of a Notus
 document tree:

doc/concepts/heuristics.md

@@ -72,15 +72,8 @@ conforms to the document model and data format semantics.
 
 This method exists mostly to enable following use cases:
 
-* **Collaborative editing**, when a change came from a different site and
-  has already been normalized by heuristic rules on that site. Care must
-  be taken to ensure that this change is based on the same revision
-  of the document, and if not, transformed against any local changes
-  before composing.
-* **Change history and revisioning**, when a change came from a revision
-  history stored on a server or a database. Similarly, care must be
-  taken to transform the change against any local (uncommitted) changes
-  before composing.
+* **Collaborative editing**, when a change came from a different site and has already been normalized by heuristic rules on that site. Care must be taken to ensure that this change is based on the same revision of the document, and if not, transformed against any local changes before composing.
+* **Change history and revisioning**, when a change came from a revision history stored on a server or a database. Similarly, care must be taken to transform the change against any local (uncommitted) changes before composing.
 
 When composing a change which came from a different site or server make
 sure to use `ChangeSource.remote` when calling `compose()`. This allows