about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2018-08-12 10:38:23 -0700
committerKartik Agaram <vc@akkartik.com>2018-08-12 10:38:23 -0700
commit63cf01588d4b1cbefdd9f22f94a144de0a84806b (patch)
treebd043478a8457c29e8dbeda95f06b5a0b2f7b7bc
parent76aace4625d4a2e0e1614acd0bea646f6db0f606 (diff)
downloadmu-63cf01588d4b1cbefdd9f22f94a144de0a84806b.tar.gz
4506
-rw-r--r--subx/Readme.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/subx/Readme.md b/subx/Readme.md
index 488e249a..cf279f32 100644
--- a/subx/Readme.md
+++ b/subx/Readme.md
@@ -27,7 +27,7 @@ b9/copy 1/imm32
 ```
 
 Notice that a single instruction, say 'copy', maps to multiple opcodes.
-That's just the tip of the iceberg of complexity that Assembly Languages deal
+That's just the tip of the iceberg of complexity that Assembly languages deal
 with.
 
 SubX doesn't shield the programmer from these details. Words always contain
@@ -48,7 +48,7 @@ into a larger toolchain, to be a back-end for a compiler. Their output is in
 turn often passed to other tools like a linker. The formats that all these
 tools use to talk to each other have grown increasingly complex in the face of
 decades of evolution, usage and backwards-compatibility constraints. All these
-considerations add to the burden of the Assembler developer. Building the
+considerations add to the burden of the assembler developer. Building the
 assembler in a high-level language helps face up to them.
 
 Assemblers _do_ often accept a far simpler language, just a file format