[SCM] live-manual branch, debian-next, updated. debian/3.0_a13-1-28-g4b83ef0

[chals]

The following commit has been merged in the debian-next branch:
commit fdbe1c219283a69fd87422b811b6ce45b1937d5e
Author: chals <chals at altorricon.com>
Date:   Fri Jul 20 15:24:14 2012 +0200

    Changing old 'Persistence Subtext' title to 'Using more than one persistence store' thanks to Ben Armstrong.

diff --git a/manual/en/user_customization-runtime.ssi b/manual/en/user_customization-runtime.ssi
index d8f8ffe..15a4ecf 100644
--- a/manual/en/user_customization-runtime.ssi
+++ b/manual/en/user_customization-runtime.ssi
@@ -164,6 +164,6 @@ Then we reboot. During the first boot the contents of #{/home}# and #{/var/cache
 
 Several different custom overlay volumes (with their own #{live-persistence.conf}# files) can be used at the same time, but if several volumes make the same directory persistent, only one of them will be used. If any two mounts are "nested" (i.e. one is a sub-directory of the other) the parent will be mounted before the child so no mount will be hidden by the other. Nested custom mounts are problematic if they are listed in the same #{live-persistence.conf}# file. See the live-persistence.conf(5) man page for how to handle that case if you really need it (hint: you usually don't).
 
-3~ Persistence SubText
+3~ Using more than one persistence store
 
-If a user would need multiple persistence storage of the same type for different locations or testing, such as #{persistence-nonwork}# and #{persistence-work}#, the boot parameter #{persistence-label}# used in conjunction with the boot parameter #{persistence}# will allow for multiple but unique persistence media. An example would be if a user wanted to use a persistence partition labeled #{persistence-subText}# they would use the boot parameters of: #{persistence}# #{persistence-label=subText}#.
+If a user would need multiple persistence store of the same type for different locations or testing, such as #{persistence-nonwork}# and #{persistence-work}#, the boot parameter #{persistence-label}# used in conjunction with the boot parameter #{persistence}# will allow for multiple but unique persistence media. An example would be if a user wanted to use a persistence partition labeled #{persistence-subText}# they would use the boot parameters of: #{persistence}# #{persistence-label=subText}#.

-- 
live-manual