Clarify documentation on command hooks order of execution (#1099).

NEWS

@@ -1,4 +1,5 @@
 2.0.7.dev0
+ * #1099: Clarify documentation on command hooks order of execution.
  * #1100: Fix a bug in which "borg --version" failing isn't considered a "fail" state in a command
    hook.
 

docs/how-to/add-preparation-and-cleanup-steps-to-backups.md

@@ -130,6 +130,10 @@ have a chance to run. Whereas the `after: error` hook doesn't run until all
 actions for—and repositories in—a configuration file have had a chance to
 execute.
 
+And if there are multiple hooks defined for a particular step (e.g. `before:
+action` for `create`), then those hooks are run in the order they're defined in
+configuration.
+
 
 ### Deprecated command hooks