Give a brief explanation of why nasal demons are undesirable.

1 files changed, 1 insertions, 1 deletions

diff --git a/IncompletelySpecifiedBehavior.md b/IncompletelySpecifiedBehavior.md
index f577772..00ad302 100644
--- a/IncompletelySpecifiedBehavior.md
+++ b/IncompletelySpecifiedBehavior.md
@@ -4,7 +4,7 @@ WebAssembly is a sandboxed platform. Programs can't access data outside the sand
 
 Beyond that, it is desirable to minimize observable differences between implementations when practical, so that programs don't inadvertently become dependent on any particular implementation's behavior. However, in some areas, performance concerns make this prohibitively expensive, so some compromises are made.
 
-Also, there is a general preference against [nasal demons](https://en.wikipedia.org/w/index.php?title=Nasal_demons). WebAssembly generally prefers to [trap](AstSemantics.md) in many situations. Otherwise, it is generally preferred to have a specific set of possible behaviors rather than unconstrained behavior. And presently, WebAssembly has no nasal demons.
+Also, there is a general preference against [nasal demons](https://en.wikipedia.org/w/index.php?title=Nasal_demons), since they are an extreme on the spectrum of observable differences, and since they make it difficult to reason about what state an application might be in. WebAssembly usually prefers to [trap](AstSemantics.md). Otherwise, it is generally preferred to have a specific set of possible behaviors rather than nasal demons. And presently, WebAssembly has no nasal demons.
 
 The following is a list of the places where the WebAssembly specification currently admits or is expected to admit multiple possible behaviors.