* ntsec.sgml: Fix typo.

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index b3f0b873b591f3d0d0e8863002406596c3921113..de7ab0649cbf085c901eec2708382d06df06e5ec 100644 (file)
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,7 @@
+2008-12-04  Corinna Vinschen  <corinna@vinschen.de>
+
+       * ntsec.sgml: Fix typo.
+
 2008-12-03  Corinna Vinschen  <corinna@vinschen.de>
 
        * ntsec.sgml: Revamp parts of the doc for clearness.

diff --git a/winsup/doc/ntsec.sgml b/winsup/doc/ntsec.sgml
index 9a22092ec608aa11ce43ee7cd95a9ac016408749..61059a9a7ccc67ee04d2376649d43d67ec57433c 100644 (file)
--- a/winsup/doc/ntsec.sgml
+++ b/winsup/doc/ntsec.sgml
@@ -826,11 +826,11 @@ can access the password of all keys stored this way in the registry.</para>
 
 <para>Conclusion: If your system is used exclusively by you, and if
 you're also the only administrator of your system, and if your system is
-adequately locked down to prevent malicious access, you can savely use
+adequately locked down to prevent malicious access, you can safely use
 this method.  If your machine is part of a network which has
 dedicated administrators, and you're not one of these administrators,
 but you (think you) can trust your administrators, you can probably
-savely use this method.</para>
+safely use this method.</para>
 
 <para>In all other cases, don't use this method.  You have been warned.</para>