Weaken my statement about needing a dependency injection mechanism a bit: an alternative mechanism for testing `libtock_core`'s system call error handling logic would be fine as well.
diff --git a/doc/DesignConsiderations.md b/doc/DesignConsiderations.md
index 7517a02..8e72eeb 100644
--- a/doc/DesignConsiderations.md
+++ b/doc/DesignConsiderations.md
@@ -72,8 +72,9 @@
Testing pieces of `libtock_core` against a fake kernel can be done using
dependency injection, but most dependency injection techniques have considerable
-code size and RAM usage costs. `libtock_core` needs a dependency injection
-technique that has minimal size impact.
+code size and RAM usage costs. `libtock_core` needs either a dependency
+injection technique that has minimal size impact or an alternative mechanism for
+testing `libtock_core`'s system call error handling logic.
## Support multiple asynchronous programming models.
