os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove some extraneous uses of "the".

Browse source
This commit is contained in:
Warren Block 2012-09-11 17:53:02 +00:00
parent 7881c8e7a8
commit 549ad2af05
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=39521
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml
View file

@ -203,7 +203,7 @@ vfs.zfs.vdev.cache.size="5M"</programlisting>
<screen>&prompt.root; <userinput>zpool create example /dev/da0</userinput></screen>
<para>To view the new pool, review the output of the
<para>To view the new pool, review the output of
<command>df</command>:</para>
<screen>&prompt.root; <userinput>df</userinput>
@ -291,7 +291,7 @@ example/compressed on /example/compressed (zfs, local)</screen>
&prompt.root; <userinput>zfs set copies=2 example/data</userinput></screen>
<para>It is now possible to see the data and space utilization
by issuing the <command>df</command> again:</para>
by issuing <command>df</command> again:</para>
<screen>&prompt.root; <userinput>df</userinput>
Filesystem 1K-blocks Used Avail Capacity Mounted on
@ -304,7 +304,7 @@ example/data 17547008 0 17547008 0% /example/data</screen>
<para>Notice that each file system on the pool has the same
amount of available space. This is the reason for using
the <command>df</command> through these examples, to show
<command>df</command> through these examples, to show
that the file systems are using only the amount of space
they need and will all draw from the same pool.
The <acronym>ZFS</acronym> file system does away with concepts
@ -351,7 +351,7 @@ example/data 17547008 0 17547008 0% /example/data</screen>
&man.df.1; commands as before. More disk devices may have
been allocated by adding them to the end of the list above.
Make a new file system in the pool, called
<literal>home</literal> where user files will eventually be
<literal>home</literal>, where user files will eventually be
placed:</para>
<screen>&prompt.root; <userinput>zfs create storage/home</userinput></screen>
@ -391,7 +391,7 @@ example/data 17547008 0 17547008 0% /example/data</screen>
<screen>&prompt.root; <userinput>zfs rollback storage/home@08-30-08</userinput></screen>
<para>To get a list of all available snapshots, run the
<para>To get a list of all available snapshots, run
<command>ls</command> in the file system's
<filename class="directory">.zfs/snapshot</filename>
directory. For example, to see the previously taken
@ -406,7 +406,7 @@ example/data 17547008 0 17547008 0% /example/data</screen>
<screen>&prompt.root; <userinput>zfs destroy storage/home@08-30-08</userinput></screen>
<para>There is no reason, after all of this testing, we should
<para>After all of this testing, there is no reason we should
keep <filename class="directory">/storage/home</filename>
around in its present state. Make it the real
<filename class="directory">/home</filename> file