diff --git a/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md b/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md
index 5649586..8eb8519 100644
--- a/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md
+++ b/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md
@@ -126,7 +126,7 @@ Then I'd strongly suggest to start reading up on afl if you want to employ it wi
 
 ## Testing for bugs in your code
 
-By default AFL will identify segfaults and such but not vulnerabilities in your code. You can add extra assertions to be run only during the AFL test with:
+Please keep in mind that fuzzing is supposed to find the **unknown/unexpected** errors, not just the ones you are anticipating. Thus, whereever possible, err on the side of caution and consider all exceptions to be a failure state that will bite you in the butt once you ship.  That said, you can use this nice template to trigger a AFL "crash" condition:
 
 ```nim
 when defined(macosx) or defined(linux) or defined(freebsd) or
@@ -141,4 +141,4 @@ template AFLAssert*(cond: bool) =
       discard posix.kill(pid, posix.SIGABRT)
 ```
 
-Also add `-d:afl` to your nim.cfg to enable this.
+Then add `-d:afl` to your nim.cfg to enable this.
\ No newline at end of file