summaryrefslogtreecommitdiff
path: root/doc/mwg/Linux-PAM_MWG.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/mwg/Linux-PAM_MWG.xml')
-rw-r--r--doc/mwg/Linux-PAM_MWG.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/mwg/Linux-PAM_MWG.xml b/doc/mwg/Linux-PAM_MWG.xml
index 5a09a7cf..a381dc6c 100644
--- a/doc/mwg/Linux-PAM_MWG.xml
+++ b/doc/mwg/Linux-PAM_MWG.xml
@@ -16,7 +16,7 @@
<email>kukuk@thkukuk.de</email>
</author>
</authorgroup>
- <releaseinfo>Version 1.0, 3. April 2008</releaseinfo>
+ <releaseinfo>Version 1.1, 16. June 2009</releaseinfo>
<abstract>
<para>
This manual documents what a programmer needs to know in order
@@ -71,7 +71,7 @@
</para>
</section>
- <section id="mwg-introducton-synopsis">
+ <section id="mwg-introduction-synopsis">
<title>Synopsis</title>
<programlisting>
#include &lt;security/pam_modules.h&gt;
@@ -97,7 +97,7 @@ gcc -shared -o pam_module.so pam_module.o -lpam
First, we cover what the module should expect from the
<emphasis remap='B'>Linux-PAM</emphasis> library and a
<emphasis remap='B'>Linux-PAM</emphasis> aware application.
- Essesntially this is the <filename>libpam.*</filename> library.
+ Essentially this is the <filename>libpam.*</filename> library.
</para>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="pam_set_data.xml"/>
@@ -169,7 +169,7 @@ gcc -shared -o pam_module.so pam_module.o -lpam
token of some lesser user. In other cases it may not be
appropriate: when <command>joe</command> maliciously wants
to reset <command>alice</command>'s password; or when anyone
- other than the user themself wishes to reset their
+ other than the user them self wishes to reset their
<emphasis>KERBEROS</emphasis> authentication token. A policy
for this action should be defined by any reasonable
authentication scheme, the module writer should consider