docs/cut
changeset 40:e294684cf338
merge
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Tue, 10 Nov 2015 21:09:04 +0100 |
parents | 7608a7416bc0 ec76f8926598 |
children | e2961496d097 |
files | cut.en.ms |
diffstat | 1 files changed, 2 insertions(+), 2 deletions(-) [+] |
line diff
1.1 --- a/cut.en.ms Thu Nov 05 17:27:04 2015 +0100 1.2 +++ b/cut.en.ms Tue Nov 10 21:09:04 2015 +0100 1.3 @@ -121,7 +121,7 @@ 1.4 selection specification is irrelevant; it doesn't even matter if 1.5 fields occur multiple times. Thus, the invocation 1.6 \f(CWcut -c 5-8,1,4-6\fP outputs the characters number 1.7 -1, 4, 5, 6, 7, and 8 in exactly this order. The 1.8 +1, 4, 5, 6, 7, and 8 in ascending order. The 1.9 selection specification resembles mathematical set theory: Each 1.10 specified field is part of the solution set. The fields in the 1.11 solution set are always in the same order as in the input. To 1.12 @@ -472,7 +472,7 @@ 1.13 It is noteworthy that the GNU coreutils in all versions 1.14 describe the performed action as a removal of parts of the 1.15 input, although the user clearly selects the parts that then 1.16 -consistute the output. Probably the words ``cut out'' are too 1.17 +constitute the output. Probably the words ``cut out'' are too 1.18 misleading. HP-UX tried to be more clear. 1.19 .PP 1.20 Different terms are also used for the part being