[exim-cvs] Docs: typoes

Gitweb: https://git.exim.org/exim.git/commitdiff/b535735cdd9680f4d47a9430ca6e3d4ce625f7f2

Commit:     b535735cdd9680f4d47a9430ca6e3d4ce625f7f2
Parent:     c1fc7e8af58af79f4a3a161cafab6e18699585ec
Author:     Jeremy Harris <jgh146exb@???>
AuthorDate: Sun Jun 7 15:26:17 2020 +0100
Committer:  Jeremy Harris <jgh146exb@???>
CommitDate: Sun Jun 7 15:26:17 2020 +0100

    Docs: typoes
---
 doc/doc-docbook/spec.xfpt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index e5a3c4b..0d666b9 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -9472,7 +9472,7 @@ Common ways of obtaining untainted equivalents of variables with
tainted values
.cindex "tainted data" "de-tainting"
come down to using the tainted value as a lookup key in a trusted database.
-This database could be the filestem structure,
+This database could be the filesystem structure,
or the password file,
or accessed via a DBMS.
Specific methods are indexed under &"de-tainting"&.
@@ -10201,7 +10201,7 @@ in a list using the given separator.
.wen

-.vitem "&*${lookup{*&<&'key'&>&*}&~*&<&'search&~type'&>&*&~&&&
+.vitem "&*${lookup&~{*&<&'key'&>&*}&~*&<&'search&~type'&>&*&~&&&
         {*&<&'file'&>&*}&~{*&<&'string1'&>&*}&~{*&<&'string2'&>&*}}*&" &&&
        "&*${lookup&~*&<&'search&~type'&>&*&~{*&<&'query'&>&*}&~&&&
         {*&<&'string1'&>&*}&~{*&<&'string2'&>&*}}*&"