summaryrefslogtreecommitdiffstats
path: root/wiki/src/contribute/design/persistence.mdwn
diff options
context:
space:
mode:
authorTails developers <amnesia@boum.org>2013-04-06 18:45:00 +0200
committerTails developers <amnesia@boum.org>2013-04-06 18:45:17 +0200
commitb2054e0471d445f29c9c1ab9c89f135318f492b1 (patch)
tree62eed4058a521e8f2c732d39f113d62d3291fd50 /wiki/src/contribute/design/persistence.mdwn
parentcdef7383ce4f8e2214c025d7b00ac43b72c564d0 (diff)
Language fixes.
Diffstat (limited to 'wiki/src/contribute/design/persistence.mdwn')
-rw-r--r--wiki/src/contribute/design/persistence.mdwn14
1 files changed, 7 insertions, 7 deletions
diff --git a/wiki/src/contribute/design/persistence.mdwn b/wiki/src/contribute/design/persistence.mdwn
index a239532..f00db9e 100644
--- a/wiki/src/contribute/design/persistence.mdwn
+++ b/wiki/src/contribute/design/persistence.mdwn
@@ -2,7 +2,7 @@ Data persistence is a somewhat tricky topic in a Live system context,
especially one explicitly designed to avoid leaving any trace of
its use.
-Some real-life usecases however require to setup some kind of data
+Some real-life usecases however require to set up some kind of data
persistence, which were then carefully introduced and supported.
[[!toc levels=4]]
@@ -149,7 +149,7 @@ User interface
### bootstrap persistent storage
A *Configure persistent storage* menu entry is the entry point to the
-*bootstrap persistent storage* UI. This UI allows the user to setup
+*bootstrap persistent storage* UI. This UI allows the user to set up
a persistent storage container in the free space left on the USB stick
by [[our USB installer|usb_installation]].
@@ -237,7 +237,7 @@ Persistence settings changes are taken into account at next boot.
the persistence partition is already mounted; or the user is
directly coming from bootstrap, and then we must mount the partition
ourselves
-* by default setup, setup a linkfiles-enabled persistent
+* by default, set up a linkfiles-enabled persistent
`${HOME}/dotfiles`, preconfigured to have its contents symlinked
into `$HOME`.
* apart of this, let's consider non-directories persistence an
@@ -277,8 +277,8 @@ we've written a graphical [[!tails_todo boot_menu]]:
supports *one* persistence container
* ask LUKS passphrase, deals with errors
* for a given persistent container, it's all or nothing: all bits of
- persistence configured in its `live.persist` are to be setup
-* runs `live-persist` to setup persistent data where it belong
+ persistence configured in its `live.persist` are to be set up
+* runs `live-persist` to set up persistent data where it belong
* pass information to the user session (at least
`tails-persistence-setup` needs information) through shell variables
set in `/var/lib/gdm3/tails.persistence`
@@ -296,7 +296,7 @@ backend / tails-greeter interface
0. For each such volume, `tails-greeter` asks the user to enter the
passphrase or to skip it, and tries to unlock. `tails-greeter`
deals with error catching, retrying, etc. as appropriate.
-0. `tails-greeter` asks `live-boot` to setup persistence (at least
+0. `tails-greeter` asks `live-boot` to set up persistence (at least
custom mounts and linkfiles), passing it the list of volumes that
were successfully unlocked.
@@ -335,7 +335,7 @@ passing to `tails-greeter`; . `live-persist` will support non-Tails
usecases on a best-effort basis, leaving room for improvement in case
other developers want to add support for their preferred usecases.
-### Asking live-persist to setup persistence
+### Asking live-persist to set up persistence
To start with, we've factored out only the custom mounts part from the
main `live-boot` script; it depends on factoring out other kinds of