Consistently use parsable instead of parseable

This is a purely cosmetical change, to consistently prefer one of
two (both acceptable) choises for the word parsable in documentation and
code. I don't really care which to use, but acording to wiktionary
https://en.wiktionary.org/wiki/parsable#English parsable is preferred.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #4682
This commit is contained in:
Christer Ekholm
2016-05-23 19:20:42 +02:00
committed by Brian Behlendorf
parent 9baaa7deae
commit 3491d6eb06
4 changed files with 7 additions and 7 deletions
+2 -2
View File
@@ -1125,7 +1125,7 @@ Scripted mode. Do not display headers, and separate fields by a single tab inste
\fB\fB-p\fR\fR
.ad
.RS 6n
Display numbers in parseable (exact) values.
Display numbers in parsable (exact) values.
.RE
.sp
@@ -1570,7 +1570,7 @@ Display real paths for vdevs resolving all symbolic links. This can be used to l
\fB\fB-p\fR\fR
.ad
.RS 12n
Display numbers in parseable (exact) values. Time values are in nanoseconds.
Display numbers in parsable (exact) values. Time values are in nanoseconds.
.RE
.sp