Manual pages: wording fix: "another" ==> "other"

In several pages, there is a consistent wording problem: "another"
where "other" should be used. This wording problem can be
surprisingly confusing for native speakers, especially those
unaware that in some other languages, "another" and "other" can be
expressed with the same word.

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>

disk-utils/fdisk.8

@@ -207,7 +207,7 @@ partition table before you write it to the device.
 And vice-versa it is possible to write the current in-memory disk layout
 to the script file by command 'O'.
 .PP
-The script files are compatible between cfdisk, sfdisk, fdisk and another
+The script files are compatible between cfdisk, sfdisk, fdisk and other
 libfdisk applications. For more details see
 .BR sfdisk (8).
 

disk-utils/sfdisk.8

@@ -61,7 +61,7 @@ partitions.
 
 .B sfdisk
 uses BLKRRPART (reread partition table) ioctl to make sure that the device is
-not used by system or another tools (see also \-\-no-reread).  It's possible that
+not used by system or other tools (see also \-\-no-reread).  It's possible that
 this feature or another sfdisk activity races with \fBudevd\fR.  The recommended way
 how to avoid possible collisions is to use \fB\-\-lock\fR option.
 The exclusive lock will cause udevd to skip the event handling on the device. 
@@ -421,7 +421,7 @@ GPT; a shortcut or an alias. It's recommended to use two letters for MBR hex cod
 avoid collision between deprecated shortcut 'E' and '0E' MBR hex code. For backward
 compatibility sfdisk tries to interpret
 .I type
-as a shortcut as a first possibility in partitioning scripts although on another places (e.g.
+as a shortcut as a first possibility in partitioning scripts although on other places (e.g.
 \fB\-\-part-type command)\fR it tries shortcuts as the last possibility.
 
 Since v2.36 libfdisk supports partition type aliases as extension to shortcuts. The alias is a

login-utils/runuser.1

@@ -109,7 +109,7 @@ in order to make the shell a login shell
 .BR \-P , " \-\-pty"
 Create pseudo-terminal for the session. The independent terminal provides
 better security as user does not share terminal with the original
-session.  This allow to avoid TIOCSTI ioctl terminal injection and another
+session.  This allow to avoid TIOCSTI ioctl terminal injection and other
 security attacks against terminal file descriptors. The all session is also
 possible to move to background (e.g., "runuser \-\-pty \-u username \-\- command &").
 If the pseudo-terminal is enabled then runuser command works

login-utils/su.1

@@ -122,7 +122,7 @@ This option is ignored if the option \fB\-\-login\fR is specified.
 .BR \-P , " \-\-pty"
 Create pseudo-terminal for the session. The independent terminal provides
 better security as user does not share terminal with the original
-session.  This allow to avoid TIOCSTI ioctl terminal injection and another
+session.  This allow to avoid TIOCSTI ioctl terminal injection and other
 security attacks against terminal file descriptors. The all session is also
 possible to move to background (e.g., "su \-\-pty \- username \-c
 application &"). If the pseudo-terminal is enabled then su command works

misc-utils/blkid.8

@@ -145,7 +145,7 @@ will print all of the devices that match the search parameter.
 This option forces
 .B blkid
 to use udev when used for LABEL or UUID tokens in \fB\-\-match\-token\fR. The
-goal is to provide output consistent with another utils (like mount, etc.)
+goal is to provide output consistent with other utils (like mount, etc.)
 on systems where the same tag is used for multiple devices.
 .TP
 \fB\-L\fR, \fB\-\-label\fR \fIlabel\fR

sys-utils/lsmem.1

@@ -70,7 +70,8 @@ Produce output in raw format.  All potentially unsafe characters are hex-escaped
 .TP
 .BR \-S , " \-\-split " \fIlist\fP
 Specify which columns (attributes) use to split memory blocks to ranges.  The
-supported columns are STATE, REMOVABLE, NODE and ZONES, or "none". The another columns are
+supported columns are STATE, REMOVABLE, NODE and ZONES, or "none".
+The other columns are
 silently ignored. For more details see DESCRIPTION above.
 .TP
 .BR \-s , " \-\-sysroot " \fIdirectory\fP

sys-utils/mount.8

@@ -64,7 +64,7 @@ command serves to attach the filesystem found on some device
 to the big file tree.  Conversely, the
 .BR umount (8)
 command will detach it again.  The filesystem is used to control how data is
-stored on the device or provided in a virtual way by network or another services.
+stored on the device or provided in a virtual way by network or other services.
 
 The standard form of the
 .B mount
@@ -439,7 +439,8 @@ will be writable, but the
 will be read-only.
 
 It's also possible to change nosuid, nodev, noexec, noatime, nodiratime and
-relatime VFS entry flags by "remount,bind" operation.  The another (for example
+relatime VFS entry flags by "remount,bind" operation.
+The other (for example
 filesystem specific flags) are silently ignored.  It's impossible to change mount
 options recursively (for example with \fB\-o rbind,ro\fR).
 
@@ -696,7 +697,7 @@ and calls
 .BR mount (2)
 system call, otherwise it runs in the original mount namespace.
 It means that the target namespace does not have
-to contain any libraries or another requirements necessary to execute
+to contain any libraries or other requirements necessary to execute
 .BR mount (2)
 command.
 .sp
@@ -1372,7 +1373,7 @@ system call.  The suggested format is \fBX-\fIappname\fR.\fIoption\fR.
 .TP
 .B x-*
 The same as \fBX-*\fR options, but stored permanently in the user space. It
-means the options are also available for umount or another operations.  Note
+means the options are also available for umount or other operations.  Note
 that maintain mount options in user space is tricky, because it's necessary use
 libmount based tools and there is no guarantee that the options will be always
 available (for example after a move mount operation or in unshared namespace).

sys-utils/umount.8

@@ -55,7 +55,7 @@ working directory there, or when a swap file on it is in use.  The
 offending process could even be
 .B umount
 itself - it opens libc, and libc in its turn may open for example locale
-files.  A lazy unmount avoids this problem, but it may introduce another
+files.  A lazy unmount avoids this problem, but it may introduce other
 issues. See \fB\-\-lazy\fR description below.
 .SH OPTIONS
 .TP
@@ -149,7 +149,7 @@ and calls
 .BR umount (2)
 system call, otherwise it runs in the original namespace.
 It means that the target mount namespace does not have
-to contain any libraries or another requirements necessary to execute
+to contain any libraries or other requirements necessary to execute
 .BR umount (2)
 command.
 .sp
@@ -267,7 +267,7 @@ A \fBhelper=\fItype\fR marker in the mtab file will redirect
 all unmount requests
 to the \fB/sbin/umount.\fItype\fR helper independently of UID.
 .PP
-Note that \fI/etc/mtab\fR is currently deprecated and helper= and another
+Note that \fI/etc/mtab\fR is currently deprecated and helper= and other
 userspace mount options are maintained by libmount.
 .SH ENVIRONMENT
 .IP LIBMOUNT_FSTAB=<path>

term-utils/scriptreplay.1

@@ -69,7 +69,7 @@ Specifies how to use CR (0x0D, carriage return) character from log files.
 The default mode is
 .IR auto ,
 in this case CR is replaced with line break for stdin log, because otherwise
-scriptreplay will overwrite the same line.  The another modes are
+scriptreplay will overwrite the same line.  The other modes are
 .I never
 and
 .IR always .

text-utils/column.1

@@ -111,7 +111,7 @@ Insert empty line to the table for each empty line on input. The default
 is ignore empty lines at all.
 .IP "\fB\-r, \-\-tree\fP \fIcolumn\fP"
 Specify column to use tree-like output. Note that the circular dependencies and
-another anomalies in child and parent relation are silently ignored.
+other anomalies in child and parent relation are silently ignored.
 .IP "\fB\-i, \-\-tree\-id\fP \fIcolumn\fP"
 Specify column with line ID to create child-parent relation.
 .IP "\fB\-p, \-\-tree\-parent\fP \fIcolumn\fP"