From: Heiko Schlittermann (HS12-RIPE) Date: Wed, 20 Apr 2016 21:36:20 +0000 (+0200) Subject: Doc: fix minor typos, clarifications (extract) X-Git-Tag: exim-4_88_RC1~85 X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=ab7ecc495b4909b8ee9c7ae8747436aa1881b9e7;p=exim.git Doc: fix minor typos, clarifications (extract) --- diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index a39f4fd0a..f165c368a 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -9181,8 +9181,8 @@ The environment is adjusted by the &%keep_environment%& and .cindex "&%extract%&" "substrings by key" The key and <&'string1'&> are first expanded separately. Leading and trailing white space is removed from the key (but not from any of the strings). The key -must not consist entirely of digits. The expanded <&'string1'&> must be of the -form: +must not be empty and must not consist entirely of digits. +The expanded <&'string1'&> must be of the form: .display <&'key1'&> = <&'value1'&> <&'key2'&> = <&'value2'&> ... .endd @@ -12798,7 +12798,7 @@ When a message is received from a remote host over an encrypted SMTP connection, this variable is set to the cipher suite that was negotiated, for example DES-CBC3-SHA. In other circumstances, in particular, for message received over unencrypted connections, the variable is empty. Testing -&$tls_cipher$& for emptiness is one way of distinguishing between encrypted and +&$tls_in_cipher$& for emptiness is one way of distinguishing between encrypted and non-encrypted connections during ACL processing. The deprecated &$tls_cipher$& variable is the same as &$tls_in_cipher$& during message reception,