about summary refs log tree commit diff stats
path: root/mu.md
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2020-10-14 09:48:24 -0700
committerKartik Agaram <vc@akkartik.com>2020-10-14 09:48:24 -0700
commit8350faef52f410c50af259c80b143497ef8b659f (patch)
tree668ca847b5297345ecc9fe53b345c5e6ab10ccba /mu.md
parent4d60956b6f4ca56905c3833d802c5fc882a22ff0 (diff)
downloadmu-8350faef52f410c50af259c80b143497ef8b659f.tar.gz
7023
Diffstat (limited to 'mu.md')
-rw-r--r--mu.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/mu.md b/mu.md
index b3375062..ce09467e 100644
--- a/mu.md
+++ b/mu.md
@@ -25,13 +25,13 @@ Statements consist of 3 parts: the operation, optional _inouts_ and optional
 _outputs_. Outputs come before the operation name and `<-`.
 
 Outputs are always registers; memory locations that need to be modified are
-passed in by reference.
+passed in by reference in inouts.
 
 So Mu programmers need to make two new categories of decisions: whether to
 define variables in registers or memory, and whether to put variables to the
 left or right. There's always exactly one way to write any given operation. In
 return for this overhead you get a lightweight and future-proof stack. And Mu
-will provide good error message to support you.
+will provide good error messages to support you.
 
 Further down, this page enumerates all available primitives in Mu, and [a
 separate page](http://akkartik.github.io/mu/html/mu_instructions.html)