Add notes on analogies

Author: flyingsilverfin

home/modules/ROOT/pages/get-started/schema.adoc

@@ -9,7 +9,9 @@
 
 In the previous section we've created our TypeDB server instance and connected TypeDB Studio (or Console).
 
-Now we'll use the server to create a database and initialize the schema. A TypeDB schema defines what data is permitted to be written to your database. Schemas are one of the key aspects of TypeDB: they allow the database to validate inserted data, check queries for validity, and perform query optimization. TypeDB's schemas are intuitive and built with higher-level building blocks compared to relational, document, or graph databases.
+Now we'll use the server to create a database and initialize the schema. A TypeDB schema defines what data is permitted to be written to your database. Think of schemas as your _blueprints_ for your data (or custom _dna_ from biology, or _classes_ in OOP).
+
+Schemas are one of the key aspects of TypeDB: they allow the database to validate inserted data, check queries for validity, and perform query optimization. TypeDB's schemas are intuitive and built with higher-level building blocks compared to relational, document, or graph databases.
 
 == TypeDB's data model at a glance
 

home/modules/ROOT/pages/what-is-typedb.adoc

@@ -61,7 +61,7 @@ With TypeDB, you get a database that is designed to tackle those problems in an
 
 TypeDB types can do far more than you'd initially expect. Not only can you define simple entities, relations, and attributes, you can also define subtype hierarchies, additional interface-like role types, and reusable functions.
 
-These capabilities in turn compose with each other and interact polymorphically—for example, a user-defined function that can accept a `person` entity as an argument can also automatically take its subtype `child` entity as an argument!
+These capabilities in turn compose with each other and interact polymorphically — for example, a user-defined function that can accept a `person` entity as an argument can also automatically take its subtype `child` entity as an argument!
 
 [,typeql]
 ----