s390-tools: Fix typos that were detected by lintian as 'typo-in-manual-page'

The static analysis tool for Debian packages 'lintian', especially if called
like 'lintian -EvIL +pedantic', checks manual pages for correctness and typos.
This commit fixes typos that were identified by lintian and marked with
'typo-in-manual-page' while s390-tools version 2.20.0 was packaged.

Closes: https://github.com/ibm-s390-linux/s390-tools/pull/134
Signed-off-by: Frank Heimes <frank.heimes@canonical.com>
Acked-by: Steffen Maier maier@linux.ibm.com [ziomon]
Acked-by: Ingo Franzki ifranzki@linux.ibm.com [zkey]
[hoeppner@linux.ibm.com: fix commit message]
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>

dasdinfo/dasdinfo.8

@@ -47,7 +47,7 @@ Print DASD uid without z/VM minidisk token
 
 z/VM may provide an additional token that can be used to distinguish
 between different minidisks (see --extended-uid option).  To remain
-compatibile with systems that were installed on older Linux or z/VM
+compatible with systems that were installed on older Linux or z/VM
 levels, the -u option will print the uid excluding any z/VM-provided
 minidisk token.
 

zconf/chccwdev.8

@@ -46,7 +46,7 @@ Set the online attribute to the desired value ((forced) online or
 (safe) offline).
 .TP
 3.
-Set all the attributes that havn't been set, yet. At this point invalid
+Set all the attributes that haven't been set, yet. At this point invalid
 attribute names will always cause an error.
 .RE
 .P

zconf/dasdstat.8

@@ -28,8 +28,8 @@ dasdstat \- read or modify the statistics of the DASD device driver.
 The dasdstat command provides easy access to the debugfs based
 statistics of the DASD device driver.
 
-The DASD statistics feature allows to gather statistical data for the
-I/O requests processed by the DASD device driver. This data can be
+The DASD statistics feature allows one to gather statistical data for
+the I/O requests processed by the DASD device driver. This data can be
 collected for individual DASD CCW devices (including PAV base and
 alias devices), DASD block devices, or globally for all requests
 handled by the DASD device driver.

zconf/zcrypt/lszcrypt.8

@@ -207,7 +207,7 @@ S - APSC available: card/queue can handle requests with the special bit
 enabled.
 .br
 M - Accelerator card/queue with support for RSA ME with up to 4k key size.
-.Sr
+.br
 C - Accelerator card/queue with support for RSA CRT with up to 4k key size.
 .br
 D - Card/queue is providing CCA functions (this is the CCA Coprocessor mode).

zdev/man/chzdev.8

@@ -162,7 +162,7 @@ chzdev supports the following device states:
 .PP
 .TP 12
 .B online
-The device is enabled in the active configuation and set up to provide a Linux
+The device is enabled in the active configuration and set up to provide a Linux
 function such as a block device like /dev/dasda, or a networking interface like
 eth0.
 .PP

ziomon/ziomon_mgr.8

@@ -40,7 +40,7 @@ Be verbose.
 
 .TP
 .BR "\-e" " or " "\-\-binary-offsets"
-Lengthes of the raw data structures.
+Lengths of the raw data structures.
 
 .TP
 .BR "\-f" " or " "\-\-force"

ziomon/ziomon_util.8

@@ -53,7 +53,7 @@ Time to elapse between samples in seconds.
 .BR "\-i" " or " "\-\-interval-length"
 Time to elapse between sending data in seconds. The samples will be aggregated
 over this period. Defaults to the duration.
-The interval lengh must be a multiple of the sample length.
+The interval length must be a multiple of the sample length.
 
 .TP
 .BR "\-d" " or " "\-\-duration"

zipl/man/zipl.8.in

@@ -41,7 +41,7 @@ time.
 .B BLS config files:
 boot configurations are specified using BootLoaderSpec (BLS) configuration files. The
 .BR zipl.conf (5)
-configuration file is still used to specify parameters or aditional boot configurations.
+configuration file is still used to specify parameters or additional boot configurations.
 .PP
 
 To use a single boot configuration section, provide its name as parameter to

zkey/ekmfweb/zkey-ekmfweb.1

@@ -12,8 +12,8 @@ Management Foundation \- Web Edition)
 .SH DESCRIPTION
 The \fBzkey\-ekmfweb.so\fP library is a key management system plugin for
 \fBzkey\fP and provides an interface to \fBEKMF Web\fP (IBM Enterprise Key
-Management Foundation \- Web Edition). It allows to integrate the external key
-management system EKMF Web into zkey.
+Management Foundation \- Web Edition). It allows one to integrate the external
+key management system EKMF Web into zkey.
 .PP
 Secure AES keys can be generated in EKMF Web and are then imported into the zkey
 secure key repository. The keys can be used to encrypt volumes, the same way
@@ -494,4 +494,4 @@ Refreshes secure keys from EKMF Web where the name starts with 'sec'.
 .TP
 .B zkey kms refresh \-\-name seckey \-\-refresh\-properties
 Refreshes the secure key with the name 'seckey' from EKMF Web and also refreshes
-the key properties.
+the key properties.

zkey/kmip/zkey-kmip.1

@@ -12,7 +12,7 @@ Interoperability Protocol (KMIP)
 .SH DESCRIPTION
 The \fBzkey\-kmip.so\fP library is a key management system plugin for
 \fBzkey\fP and provides an interface to KMIP servers. With this plugin, you can
-integrate external KMIP\-based key manangement systems into zkey.
+integrate external KMIP\-based key management systems into zkey.
 .PP
 AES keys can be generated by a KMIP server and then imported into the zkey
 secure key repository as secure keys. The keys can be used to encrypt
@@ -547,7 +547,7 @@ Specifies the \fBcustom/vendor attribute scheme\fP for KMIP servers supporting
 the KMIP protocol version 2.0 or higher. Possible values are \fBv1\-style\fP and
 \fBv2\-style\fP. For \fBv1\-style\fP, the attribute's \fBVendor Identifier\fP is
 set to \fBx\fP, and \fBAttribute Name\fP is set to \fBzkey\-<something>\fP.
-This coresponds to the KMIP custom attribute style of the KMIP protocol version
+This corresponds to the KMIP custom attribute style of the KMIP protocol version
 1.0 - 1.4. For \fBv2\-style\fP, the attribute's \fBVendor Identifier\fP is
 set to \fBzkey\fP, and \fBAttribute Name\fP is set to \fB<something>\fP.
 .IP "\(bu" 2

zkey/zkey.1

@@ -66,7 +66,7 @@ EP11 cryptographic adapter.
 Secure keys in a key repository can either be generated locally, or by a \fBkey
 management system (KMS)\fP. A key repository can be bound to a key management
 system (KMS) via a key management system plugin (KMS plugin), which builds the
-interface to the key management system. This allows to integrate a zkey key
+interface to the key management system. This allows one to integrate a zkey key
 repository into an enterprise key management system, that manages the keys in
 a larger environment.
 When a key repository is bound to a key management system, then all keys are
@@ -463,7 +463,7 @@ whether it is a secure key that can be used for the XTS cipher mode, the textual
 description, associated cryptographic adapters (APQNs) and volumes, the
 sector size, the key verification pattern, timestamps for key creation, last
 modification and last re-encipherment, and whether the key is local or
-bound to a key management systen (KMS).
+bound to a key management system (KMS).
 .
 .SS "Remove existing AES secure keys from the secure key repository"
 .
@@ -1831,7 +1831,7 @@ the secure key to type CCA-AESCIPHER.
 This option is only used for secure keys contained in the secure key repository.
 .TP
 .BR \-F ", " \-\-force\fP
-The user is prompted to confirm the convertion of a secure key. Use this option
+The user is prompted to confirm the conversion of a secure key. Use this option
 to convert a secure key without prompting for a confirmation.
 .
 .
@@ -2129,4 +2129,4 @@ If
 .B $ZKEY_KMS_PLUGINS
 is set, it specifies the name of the KMS plugin configuration file.
 If it is not set, then the default KMS plugin configuration file
-\fB/etc/zkey/kms-plugins.conf\fP is used.
+\fB/etc/zkey/kms-plugins.conf\fP is used.