Update documentation.

docs/Feature_Reference.tex

@@ -437,6 +437,17 @@ \subsection{\textSourceText{cv53-cv66}, \textSourceText{cv91}\index{cv91} – Ot
 \end{supertabular}
 \end{center}
 
+\subsection{\textSourceText{swsh} – Swash letters (italic only)}
+Produces swash versions of several capitals: \textex{\textit{\addfontfeature{Style=Swash}A Æ D J}}. There are three swash
+versions of Q\,, selected via index (if indexing of \textSourceText{swsh} is supported by your
+application): 1=\textex{\textit{\cvd[2]{33}{Qui}}}, 
+2=\textex{\textit{\cvd[4]{33}{Qui}}}, 3=\textex{\textit{\cvd[3]{33}{Qui}}}.
+Note that swash versions of Q can also be selected with \textSourceText{cv33}. Swash Q is not permitted in
+word-final position; there plain italic Q is substituted. Also, if Q with extended tail might collide with
+a following letter, another appropriate form of Q is substituted. There are also swash versions of lowercase
+e and k: \textex{\textit{\addfontfeature{Style=Swash} e k}}. These are only permitted in word-final position:
+\textex{\textit{\addfontfeature{Style=Swash}elevate, skylark}}.
+
 \subsection{\textSourceText{ss01} – Alternate thorn and eth}
 Produces\index{ss01} Nordic thorn and eth (\textex{\addfontfeature{Language=English}\textAltThornEth{{\th}{\dh}{\TH}}})
 when the language is English, and English thorn and eth
@@ -454,7 +465,7 @@ \subsection{\textSourceText{ss02} – Insular Letter-Forms}
 Produces\index{ss02|textbf} insular letter-forms, e.g. \textex{\addfontfeatures{Language=English,StylisticSet=2}dfgrsw}.
 The result is different,
 depending on whether the language is English or Irish (make sure the language for your document is set
-properly). In English text, capitals are not affected (except W), as these do not not commonly have
+properly). In English text, capitals are not affected (except W), as these do not commonly have
 insular shapes in early manuscripts; instead, enter the Unicode code points or use the Character Variant
 (\textSourceText{cvNN}) features. In English text, ss02 imitates the typography of the Old English
 passages of Hickes’s \textit{Thesaurus}, not the usage of Old English or Anglo-Latin manuscripts. In

docs/JunicodeManual.tex

@@ -13,7 +13,7 @@
 \huge \centering the font for medievalists \\[1cm]
  \Huge\centering {\color{myRed}} \\[1cm]
  \huge\centering {\jItalic specimens and user manual} \\[1ex]
- \Large\centering{\jRegular for version 2.209}\\
+ \Large\centering{\jRegular for version 2.211}\\
 \vfill
 {\color{myRed}}
 \end{titlepage}

docs/Record_Interpreter_notes.tex

@@ -18,7 +18,7 @@ \section{A preliminary note on transcription}
 
 Converting a document from visual image to Unicode-encoded text adds a good bit of value all by itself, but only if done
 with due regard for the semantics of Unicode characters. Every Unicode character has a meaning, and that meaning is a
-help to readers. Using the wrong character is a hinderance to readers, even it if \textit{looks} right.
+help to readers. Using the wrong character is a hinderance to readers, even if it \textit{looks} right.
 
 For example, in transcribing a Middle English text, you may decide that the Unicode ezh (\char"0292,~\unic{U+0292}) looks more like
 the yogh in your source than the Unicode yogh (\kern+1.5pt\char"021D,~\unic{U+021D}) and therefore decide to use it for yogh. But the ezh is

docs/in_tex.tex

@@ -29,6 +29,8 @@ \section{Loading the packages}
     \item[tabular] Numbers will be tabular (or monospaced).
     \item[oldstyle] Numbers will be old-style, harmonizing with lowercase letters.
     \item[lining] Numbers will be lining, harmonizing with uppercase letters.
+    \item[renderer] Choose a renderer: this can be any of those accepted by fontspec (the default
+    is OpenType). This should not generally be changed.
 \end{description}
 
 \noindent With the variable font, terms like “light” and “semibold” (and, for that  matter,