4185 New hash algorithm support

@@ -932,11 +932,11 @@
 
 .sp
 .ne 2
 .na
 \fB\fBchecksum\fR=\fBon\fR | \fBoff\fR | \fBfletcher2\fR | \fBfletcher4\fR |
-\fBsha256\fR | \fBnoparity\fR \fR
+\fBsha256\fR | \fBnoparity\fR | \fBsha512\fR | \fBskein\fR | \fBedonr\fR\fR
 .ad
 .sp .6
 .RS 4n
 Controls the checksum used to verify data integrity. The default value is
 \fBon\fR, which automatically selects an appropriate algorithm (currently,

@@ -945,10 +945,14 @@
 disables integrity but also disables maintaining parity for user data.  This
 setting is used internally by a dump device residing on a RAID-Z pool and should
 not be used by any other dataset. Disabling checksums is \fBNOT\fR a recommended
 practice.
 .sp
+The \fBsha512\fR, \fBskein\fR and \fBedonr\fR checksum algorithms require
+enabling the appropriate features on the pool. Please see
+\fBzpool-features(5)\fR for more information on these algorithms.
+.sp
 Changing this property affects only newly-written data.
 .RE
 
 .sp
 .ne 2

@@ -2860,11 +2864,11 @@
 .RS 4n
 Generate a deduplicated stream.  Blocks which would have been sent multiple
 times in the send stream will only be sent once.  The receiving system must
 also support this feature to recieve a deduplicated stream.  This flag can
 be used regardless of the dataset's \fBdedup\fR property, but performance
-will be much better if the filesystem uses a dedup-capable checksum (eg.
+will be much better if the filesystem uses a dedup-capable checksum (e.g.
 \fBsha256\fR).
 .RE
 
 .sp
 .ne 2