From bc17e738f08f4c8f35388f108af3b145941185a1 Mon Sep 17 00:00:00 2001 From: "Colin M. Ford" Date: Tue, 28 Nov 2023 22:07:55 -0500 Subject: [PATCH] a few more should > must --- Doc/source/designspaceLib/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/source/designspaceLib/index.rst b/Doc/source/designspaceLib/index.rst index 8fb10734c..c871ae76d 100644 --- a/Doc/source/designspaceLib/index.rst +++ b/Doc/source/designspaceLib/index.rst @@ -137,7 +137,7 @@ be defined in the ``public.fontInfo`` lib. Checking validity of the data using A tool generating the font should copy the font info directly from the ``public.fontInfo`` lib item to the instance or the variable font, superceding -all other settings. All info **not** supplied in ``public.fontInfo`` should be +all other settings. All info **not** supplied in ``public.fontInfo`` must be inherited from the name attributes in the ```` or ```` elements (first) and the UFO font info from the source at the origin (second). Absence of a key from the ``public.fontInfo`` lib does **not** mean a that piece @@ -145,7 +145,7 @@ of font info should be interpreted as being undefined unless it is also left undefined in the other locations. In the case of information in ``public.fontInfo`` conflicting with supplied name strings in the ```` or ```` elements, or the info supplied from the source at the origin, the data in -``public.fontInfo`` should supercede that information because it is understood +``public.fontInfo`` must supercede that information because it is understood that the designer is using ``public.fontInfo`` to gain more granular control over the resulting font.