about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2021-07-03 10:44:05 -0700
committerKartik K. Agaram <vc@akkartik.com>2021-07-03 10:44:05 -0700
commita745749382b898da1fbd1e23949a9edcf703d917 (patch)
tree4fb94c701b95d7f0214554a39d83e0bb56d431b0
parentbd538804dba0904c8951a75767d00e7a71834f5a (diff)
downloadmu-a745749382b898da1fbd1e23949a9edcf703d917.tar.gz
.
-rw-r--r--shell/README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/shell/README.md b/shell/README.md
index d0dd61ec..920e6aec 100644
--- a/shell/README.md
+++ b/shell/README.md
@@ -41,15 +41,15 @@ Currently runs a tiny dialect of Lisp. Steps to run it from the top-level:
   results. Hit `ctrl-m` to focus on the `...` after a run, and browse how the
   _trace_ of how the results were computed. [Here's a 2-minute demo](https://archive.org/details/akkartik-mu-2021-05-31).
 
-3. If your Qemu installation supports them, an `-accel` arguments
+3. If your Qemu installation supports them, an `-accel` argument
    will speed up emulation. Try `-accel help` to list your options.
 
   Once you select an accelerator, I recommend also adjusting the `responsiveness`
   mask in shell/evaluate.mu, which controls how frequently the fake screen
   updates within the REPL. Smaller values will seem more responsive, larger
-  values will leave more time to run your programs. I like to see the screen
-  update about once a second. Some suggested values depending on how fast your
-  Qemu is running:
+  values will run your programs faster. I like to see the fake screen update
+  about once a second. Some suggested values depending on how fast your Qemu
+  is running:
 
   - `-accel kvm` on a T420s running Linux: `0xffff/responsiveness=64k`
   - `-accel tcg` on a 2019 Mac: `0xfff/responsiveness=4k`