The wording's rather unclear on what 'nonfatal die' does. To avoid
arguing whether calling die is a 'failure', explicitly say that nonfatal
doesn't stop die or assert.
---
 pkg-mgr-commands.tex |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index 0278aec..b87bb49 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -16,8 +16,9 @@ The following commands affect this behaviour:
 \begin{description}
 \item[nonfatal] \featurelabel{nonfatal} Executes the remainder of its arguments as a command,
     preserving the exit status. If this results in a command being called that would normally abort
-    the build process due to a failure, instead a non-zero exit status shall be returned. Only in
-    EAPIs listed in table~\ref{tab:commands-die-table} as supporting \t{nonfatal}.
+    the build process due to a failure (but not due to an explicit \t{die} or \{assert} call),
+    instead a non-zero exit status shall be returned. Only in EAPIs listed in
+    table~\ref{tab:commands-die-table} as supporting \t{nonfatal}.
 \end{description}
 
 \begin{centertable}{EAPI Command Failure Behaviour} \label{tab:commands-die-table}
-- 
1.6.3.3