From: Phil Pennock <pdp@exim.org>
Date: Tue, 22 May 2012 13:06:24 +0000 (-0400)
Subject: OCSP description: minor nits
X-Git-Tag: exim-4_80_RC5~9
X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=98a3b5270f8d5c172d26a407dbf7405755b4e976;p=exim.git

OCSP description: minor nits
---

diff --git a/doc/doc-txt/experimental-spec.txt b/doc/doc-txt/experimental-spec.txt
index 74b14fe06..5dd6832b1 100644
--- a/doc/doc-txt/experimental-spec.txt
+++ b/doc/doc-txt/experimental-spec.txt
@@ -55,12 +55,13 @@ contents are always valid.  Exim will expand the "tls_ocsp_file" option
 on each connection, so a new file will be handled transparently on the
 next connection.
 
-Exim will check for a validity next update timestamp in the OCSP proof;
+Exim will check for a valid next update timestamp in the OCSP proof;
 if not present, or if the proof has expired, it will be ignored.
 
 At this point in time, we're gathering feedback on use, to determine if
 it's worth adding complexity to the Exim daemon to periodically re-fetch
-OCSP files and somehow handling multiple files.
+OCSP files and somehow handling multiple files.  There is no client support
+for OCSP in Exim, this is feature expected to be used by mail clients.