summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLouis Sautier <sautier.louis@gmail.com>2018-12-13 16:12:42 +0100
committerTomáš Mráz <t8m@users.noreply.github.com>2019-01-10 17:09:09 +0100
commit2ec68e871038665749338da59d938a33c3248110 (patch)
tree7558c9a1af4518525402ffb4d098a9b7d4084858
parentc426914fa166ffb0482b6f6ad659ddf17d5dfaa1 (diff)
Fix a typo in the documentation
-rw-r--r--doc/man/pam_conv.3.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/man/pam_conv.3.xml b/doc/man/pam_conv.3.xml
index 0098ff94..5106ddf7 100644
--- a/doc/man/pam_conv.3.xml
+++ b/doc/man/pam_conv.3.xml
@@ -133,10 +133,10 @@ struct pam_conv {
single form with many messages/prompts on at once.
</para>
<para>
- In passing, it is worth noting that there is a descrepency between
+ In passing, it is worth noting that there is a discrepancy between
the way Linux-PAM handles the const struct pam_message **msg
- conversation function argument from the way that Solaris' PAM
- (and derivitives, known to include HP/UX, are there others?) does.
+ conversation function argument and the way that Solaris' PAM
+ (and derivatives, known to include HP/UX, are there others?) does.
Linux-PAM interprets the msg argument as entirely equivalent to the
following prototype
const struct pam_message *msg[] (which, in spirit, is consistent with