remote: guard against symlinks in earlier path components

[safcm/safcm.git] / README.adoc

diff --git a/README.adoc b/README.adoc
index 94f279248a4c2aa7fb3239e1ce9f93233a866fe7..6a2b108d94cfa8f4242483a38eb890a9f97c40b0 100644 (file)
--- a/README.adoc
+++ b/README.adoc
@@ -8,7 +8,7 @@ under GPLv3+. It is:
 - *configuration management*: sync files, packages, services and run commands
   on remote hosts
 
-The goal is that even unexperienced users (with safcm or configuration
+The goal is that even inexperienced users (with safcm or configuration
 management in general) should be able to apply configuration with safcm
 quickly. This means all key concepts of safcm must be easy to grasp and for
 each task there should be one obvious way.
@@ -102,10 +102,10 @@ future, others are due to the design of safcm.
   file and execute or source it as a workaround.
 
 - Permissions of existing files and directories will be overwritten with the
-  default (root/root, 0644 for files, 0755 for directories) unless manually
-  configured via `permissions.yaml`. This includes important paths like
-  `/root` which often have strict permissions by default, so carefully check
-  the output for unwanted changes.
+  default (root/root or root/wheel, 0644 for files, 0755 for directories)
+  unless manually configured via `permissions.yaml`. This includes important
+  paths like `/root` which often have strict permissions by default, so
+  carefully check the output for unwanted changes.
 
 - The full file content of all files is sent to the remote during
   synchronization. This makes it impractical to synchronize large files with