From 41e4c01a7fb8f78ebd1e2a0656cb49fdad156f95 Mon Sep 17 00:00:00 2001
From: b1v1r <b1v1r@9017d574-64ec-4062-9424-5e00b32a252b>
Date: Tue, 24 Mar 2009 21:22:17 +0000
Subject: [PATCH] Fix a small typo.

---
 doc/modsecurity2-data-formats.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/modsecurity2-data-formats.xml b/doc/modsecurity2-data-formats.xml
index 3f0ed5cc..e8eb70d5 100644
--- a/doc/modsecurity2-data-formats.xml
+++ b/doc/modsecurity2-data-formats.xml
@@ -4,7 +4,7 @@
 <article>
     <title>ModSecurity 2 Data Formats</title>
     <articleinfo>
-        <releaseinfo>Version 2.5.9 (March 5, 2009)</releaseinfo>
+        <releaseinfo>Version 2.5.10-dev1 (March 24, 2009)</releaseinfo>
         <copyright>
             <year>2004-2009</year>
             <holder>Breach Security, Inc. (<ulink url="http://www.breach.com"
@@ -17,7 +17,7 @@
         and products.</para>
     <section>
         <title>Alerts</title>
-        <para>As part of its operations ModSecurity will emit alerts, which are eather
+        <para>As part of its operations ModSecurity will emit alerts, which are either
                 <emphasis>warnings</emphasis> (non-fatal) or <emphasis>errors</emphasis> (fatal,
             usually leading to the interception of the transaction in question). Below is an example
             of a ModSecurity alert entry:</para>