Update section 2.3

Author: gramian

src/main/asciidoc/getting-started/multimodel.adoc

@@ -45,7 +45,7 @@ In the table below, you can find a comparison between the graph model, the relat
 
 The data in this model is stored inside documents. A document is a set of key/value pairs (also referred to as fields or properties), where the key allows access to its value. Values can hold primitive data types, embedded documents, or arrays of other values. Documents are not typically forced to have a schema, which can be advantageous, because they remain flexible and easy to modify. Documents are stored in collections, enabling developers to group data as they decide. ArcadeDB uses the concepts of "<<types,Types>>" and "<<buckets,Buckets>>" as its form of "collections" for grouping documents. This provides several benefits, which we will discuss in further sections of the documentation.
 
-ArcadeDB's document model also adds the concept of a "<<relationships,Relationship>>" between documents. With ArcadeDB, you can decide whether to embed documents or link to them directly. When you fetch a document, all the links are automatically resolved by ArcadeDB. This is a major difference to other document databases, like MongoDB or CouchDB, where the developer must handle any and all relationships between the documents herself.
+ArcadeDB's document model also adds the concept of a "<<relationships,Relationship>>" between documents. With ArcadeDB, you can decide whether to embed documents or link to them directly. When you fetch a document, all the links are automatically resolved by ArcadeDB. This is a major difference to other document databases, like MongoDB or CouchDB, where the developer must handle any and all relationships between the documents themself.
 
 The table below illustrates the comparison between the relational model, the document model, and the ArcadeDB document model: