You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ja...@apache.org on 2015/02/04 22:38:16 UTC
svn commit: r1657407 - in /httpd/httpd/trunk/docs/manual/mod:
mod_unique_id.html.en mod_unique_id.xml
Author: jailletc36
Date: Wed Feb 4 21:38:15 2015
New Revision: 1657407
URL: http://svn.apache.org/r1657407
Log:
Fix typo spotted by micha137 in online doc
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_unique_id.html.en
httpd/httpd/trunk/docs/manual/mod/mod_unique_id.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_unique_id.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_unique_id.html.en?rev=1657407&r1=1657406&r2=1657407&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_unique_id.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_unique_id.html.en Wed Feb 4 21:38:15 2015
@@ -196,7 +196,7 @@ identifier for each request</td></tr>
and can otherwise use the same alphabet and bit length. Since
the time stamps are essentially an increasing sequence, it's
sufficient to have a <em>flag second</em> in which all machines
- in the cluster stop serving and request, and stop using the old
+ in the cluster stop serving any request, and stop using the old
encoding format. Afterwards they can resume requests and begin
issuing the new encodings.</p>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_unique_id.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_unique_id.xml?rev=1657407&r1=1657406&r2=1657407&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_unique_id.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_unique_id.xml Wed Feb 4 21:38:15 2015
@@ -182,7 +182,7 @@ identifier for each request</description
and can otherwise use the same alphabet and bit length. Since
the time stamps are essentially an increasing sequence, it's
sufficient to have a <em>flag second</em> in which all machines
- in the cluster stop serving and request, and stop using the old
+ in the cluster stop serving any request, and stop using the old
encoding format. Afterwards they can resume requests and begin
issuing the new encodings.</p>