about summary refs log tree commit diff stats
diff options
context:
space:
mode:
-rw-r--r--README.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/README.md b/README.md
index f2b07e56..f806ea9e 100644
--- a/README.md
+++ b/README.md
@@ -18,10 +18,10 @@ Running the code you want to run, and nothing else.
 
 [![Build Status](https://api.travis-ci.org/akkartik/mu.svg?branch=master)](https://travis-ci.org/akkartik/mu)
 
-The Mu translator is built up from machine code and requires just a Unix-like
-kernel and nothing else. You can also bootstrap it from C++. Both C++ and
+Mu requires just a Unix-like OS and nothing else. The Mu translator is built
+up from machine code. You can also bootstrap it from C++. Both C++ and
 self-hosted versions emit identical binaries. The generated binaries require
-just a Unix-like kernel and nothing else.
+just a Unix-like kernel and nothing else. ([More details.](http://akkartik.name/akkartik-convivial-20200315.pdf))
 
 ## Goals
 
@@ -64,13 +64,13 @@ checks. Here's the program we translated above:
 
 <img alt='ex2.mu' src='html/ex2.mu.png'>
 
-There are no expressions, only statements that operate on variables. Most
-statements in Mu translate to a single machine code instruction. Variables
-reside in memory by default. Programs must specify registers when they want to
-use them. Functions must return results in registers. Execution begins at the
-function `main`, which always returns its result in register `ebx`. [This paper](http://akkartik.name/akkartik-convivial-20200315.pdf)
-has more details, and there's a [summary](mu_summary) of all supported
-instructions.
+There are no expressions; functions consist of only statements that operate on
+variables. Most statements in Mu translate to [a single machine code instruction](http://akkartik.github.io/mu/html/mu_instructions.html).
+Variables reside in memory by default. Programs must specify registers when
+they want to use them. Functions must return results in registers. Execution
+begins at the function `main`, which always returns its result in register
+`ebx`. [This paper](http://akkartik.name/akkartik-convivial-20200315.pdf) has
+more details, and there's a [summary](mu_summary) of all supported instructions.
 
 ## SubX