[SCM] live-manual branch, debian, updated. debian/3.0_a10-1-39-g216427c

[Ben Armstrong]

The following commit has been merged in the debian branch:
commit 58b7edff5d07c24f40e14a267850d6e39232c14d
Author: Ben Armstrong <synrg at debian.org>
Date:   Fri Mar 23 11:42:59 2012 -0300

    Minor fixes & clarification in persistence section.

diff --git a/manual/en/user_customization-runtime.ssi b/manual/en/user_customization-runtime.ssi
index cf49339..9ee889b 100644
--- a/manual/en/user_customization-runtime.ssi
+++ b/manual/en/user_customization-runtime.ssi
@@ -102,7 +102,7 @@ _* a partition, identified by its GPT name.
 
 _* a filesystem, identified by its filesystem label.
 
-_* a image/archive file located on the root of any readable filesystem (even an NTFS partition of a foreign OS), identified by its file name. In this case the file name must also use the containing filesystem as the file extension, e.g. "<label>.ext3".
+_* an image/archive file located on the root of any readable filesystem (even an NTFS partition of a foreign OS), identified by its file name. In this case the file name must also use the containing filesystem as the file extension, e.g. "<label>.ext3".
 
 It is possible to restrict which types of persistent volumes to use by specifying certain boot parameters described in the live-boot(7) man page. The "identifying labels" referred to above can be any of the following:
 
@@ -166,7 +166,7 @@ Several different custom overlay volumes (with their own #{live.persist}# files)
 
 3~ Snapshots
 
-Snapshots are collections of files and directories which are not mounted while running but which are copied from a persistent volume to the system (tmpfs) at boot and which are resynced at reboot/shutdown of the system. The volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive named #{live-sn.cpio.gz}#. A power interruption during run time could lead to data loss, hence a tool invoked #{live-snapshot --refresh}# could be called to sync important changes. This type of persistence, since it does not write continuously to the persistent media, is the most flash-based device friendly and the fastest of all the persistence systems, but it occupies as much RAM as the size of the uncompressed snapshot.
+Snapshots are collections of files and directories which are not mounted while running but which are copied from a persistent volume to the system (tmpfs) at boot and which are resynced at reboot/shutdown of the system. The volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive named #{live-sn.cpio.gz}#. A power interruption during run time could lead to data loss, hence, if you have important changes, invoke #{live-snapshot --refresh}# as often as needed. This type of persistence, since it does not write continuously to the persistent media, is the most flash-based device friendly and the fastest of all the persistence systems, but it occupies as much RAM as the size of the uncompressed snapshot.
 
 A /home version of snapshot exists too and its label is #{home-sn.*}#; it works the same as the main snapshot but it is only applied to /home.
 

-- 
live-manual