Improve etckeeper description

1 files changed, 9 insertions, 12 deletions

diff --git a/fripost-docs.org b/fripost-docs.org
index 38e3a27..4eb2f5a 100644
--- a/fripost-docs.org
+++ b/fripost-docs.org
@@ -1163,23 +1163,20 @@ To get commit access, contact admin@fripost.org with your request.
 
 ** Use etckeeper
 
-We keep /etc in a git repository using the tool etckeeper.
+We keep /etc in a git repository using the tool etckeeper. This makes it
+possible to use standard git commands in /etc, e.g. `git log'. `etckeeper' has
+the benefit of keeping track of file permissions, which git by itself will not.
 
-This means that every time you make changes to any files in /etc, you are
-expected to commit them using a descriptive commit message.  Please add a
-signature (initials or your username) since all commits will be made as root.
+Every time you make changes to any files in /etc, you are encouraged to commit
+them using a descriptive commit message.
 
-$ etckeeper commit "postfix: enable to relay messages to remote hosts via smtp /skangas"
+$ etckeeper commit "postfix: relay messages to remote hosts via smtp"
 
-If you do not commit your changes, the next system upgrade will fail and
-whoever makes the upgrade will have to commit your changes for you.  They may
-have to guess as to why you made your changes.  Please do not put your
+If you do not commit your changes, they will be automatically committed.  This
+is not ideal, since this means other administrators might have to guess as to
+why changes were being made and by whom.  Please try to avoid putting your
 co-administrators in this uncomfortable position.
 
-It is also possible to use simple git commands in /etc, e.g. `git log'.
-`etckeeper' has the benefit of keeping track of file permissions, which git
-by itself will not.
-
 ** Use Cluster SSH
 
 This pretty much sums it up: