From 9b7dd1d439cbdf26868a9823625a247af30282c9 Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Thu, 24 Nov 2011 16:20:03 +0000
Subject: [PATCH] uniqueMember fits better with the example above than member

---
 opendj3/src/main/docbkx/admin-guide/chap-groups.xml |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/opendj3/src/main/docbkx/admin-guide/chap-groups.xml b/opendj3/src/main/docbkx/admin-guide/chap-groups.xml
index 04fea6f..57e7f23 100644
--- a/opendj3/src/main/docbkx/admin-guide/chap-groups.xml
+++ b/opendj3/src/main/docbkx/admin-guide/chap-groups.xml
@@ -377,8 +377,8 @@
  <literal>check-references-filter-criteria</literal> to identify the attribute
  and the filter. For example, you can specify that group members must be person
  entries by setting <literal>check-references-filter-criteria</literal> to
- <literal>member:(objectclass=person)</literal>. To ensure that entries must
- be located in the same naming context, set
+ <literal>uniqueMember:(objectclass=person)</literal>. To ensure that entries
+ must be located in the same naming context, set
  <literal>check-references-scope-criteria</literal> to
  <literal>naming-context</literal>.</para>
  </section>

--
Gitblit v1.10.0