small typos

doc/CHANGES.md

@@ -62,7 +62,7 @@ Change history
 
 ## v2.9a (2024/02/13)
 
-  * Added a `Scale=MatchAveragecase` paramater which averages `Scale=MatchLowercase` and `Scale=MatchUppercase`.
+  * Added a `Scale=MatchAveragecase` parameter which averages `Scale=MatchLowercase` and `Scale=MatchUppercase`.
   * Switched options to LaTeX keyval handler.
   * Added option `verbose` to undo silent/quiet.
   * `euenc`/`tuenc` options are now obsolete (TU is the only encoding). 
@@ -92,7 +92,7 @@ Change history
 
 ## v2.7h (2020/02/03)
 
-  * Eroneous uses of `language=DFLT` changed to `language=dflt`.
+  * Erroneous uses of `language=DFLT` changed to `language=dflt`.
   * Fix spurious error in some cases of `SlantedFont` and `BoldSlantedFont`
     being specified in a `.fontspec` file.
   * Fix regression with `unicode-math` related log files showing the wrong
@@ -102,7 +102,7 @@ Change history
 ## v2.7g (2020/01/26)
 
   * Fix regression that broke changing the default encoding after `fontspec` was loaded
-    (e.g., to use legacy fonts by default but use a `fontspec` font occassionally).
+    (e.g., to use legacy fonts by default but use a `fontspec` font occasionally).
   * Fix bug exhibited in `polyglossia` and perhaps elsewhere when `Script` is set without
     a corresponding `Language`.
   * Use `\familydefault` instead of `\rmdefault` when calculating scaling parameters in
@@ -164,7 +164,7 @@ Change history
 
           \newfontlanguage{Turkish}{TRK,TUR}
 
-      when selected, this first checks for the existance of the TRK language tag, and if
+      when selected, this first checks for the existence of the TRK language tag, and if
       not found then checks for the TUR language tag to use if available.
 
   * Add new `Renderer` options for LuaTeX that enable the HarfBuzz engine. These only
@@ -341,7 +341,7 @@ Change history
   * Allow slanted small caps and better internal methods for "combining" font shapes; this fixes a few bugs.
   * Incorporate "new" font script tags for Indic fonts. E.g., when selecting `Script=Bengali`, fontspec will first query the font for the `bng2` OpenType script, and if not found select `beng`.
   * Restrict some font features from being able to be used within `\addfontfeatures` that were causing some font-loading confusion.
-  * Fixed behaviour in which `\baselineskip` and `\f@size` would (possibly) change values after loading the packge.
+  * Fixed behaviour in which `\baselineskip` and `\f@size` would (possibly) change values after loading the package.
   * Remove copy of `fixltx2e`'s code for footnote symbols; handled by LaTeX2e now.
   * Deprecate `ExternalLocation` for the simpler (and identical) `Path` option.
   * Improvement to some warnings/info messages.
@@ -423,7 +423,7 @@ Change history
 
 ## v2.3c (2013/05/20)
 
-  * Compatbility with luaotfload 2013/05/20 2.2c, support for older version
+  * Compatibility with luaotfload 2013/05/20 2.2c, support for older version
       removed.
 
 ## v2.3b (2013/05/12)

fontspec-code-vars.dtx

@@ -5,7 +5,7 @@
 % \begin{variable}{\l_@@_firsttime_bool}
 % As \cs{keys_set:nn} is run multiple times, some of its
 % information storing only occurs once while we decide if the font family
-% has been defined or not. When the later processing is occuring per-shape
+% has been defined or not. When the later processing is occurring per-shape
 % this no longer needs to happen; this is indicated by the `firsttime'
 % conditional.
 % \end{variable}

fontspec-doc-featset.tex

@@ -297,7 +297,7 @@ \section{Different features for different font sizes}
 \end{table}
 
 \paragraph{Interaction with other features}
-For \feat{SizeFeatures} to work with \feat{ItalicFeatures}, \feat{BoldFeatures}, etc., and \feat{SmallCapsFeatures}, a strict heirarchy is required:
+For \feat{SizeFeatures} to work with \feat{ItalicFeatures}, \feat{BoldFeatures}, etc., and \feat{SmallCapsFeatures}, a strict hierarchy is required:
 \begin{Verbatim}
  UprightFeatures =
   {
@@ -612,7 +612,7 @@ \subsection{Font transformations}
 
 In rare situations users may want to mechanically distort the shapes of the glyphs in the current font such as shown in \exref{fake}. Please don't overuse these features; they are \emph{not} a good alternative to having the real shapes.
 
-\begin{Xexample}{fake}{Articifial font transformations.}
+\begin{Xexample}{fake}{Artificial font transformations.}
   \fontspec{Quattrocento-Regular.ttf} \emph{ABCxyz} \quad
   \fontspec{Quattrocento-Regular.ttf}[FakeSlant=0.2] ABCxyz
 
@@ -685,7 +685,7 @@ \subsection{Optical font sizes} \label{sec:aat-opticalsize}
 \subsection{Weight} \label{sec:variable-weight}
 For fonts with a variable weight axis, the weight can be specified through the
 \feat{Weight} feature. The value should be between 0 and 1000, where typically
-400 corresponds to regular wight and 700 is a bold font.
+400 corresponds to regular weight and 700 is a bold font.
 \begin{Verbatim}
   \fontspec{Source Serif Variable}[Weight=700]
   Bold                                     \\

fontspec-doc-fontsel.tex

@@ -250,7 +250,7 @@ \subsection{By custom file name using a \texttt{.fontspec} file}
       % <other desired options just for the `upright' font>
     }
 \end{Verbatim}
-The \pkg{fontspec} interface here is designed to be flexible to accomodate a variety
+The \pkg{fontspec} interface here is designed to be flexible to accommodate a variety
 of use cases; there is more than one way to achieve the same outcome when font faces are
 collected together into a larger font family.
 
@@ -472,7 +472,7 @@ \subsection{Specifically choosing the \NFSS\ family}
 \begin{Verbatim}
   \fontfamily{myverbatimfont}\selectfont
 \end{Verbatim}
-which is essentially the same as writing |\verbatimfont|, or to go back to the orginal example:
+which is essentially the same as writing |\verbatimfont|, or to go back to the original example:
 \begin{Verbatim}
   \fvset{fontfamily=myverbatimfont}
 \end{Verbatim}

fontspec-doc-opentype.tex

@@ -1406,7 +1406,7 @@ \subsubsection{CJK shape}
 
 There have been many standards for how CJK ideographic
 glyphs are `supposed' to look. Some fonts will contain many alternate
-glyphs available in order to be able to display these gylphs
+glyphs available in order to be able to display these glyphs
 correctly in whichever form is appropriate. Both \AAT\ and OpenType
 fonts support the following \feat{CJKShape} options:
 \opt{Traditional}, \opt{Simplified}, \opt{JIS1978}, \opt{JIS1983},

fontspec-doc-xetex.tex

@@ -214,7 +214,7 @@ \subsection{Style}
 \subsection{CJK shape}
 There have been many standards for how CJK ideographic
 glyphs are `supposed' to look. Some fonts will contain many alternate
-glyphs in order to be able to display these gylphs
+glyphs in order to be able to display these glyphs
 correctly in whichever form is appropriate. Both \AAT\ and OpenType
 fonts support the following \feat{CJKShape} options:
 \opt{Traditional}, \opt{Simplified}, \opt{JIS1978}, \opt{JIS1983},

testsetup/install-texlive.sh

@@ -6,7 +6,7 @@
 # A minimal current TL is installed adding only the packages that are
 # required
 
-# See if there is a cached verson of TL available
+# See if there is a cached version of TL available
 export PATH=/tmp/texlive/bin/x86_64-linux:$PATH
 if ! command -v texlua > /dev/null; then
   # Obtain TeX Live