diff --git a/readme.md b/readme.md
index d46ff21..4a06bdf 100644
--- a/readme.md
+++ b/readme.md
@@ -417,7 +417,9 @@ Therfore we can query $metadata and check the entity type:
 ```
 ### Association
 
-No navigation properties yet. Well, as the custom API is independent of the OData web service, it is required to define also an API for Contact:
+No navigation properties yet. 
+
+Well, as the custom API is independent of the OData web service, it is required to define also an API for Contact:
 
 ``` al
 page 50103 "Contact API"
@@ -735,7 +737,7 @@ But the `$metadata` changed. The more or less meaningless navigation property `c
 </EntityType>
 ```
 
-The cardinality still does not fit, there can only be one company contact linked to a contact. 
+The cardinality does not fit anymore; as there can only be one company contact linked to a contact. But in fact, that is comparable to me with the OData web services.
 
 But now I can query for `contacts('KT200038')?$expand=companyContacts($expand=contact)`:
 ```json
@@ -770,4 +772,4 @@ I appreciate the clean separation of APIs from other APIs or even the UI. They c
 
 Also, a simple association no longer results in a collection.  I also like that both required AL code and resulting $metadata are now denser.
 
-You have to think differently about your queries. It is best to design any relation explicitly as own page and refer it as part, at least from a perspective of querying data. 
\ No newline at end of file
+You have to think differently about your queries. It is best to design any relation explicitly as own page and refer it as part, at least from a perspective of querying data.