1 files changed, 10 insertions(+), 7 deletions(-)

M README.org

@@ 425,10 425,12 @@ two distinct presets for presentations: one is for coding related
 demonstrations and the other for prose.  Both must have some common
 styles, but must define distinct font families each of which is
 suitable for the given task.  In this case, we do not want to fall
-back to the generic =t= preset and we also do not wish to duplicate
-properties manually, potentially making mistakes in the process.
-Fontaine thus provides a method of inheriting a named preset's
-properties.  Here is the idea:
+back to the generic =t= preset (per the default behaviour) and we also
+do not wish to duplicate properties manually, potentially making
+mistakes in the process.  Fontaine thus provides a method of
+inheriting a named preset's properties by using the =:inherit=
+property with a value that references the name of another preset
+(technically, the ~car~ of that list).  Here is the idea:
 
 #+begin_src emacs-lisp
 (setq fontaine-presets


@@ 454,10 456,11 @@ properties.  Here is the idea:
 In this scenario, the =regular= preset gets all its properties from
 the =t= preset.  We omit them here in the interest of brevity (see the
 default value of ~fontaine-presets~ and its documentation for the
-details).  In turn, the =code-demo= specifies more properites and
-falls back to =t= for any property not explicitly referenced.
+details).  In turn, the =code-demo= specifies more properties and
+falls back to =t= for any property not explicitly referenced therein.
 Finally, the =prose-demo= copies everything in =code-demo=, overrides
-any property therein, and falls back to =t= for every other property.
+every property it specifies, and falls back to =t= for every other
+property.
 
 In the interest of simplicity, Fontaine does not support recursive
 inheritance.  If there is a compelling need for it, we can add it in