[SCM] Debian Live manual branch, master, updated. d873b4e10a17d862de72c5a3f9c8c204a24eef4a

[Marco Amadori]

The following commit has been merged in the master branch:
commit d873b4e10a17d862de72c5a3f9c8c204a24eef4a
Author: Marco Amadori <marco.amadori at gmail.com>
Date:   Wed Nov 26 20:26:38 2008 +0100

    Fixed some grammar, typo and syntax errors.
    
    * Thanks for Ivan Shmakov <oneingray at gmail.com> for the corrections.

diff --git a/xml/chapters/live-environment.xml b/xml/chapters/live-environment.xml
index f91416b..4013779 100644
--- a/xml/chapters/live-environment.xml
+++ b/xml/chapters/live-environment.xml
@@ -89,7 +89,7 @@ $ mkfs.ext2 -F live-rw
 </section>
 
 <section><title>Snapshots</title>
-<para>Snapshots are collection of files and directories which are not mounted while running but which are copied from a persistent device to the system (tmpfs) at boot and which are resynced at reboot/shutdown of the system. The content of a snapshot could reside on a partition or an image file (like the above mentioned types) labeled <command>live-sn</command>, but it defaults as a  simple cpio archive named <command>live-sn.cpio.gz</command>. As above at boot time, the block devices connected to the system are traversed to see it a suche named partition or file could be found. A power interruption during runtime could mean data lost hence a tool invoked  <command>live-snapshot --refresh</command> could be called to sync important changes. This type of persistence since no not write continuosly to the persistent media is the most flash-based device friendly and the fastest of all the persistence systems.</para>
+<para>Snapshots are collection of files and directories which are not mounted while running but which are copied from a persistent device to the system (tmpfs) at boot and which are resynced at reboot/shutdown of the system. The content of a snapshot could reside on a partition or an image file (like the above mentioned types) labeled <command>live-sn</command>, but it defaults to a simple cpio archive named <command>live-sn.cpio.gz</command>. As above at boot time, the block devices connected to the system are traversed to see if a partition or a file named like that could be found. A power interruption during runtime could lead to data lost hence a tool invoked  <command>live-snapshot --refresh</command> could be called to sync important changes. This type of persistence since it does not write continuosly to the persistent media is the most flash-based device friendly and the fastest of all the persistence systems.</para>
 <para> A /home version of snapshot exists too and its label is <command>home-sn.*</command>; it works the same as the main snapshot but it is only applied to /home.</para>
 <para> All kind of snapshots cannot currently handle file deleting while full persistence and obviously home automounting could.</para>
 </section>

-- 
Debian Live manual