docs: Fix typo in the howto collection.

Thanks to Hermann Gausterer <git-samba-2012@mrq1.org> for reporting!

Karolin

Autobuild-User(master): Volker Lendecke <vl@samba.org>
Autobuild-Date(master): Mon Dec  3 12:36:14 CET 2012 on sn-devel-104

1 files changed, 1 insertions, 1 deletions

diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml
index f2f3a303ef..2b12e11f19 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml
@@ -309,7 +309,7 @@ Ideally, the implementation of SSO should reduce complexity and reduce administa
 The initial goal of many network administrators is often to create and use a centralized identity management
 system. It is often assumed that such a centralized system will use a single authentication infrastructure
 that can be used by all information systems. The Microsoft Windows NT4 security domain architecture and the
-Micrsoft active directory service are often put forward as the ideal foundation for such a system. It is
+Microsoft active directory service are often put forward as the ideal foundation for such a system. It is
 conceptually simple to install an external authentication agent on each of the disparate infromation systems
 that can then use the Microsoft (NT4 domain or ads service) for user authentication and access control. The
 wonderful dream of a single centralized authentication service is commonly broken when realities are realized.