svn commit: r43242 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs

[Warren Block]

On Mon, 25 Nov 2013, Benjamin Kaduk wrote:

> On Mon, 25 Nov 2013, Warren Block wrote:
>
>> Author: wblock
>> Date: Mon Nov 25 05:58:08 2013
>> New Revision: 43242
>> URL: http://svnweb.freebsd.org/changeset/doc/43242
>> 
>> Log:
>>  Edits for clarity and simplicity.
>> 
>> Modified: 
>> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
>> ==============================================================================
>> --- 
>> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml 
>> Mon Nov 25 04:36:45 2013	(r43241)
>> +++ 
>> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml 
>> Mon Nov 25 05:58:08 2013	(r43242)
>> @@ -732,10 +732,10 @@ History for 'tank':
>> 2013-02-27.18:51:13 [internal create txg:55] dataset = 39
>> 2013-02-27.18:51:18 zfs create tank/backup</screen>
>> 
>> -      <para>The other more detailed history display can be invoked by
>> -	using the <literal>-l</literal> command.  This will show the
>> -	log records in long format, which includes more information
>> -	like the user name who issued the command and the hostname on
>> +      <para>A more-detailed history is invoked by
>
> I do not think that "invoked" is quite the right word here; we are not 
> calling upon the history, but rather printing it.

Agreed, and that sentence can be simplified also.

>> +	adding <literal>-l</literal>.
>> +	Log records are shown in long format, including information
>> +	like the name of the user who issued the command and the hostname on
>> 	which the change was made.</para>
>>
>>       <screen>&prompt.root; <userinput>zpool history -l</userinput>
>> @@ -842,55 +840,53 @@ data                      288G  1.53T
>>     <sect2 xml:id="zfs-zfs-create">
>>       <title>Creating & Destroying Datasets</title>
>> 
>> -      <para>Unlike with traditional disks and volume managers, space
>> -	in <acronym>ZFS</acronym> is not preallocated, allowing
>> -	additional file systems to be created at any time.  With
>> -	traditional file systems, once all of the space was
>> -	partitioned and assigned to a file system, there was no way to
>> +      <para>Unlike traditional disks and volume managers, space
>> +	in <acronym>ZFS</acronym> is not preallocated.
>> +	Wtraditional file systems, once all of the space was
>
> typo?

Wwhere?  :)

>> +	partitioned and assigned, there was no way to
>> 	add an additional file system without adding a new disk.
>> @@ -1209,65 +1201,59 @@ tank    custom:costcenter  -
>>       <para>When enabled,
>> 	<link linkend="zfs-term-deduplication">Deduplication</link>
>> 	uses the checksum of each block to detect duplicate blocks.
>> +	When a new block is a duplicate of an existing block,
>> +	<acronym>ZFS</acronym> writes an additional reference to
>> +	the existing data instead of the whole duplicate block.  This can 
>> offer
>> +	tremendous space savings if the data contains many discreet
>
> s/discreet/discrete/

Yes, but the usage is questionable anyway.  Rewritten.