# HG changeset patch
# User markus schnalke <meillo@marmaro.de>
# Date 1447186144 -3600
# Node ID e294684cf3383b6abb3bb9fd245234ab705fdbae
# Parent  7608a7416bc0367b507022cbd613aef2894717ab# Parent  ec76f8926598ed3a80417f19d1e31e432197a078
merge

diff -r 7608a7416bc0 -r e294684cf338 cut.en.ms
--- a/cut.en.ms	Thu Nov 05 17:27:04 2015 +0100
+++ b/cut.en.ms	Tue Nov 10 21:09:04 2015 +0100
@@ -121,7 +121,7 @@
 selection specification is irrelevant; it doesn't even matter if
 fields occur multiple times. Thus, the invocation
 \f(CWcut -c 5-8,1,4-6\fP outputs the characters number
-1, 4, 5, 6, 7, and 8 in exactly this order. The
+1, 4, 5, 6, 7, and 8 in ascending order. The
 selection specification resembles mathematical set theory: Each
 specified field is part of the solution set. The fields in the
 solution set are always in the same order as in the input. To
@@ -472,7 +472,7 @@
 It is noteworthy that the GNU coreutils in all versions
 describe the performed action as a removal of parts of the
 input, although the user clearly selects the parts that then
-consistute the output. Probably the words ``cut out'' are too
+constitute the output. Probably the words ``cut out'' are too
 misleading. HP-UX tried to be more clear.
 .PP
 Different terms are also used for the part being