From a159ae6e3a5c05ad5c5b9fb03f111c4e3314f1e2 Mon Sep 17 00:00:00 2001
From: John Terpstra <jht@samba.org>
Date: Thu, 30 Sep 2004 04:40:00 +0000
Subject: Fix typo. (This used to be commit
 630b67df12430d4f58e4e461101daf788805549e)

---
 docs/Samba-HOWTO-Collection/BDC.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/Samba-HOWTO-Collection/BDC.xml')

diff --git a/docs/Samba-HOWTO-Collection/BDC.xml b/docs/Samba-HOWTO-Collection/BDC.xml
index 6f70eea867..0103d6cf7b 100644
--- a/docs/Samba-HOWTO-Collection/BDC.xml
+++ b/docs/Samba-HOWTO-Collection/BDC.xml
@@ -548,7 +548,7 @@ regarding its behavior.
 </para></note>
 
 <para>
-The use of the <smbconfoption><name>idmap backend</name><value>ldap:ldap://master.quenya/org</value></smbconfoption>
+The use of the <smbconfoption><name>idmap backend</name><value>ldap:ldap://master.quenya.org</value></smbconfoption>
 option on a BDC only make sense where ldapsam is used on a PDC. The purpose for an LDAP based idmap backend is
 also to allow a domain-member (without its own passdb backend) to use winbindd to resolve Windows network users
 and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on Domain
-- 
cgit