fix: remaining HTML entities and wrong quotation marks

Author: vwkd

content/data-storage/er-model/index.md

@@ -33,7 +33,7 @@ tags:
 - diagram of entity types with their attribute types and their relationship types, usually drawn as boxes and lines
 - beware: the diagram is drawn for the abstract types, it really "exists" only for the concrete instances ❗️
 
-![Person entity type and "has" relationship to Birthday entity type](er1.svg)
+![Person entity type and 'has' relationship to Birthday entity type](er1.svg)
 
 - can think of entity types as nouns and relationship types as verbs, e.g. person owns car, car is owned by person
 - beware: a relationship label can be read in one direction only, the other direction is obtained by turning the verb into passive voice
@@ -53,15 +53,15 @@ tags:
 - always combines two symbols, the inner component represents the minimum, the outer component represents the maximum, from the point of view of the given entity
 - makes only sense for the following combinations: the symbol `||` means exactly one, `o{` means zero or more, and `|{` means one or more, for cardinality from left entity to right
 
-![Person entity type and "has" relationship to Birthday entity type with cardinality one](er2.svg)
+![Person entity type and 'has' relationship to Birthday entity type with cardinality one](er2.svg)
 
-![Person entity type and "has" relationship to Book entity type with cardinality zero or more](er3.svg)
+![Person entity type and 'has' relationship to Book entity type with cardinality zero or more](er3.svg)
 
 - beware: if wants to be able to version the data, needs to keep the cardinality of a relationship at one and have many duplicated entities with the same content, instead of having a single entity that many otherwise unrelated entities link to, e.g. `Person ||has|| Birthday`, `Person ||has|| Age`, `Person ||has|| Address`, `Person ||has|| Nationality`, instead of `}|has||` or `Person ||has|{ Book` instead of `}|has|{` etc. ⚠️
 
-![Person entity type and "has" relationship to Birthday entity type with cardinality one but reverse zero or more](er2bad.svg)
+![Person entity type and 'has' relationship to Birthday entity type with cardinality one but reverse zero or more](er2bad.svg)
 
-![Person entity type and "has" relationship to Book entity type with cardinality zero or more but reverse also zero or more](er3bad.svg)
+![Person entity type and 'has' relationship to Book entity type with cardinality zero or more but reverse also zero or more](er3bad.svg)
 
 
 

content/data-storage/graph-databases/index.md

@@ -105,7 +105,7 @@ Use attributes otherwise
 Use nodes if wants to connect two more than two entities
 Use relationship otherwise
 
-Use fine grained relationships names, checking attributes on target mode is more expensive, e.g. Person located_home Address instead of Person located Address {type: home}
+Use fine grained relationships names, checking attributes on target mode is more expensive, e.g. Person located_home Address instead of Person located Address `{type: home}`
 Eliminates graph travels, faster performance
 Put complex attributes with multiple attributes in own nodes, e.g. Address
 

content/data-storage/traditional-databases/index.md

@@ -21,13 +21,13 @@ tags:
 - each column (field) in the table represents an attribute type of that entity type, e.g. unique identifier (primary key) in first column
 - relationships between entities are implicitly encoded using attributes, "foreign key" attribute contains primary key of entity that is related to
 
-![Person entity type with birthday attribute and "use" relationship to Birthday entity type with cardinality one](er4.svg)
+![Person entity type with birthday attribute and 'use' relationship to Birthday entity type with cardinality one](er4.svg)
 
 - the relationship can be labeled "uses", is usually not labeled since it is always the same
 - the cardinality of a relationship must be at least one, otherwise the attribute would be empty
 - if the cardinality is higher than one, the attribute must be an array, since it can contain multiple instances ❗️
 
-![Person entity type with phone attribute array and "use" relationship to Phone entity type with cardinality one or more](er5.svg)
+![Person entity type with phone attribute array and 'use' relationship to Phone entity type with cardinality one or more](er5.svg)
 
 - schema-fixed: data must have fixed structure, column of table forces nodes to have the same attribute types, can not add / remove attributes only for some entities without changing other ones
 

content/the-web/http-cache/index.md

@@ -164,7 +164,7 @@ tags:
 - beware: if does cache "external" resource risks breakages due to incompatibilities from mixing of new and old versions of interdependent resources ⚠️
 - cache personalised responses at most in private cache, e.g. profile page, etc.
 - beware: never cache personalised responses in public cache, otherwise second client can see response for first ❗️
-- usually caches only responses with certain status codes, e.g. < 500 because server error is not normal
+- usually caches only responses with certain status codes, e.g. &lt; 500 because server error is not normal
 - beware: caching and not caching a resource doesn't correspond to a static / dynamic Web server, e.g. can statically serve a changing resource, can dynamically serve a non-changing resource ❗️