From d2f0dbd8b0421e1af6ea202533a18dc58d677c9c Mon Sep 17 00:00:00 2001
From: neil_a_wilson <neil_a_wilson@localhost>
Date: Sun, 02 Sep 2007 02:05:01 +0000
Subject: [PATCH] Correct a number of spelling errors in configuration definitions.
---
opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/PasswordPolicyConfiguration.xml | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/PasswordPolicyConfiguration.xml b/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/PasswordPolicyConfiguration.xml
index 1222414..8f91647 100644
--- a/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/PasswordPolicyConfiguration.xml
+++ b/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/PasswordPolicyConfiguration.xml
@@ -764,7 +764,7 @@
<adm:property name="lockout-failure-expiration-interval"
mandatory="false" multi-valued="false">
<adm:synopsis>
- pecifies the length of time that should pass before an
+ Specifies the length of time that should pass before an
authentication failure is no longer counted against a user for the
purposes of account lockout.
</adm:synopsis>
@@ -922,12 +922,12 @@
multi-valued="false">
<adm:synopsis>
Specifies the maximum length of time that an account may remain
- idle (i.e., the associated user does notauthenticate to the
+ idle (i.e., the associated user does not authenticate to the
server) before that user is locked out.
</adm:synopsis>
<adm:description>
Specifies the maximum length of time that an account may remain
- idle (i.e., the associated user does notauthenticate to the
+ idle (i.e., the associated user does not authenticate to the
server) before that user is locked out. The value of this
attribute should be an integer followed by a unit of seconds,
minutes, hours, days, or weeks. A value of 0 seconds indicates
@@ -961,7 +961,7 @@
should fail if a failure occurs while attempting to update password policy
state information (e.g., to clear a record of previous authentication
failures or to update the last login time), or even whether to reject a
- bind request if it is known aheaed of time that it will not be possible to
+ bind request if it is known ahead of time that it will not be possible to
update the authentication failure times in the event of an unsuccessful
bind attempt (e.g., if the backend writability mode is disabled).
</adm:synopsis>
--
Gitblit v1.10.0