README: language proofreading
This commit is contained in:
parent
e32ec08832
commit
7c90366688
16
README.md
16
README.md
|
@ -22,7 +22,7 @@ You need some packages as dependencies:
|
|||
|
||||
# Configuration
|
||||
|
||||
The configuration is done in two part, system wide to configure the
|
||||
The configuration is done in two parts, system wide to configure the
|
||||
**impermanence** service that will mount the memory filesystem and
|
||||
populate it.
|
||||
|
||||
|
@ -74,7 +74,7 @@ directories:
|
|||
The restart parameter to the service will unmount the device and
|
||||
recreate it, allowing a fresh restart.
|
||||
|
||||
This is a bad idea to use it while the user is connected.
|
||||
It is a bad idea to use while the user is connected.
|
||||
|
||||
## start
|
||||
|
||||
|
@ -84,7 +84,7 @@ Creates and populates the home filesystem.
|
|||
|
||||
Umount the home filesystem.
|
||||
|
||||
This is a bad idea to use it while the user is connected.
|
||||
It is a bad idea to use while the user is connected.
|
||||
|
||||
## status
|
||||
|
||||
|
@ -102,13 +102,13 @@ Using `find` it's easy to scan all the files from the ramdisk
|
|||
(excluding the symbolic links) and order them by date of change.
|
||||
|
||||
This can be done with `find -x ~/ -type f -exec ls -altr {} +`, the
|
||||
last files are the most recently modified one.
|
||||
last files are the most recently modified.
|
||||
|
||||
## Beware file loss
|
||||
|
||||
When using this way of life, you need to remember every changes
|
||||
that doesn't belong in the persistent areas will be lost. For
|
||||
example, this will happen for every new files or directories at the
|
||||
When using this way of life, you need to remember all changes
|
||||
that don't belong in the persistent areas will be lost. For
|
||||
example, this will happen for all new files or directories at the
|
||||
root of your $HOME.
|
||||
|
||||
Impermanence requires the user to be aware of what files must stay
|
||||
|
@ -135,7 +135,7 @@ include, you could rather list only a subset of those, which will
|
|||
make a long list and require a few guess&fix sessions to get the
|
||||
things right.
|
||||
|
||||
The less the directories are at the top level, the more you will
|
||||
The less directories are at the top level, the more you will
|
||||
pinpoint the exact configuration you want to keep over time.
|
||||
|
||||
## Restarting impermanence
|
||||
|
|
Loading…
Reference in New Issue