From 562a015aeb1f2ec2778cdc4898c50e467e04e8b6 Mon Sep 17 00:00:00 2001
From: Luke Taylor <luke.taylor@springsource.com>
Date: Thu, 17 Mar 2005 14:14:18 +0000
Subject: [PATCH] Javadoc typo corrected.

---
 .../acegisecurity/providers/cas/StatelessTicketCache.java | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/src/main/java/org/acegisecurity/providers/cas/StatelessTicketCache.java b/core/src/main/java/org/acegisecurity/providers/cas/StatelessTicketCache.java
index ad406e040e..36523b83dc 100644
--- a/core/src/main/java/org/acegisecurity/providers/cas/StatelessTicketCache.java
+++ b/core/src/main/java/org/acegisecurity/providers/cas/StatelessTicketCache.java
@@ -20,11 +20,11 @@ package net.sf.acegisecurity.providers.cas;
  * 
  * <p>
  * When a service ticket or proxy ticket is validated against the CAS server,
- * it is unable to be used again. Most types of callers  are stateful and are
+ * it is unable to be used again. Most types of callers are stateful and are
  * associated with a given <code>HttpSession</code>. This allows the
  * affirmative CAS validation outcome to be stored in the
  * <code>HttpSession</code>, meaning the removal of the ticket from the CAS
- * server is not an issue issue.
+ * server is not an issue.
  * </p>
  * 
  * <P>
@@ -51,8 +51,8 @@ package net.sf.acegisecurity.providers.cas;
  * </p>
  * 
  * <P>
- * Implementations should provide a reasonable timeout on stored entries,  such
- * that the stateless caller are not required to unnecessarily acquire  fresh
+ * Implementations should provide a reasonable timeout on stored entries, such
+ * that the stateless caller are not required to unnecessarily acquire fresh
  * CAS service tickets or proxy tickets.
  * </p>
  *