diff options
author | Jeremy Harris <jgh146exb@wizmail.org> | 2020-06-07 15:26:17 +0100 |
---|---|---|
committer | Jeremy Harris <jgh146exb@wizmail.org> | 2020-06-07 15:26:17 +0100 |
commit | b535735cdd9680f4d47a9430ca6e3d4ce625f7f2 (patch) | |
tree | 0f7a95e61b89ecddee7b8ba7bbf280bc2b76c88c /doc | |
parent | c1fc7e8af58af79f4a3a161cafab6e18699585ec (diff) |
Docs: typoes
Diffstat (limited to 'doc')
-rw-r--r-- | doc/doc-docbook/spec.xfpt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index e5a3c4be8..0d666b9c1 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'&>&*}}*&" |