From ae971fbeb5062f76eb335dfb8da166f319854dfd Mon Sep 17 00:00:00 2001 From: Miklos Vajna Date: Sat, 5 Jan 2008 04:25:32 +0100 Subject: Fix two typo in README. Signed-off-by: Miklos Vajna --- README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README') diff --git a/README b/README index 5a81d98..2a44fab 100644 --- a/README +++ b/README @@ -46,7 +46,7 @@ storage, empty directories, and special files. git and mercurial have only limited tracking of file metadata, being able to track the executable bit, but not other permissions or owner info. So -file metadata storage is handled by `metastore`. Amoung other chores, +file metadata storage is handled by `metastore`. Among other chores, `etckeeper init` sets up a `pre-commit` hook that uses `metastore` to store metadata about file owners, permissions, and even extended attributes into a `/etc/.metadata` file. This metadata is stored in git along with @@ -176,7 +176,7 @@ Two blog posts provided inspiration for techniques used by etckeeper: [isisetup][2] has some of the same aims as etckeeper, however, unlike it, etckeeper does not aim to be a git porcelain with its own set of commands for manipulating the /etc repository. Instead, etckeeper provides a simple -setup procedure and hooks for setting up an /etc repsository, and then gets +setup procedure and hooks for setting up an /etc repository, and then gets out of your way; you manage the repository using regular git commands. [2]: http://www.isisetup.ch/ -- cgit v1.2.3