From: Jochen Sprickerhof <jspricke@debian.org>
Date: Mon, 26 Jun 2017 10:11:30 +0200
Subject: manpage-typos

===================================================================
---
 doc/pam_mount.8.in      |  4 ++--
 doc/pam_mount.conf.5.in | 20 ++++++++++----------
 doc/pam_mount.txt       |  2 +-
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/doc/pam_mount.8.in b/doc/pam_mount.8.in
index 8a1bf2e..5cb1c11 100644
--- a/doc/pam_mount.8.in
+++ b/doc/pam_mount.8.in
@@ -94,7 +94,7 @@ pam_mount, as the first "auth" module, will prompt for a password and export it
 to the PAM system.
 .IP "2." 4
 pam_ldap will use the password from the PAM system to try and authenticate the
-user. If this succedes, the user will be authenticated. If it fails, pam_unix
+user. If this succeeds, the user will be authenticated. If it fails, pam_unix
 will try to authenticate.
 .IP "3." 4
 pam_unix will try to authenticate the user if pam_ldap failed. If pam_unix
@@ -112,7 +112,7 @@ auth optional pam_mount.so
 .PP
 It may seem odd, but the first three lines will make it so that at least one of
 pam_unix2 or pam_ldap has to succeed. As you can see, pam_mount will be run
-\fBafter\fR successful authentification with these subsystems.
+\fBafter\fR successful authentication with these subsystems.
 .SH Encrypted disks
 .PP
 pam_mount supports a few types of crypto. The most common are encfs, dm\-crypt
diff --git a/doc/pam_mount.conf.5.in b/doc/pam_mount.conf.5.in
index b942f55..f4c3641 100644
--- a/doc/pam_mount.conf.5.in
+++ b/doc/pam_mount.conf.5.in
@@ -68,7 +68,7 @@ may fail if the filesystem kernel module is not loaded yet, since \fBmount\fP(8)
 will check /proc/partitions.
 .IP ""
 The fstypes \fBcifs\fP, \fBsmbfs\fP, \fBncpfs\fP, \fBfuse\fP,
-\fBnfs\fP and \fBnfs\fP are overriden by pam_mount and we run the respective
+\fBnfs\fP and \fBnfs\fP are overridden by pam_mount and we run the respective
 helper programs directly instead of invoking \fBmount\fP(8) with the basic
 default set of arguments which are often insufficient for networked
 filesystems. See this manpage's section "Examples" below for more details.
@@ -183,18 +183,18 @@ and then mounting further volumes from luserconfigs is possible.
 .TP
 \fB<mntoptions allow="\fP\fIoptions,...\fP\fB" />\fP
 The <mntoptions> elements determine which options may be specified in <volumes>
-in per-user configuration files (see <luserconf>). It does not apply to the
-master file. Specifying <mntoptions> is forbidden and ignored in per-user
+in per\-user configuration files (see <luserconf>). It does not apply to the
+master file. Specifying <mntoptions> is forbidden and ignored in per\-user
 configs. The default allowed list consists of "\fInosuid,nodev\fP", and this
 default is cleared when the first allow="..." attribute is seen by the config
 parser. All further allow="..." are additive, though.
 .TP
 \fB<mntoptions deny="\fP\fIoptions,...\fP\fB" />\fP
-Any options listed in deny may not appear in the option list of per-user
+Any options listed in deny may not appear in the option list of per\-user
 mounts. The default deny list is empty.
 .TP
 \fB<mntoptions require="\fP\fIoptions,...\fP\fB" />\fP
-All options listed in require must appear in the option list of per-user
+All options listed in require must appear in the option list of per\-user
 mounts. The default require list consists of "\fInosuid,nodev\fP", and like
 allow="", is cleared when first encountered by the parser, and is otherwise
 additive.
@@ -223,10 +223,10 @@ logging in.
 fd0ssh is a hack around OpenSSH that essentially makes it read passwords from
 stdin even though OpenSSH normally does not do that.
 .TP
-\fB<fsck>\fP\fIfsck -p %(FSCKTARGET)\fP\fB</fsck>\fP
+\fB<fsck>\fP\fIfsck \-p %(FSCKTARGET)\fP\fB</fsck>\fP
 Local volumes will be checked before mounting if this program is set.
 .TP
-\fB<ofl>\fP\fIofl -k%(SIGNAL) %(MNTPT)\fP\fB</ofl>\fP
+\fB<ofl>\fP\fIofl \-k%(SIGNAL) %(MNTPT)\fP\fB</ofl>\fP
 The Open File Lister is used to identify processes using files within the given
 subdirectory, and optionally send a signal to those processes.
 .TP
@@ -350,7 +350,7 @@ Remember that \fB~\fP can be used in the mountpoint attribute to denote the
 home directory as retrievable through getpwent(3).
 .SS sshfs and ccgfs
 .PP
-Not specifying any path after the colon (:) uses the path whereever ssh will
+Not specifying any path after the colon (:) uses the path wherever ssh will
 put you in, usually the home directory.
 .PP
 <volume fstype="fuse" path="sshfs#%(USER)@fileserver:" mountpoint="~" />
@@ -386,7 +386,7 @@ example):
 .PP
 <volume user="test" fstype="tmpfs" mountpoint="/home/test"
 options="size=10M,uid=%(USER),mode=0700" />
-.SS dm-crypt volumes
+.SS dm\-crypt volumes
 .PP
 Crypt mounts require a kernel with CONFIG_BLK_DEV_DM and CONFIG_DM_CRYPT
 enabled, as well as all the ciphers that are going to be used, e.g.
@@ -403,7 +403,7 @@ cipher="aes\-cbc\-essiv:sha256" />
 .PP
 cryptoloop is not explicitly supported by pam_mount. Citing the Linux kernel
 config help text: "WARNING: This device [cryptoloop] is not safe for
-journal[l]ed filesystems[...]. Please use the Device Mapper [dm-crypt] module
+journal[l]ed filesystems[...]. Please use the Device Mapper [dm\-crypt] module
 instead."
 .SS OpenBSD encrypted home
 OpenBSD encrypted home directory example:
diff --git a/doc/pam_mount.txt b/doc/pam_mount.txt
index f511514..6fd1980 100644
--- a/doc/pam_mount.txt
+++ b/doc/pam_mount.txt
@@ -95,7 +95,7 @@ PAM configuration
            and export it to the PAM system.
 
        2.  pam_ldap will use the password from  the  PAM  system  to  try  and
-           authenticate the user. If this succedes, the user will be authenti-
+           authenticate the user. If this succeeds, the user will be authenti-
            cated. If it fails, pam_unix will try to authenticate.
 
        3.  pam_unix will try to authenticate the user if pam_ldap  failed.  If
