aboutsummaryrefslogtreecommitdiffstats
path: root/include/mips_mem.h
diff options
context:
space:
mode:
Diffstat (limited to 'include/mips_mem.h')
-rw-r--r--include/mips_mem.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/mips_mem.h b/include/mips_mem.h
index 97724ff..9a62422 100644
--- a/include/mips_mem.h
+++ b/include/mips_mem.h
@@ -103,7 +103,7 @@ mips_error mips_mem_write(
really know what is being released (it could be memory, it could
be file handles), and shouldn't care. Calling mips_mem_free on an
empty (zero) handle is legal. Calling mips_mem_free twice on the
- same handle is illegal, and the resulting behaviour is undefined
+ same non-empty handle is illegal, and the resulting behaviour is undefined
(most likely a crash).
A pattern that can be useful is: