summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorSteve Kemp <steve@steve.org.uk>2016-04-24 05:35:22 +0300
committerSteve Kemp <steve@steve.org.uk>2016-04-24 05:35:22 +0300
commit89c2b36aaa3478fc0ad3742cddf66c2abae01b7c (patch)
tree54bd7b3dcd14ff6942386b5e7db19493d1133cf4 /README.md
parent0f443fc795832b5d3a5b9bd134ce36799caea843 (diff)
parenta091630ee5c4851ef849b5f2642d156558ea22a2 (diff)
Merge pull request #1 from ivuk/fix-typo-readme
Fix typos in README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index b02071d..5e43abf 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ Install the '`byteback`' package on the server, along with its dependencies.
You then need to perform the following local setup on the server, which can securely handle backups for multiple clients. You need a dedicated user (which is usually called 'byteback') with a home directory on a btrfs filesystem. You will need to mount the filesystem with the '`user_subvol_rm_allowed`' flag to enable pruning to work (or run that part as root).
-The following commands are appropriate for a Debian system, you might need to alter it for other Linux distributions, or if you are not using LVM for your discs:
+The following commands are appropriate for a Debian system, you might need to alter them for other Linux distributions, or if you are not using LVM for your discs:
#
# Create a dedicated UNIX user which will store everyone's backups, and
@@ -60,7 +60,7 @@ This is now documented in the manpage for byteback-backup(1).
Viewing and restoring backups
-----------------------------
-This is now documented in the manapge for byteback-restore(1).
+This is now documented in the manpage for byteback-restore(1).
The trust model