[PATCH}pam_winbind grammar and typos

[Jeremy Allison]

On Tue, Aug 25, 2020 at 01:37:13PM +0100, Rowland penny via samba-technical wrote:
> Attempt to fix the grammar and typos in the pam_winbind manpage, see
> attached patch.

LGTM Rowland, RB+ and pushed. Feel free to re-push if
the autobuild fails :-).

Jeremy.

> From 2ca75b1b3ec2eefb169b222177f6bce4a6e61e47 Mon Sep 17 00:00:00 2001
> From: Rowland Penny <rpenny at samba.org>
> Date: Tue, 25 Aug 2020 13:19:28 +0100
> Subject: [PATCH] pam_winbind manpage: grammar and typos
> 
> Signed-off-by: Rowland Penny <rpenny at samba.org>
> ---
>  docs-xml/manpages/pam_winbind.8.xml | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/docs-xml/manpages/pam_winbind.8.xml b/docs-xml/manpages/pam_winbind.8.xml
> index 32030ef0ecc..171bb408757 100644
> --- a/docs-xml/manpages/pam_winbind.8.xml
> +++ b/docs-xml/manpages/pam_winbind.8.xml
> @@ -165,23 +165,23 @@
>  		(when the DIR type is supported by the system's Kerberos
>  		library). In case of FILE a credential cache in the form of
>  		/tmp/krb5cc_UID will be created -  in case of DIR you NEED
> -		to specify a directory. UID is replaced with the numeric
> -		user id. The UID directory is being created. The path up to
> -		the directory should already exist. Check the details of the
> -		Kerberos implmentation.</para>
> +		to specify a directory which must exist, the UID directory
> +		will be created in the specified directory.
> +		In all cases UID is replaced with the numeric user id.
> +		Check the details of the Kerberos implementation.</para>
>  
>  		<para>When using the KEYRING type, the supported mechanism is
>  		<quote>KEYRING:persistent:UID</quote>, which uses the Linux
>  		kernel keyring to store credentials on a per-UID basis.
> -		The KEYRING has its limitations. As it is secure kernel memory,
> -		for example bulk sorage of credentils is for not possible.</para>
> +		KEYRING has limitations. For example, it is secure kernel memory,
> +		so bulk storage of credentials is not possible.</para>
>  
> -		<para>When using th KCM type, the supported mechanism is
> +		<para>When using the KCM type, the supported mechanism is
>  		<quote>KCM:UID</quote>, which uses a Kerberos credential
> -		manaager to store credentials on a per-UID basis similar to
> +		manager to store credentials on a per-UID basis similar to
>  		KEYRING. This is the recommended choice on latest Linux
> -		distributions, offering a Kerberos Credential Manager. If not
> -		we suggest to use KEYRING as those are the most secure and
> +		distributions that offer a Kerberos Credential Manager. If not,
> +		we suggest to use KEYRING, as those are the most secure and
>  		predictable method.</para>
>  
>  		<para>It is also possible to define custom filepaths and use the "%u"
> -- 
> 2.20.1
>