From d478522d603a6257f83759d4713f222355db4af9 Mon Sep 17 00:00:00 2001
From: Aryadev Chavali <aryadev@aryadevchavali.com>
Date: Tue, 9 Apr 2024 21:23:54 +0630
Subject: Some rewording of spec.org

---
 spec.org | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/spec.org b/spec.org
index b639162..4a995d2 100644
--- a/spec.org
+++ b/spec.org
@@ -6,8 +6,8 @@
 * WIP Data types
 There are 3 main data types of the virtual machine.  They are all
 unsigned.  There exist signed versions of these data types, though
-there is no difference in terms of bytecode between them.  For an
-unsigned type <T> the signed version is simply S_<T>.
+there is no difference (internally) between them.  For an unsigned
+type <T> the signed version is simply S_<T>.
 |-------+------|
 | Name  | Bits |
 |-------+------|
@@ -29,9 +29,9 @@ many of A can I fit in B".
 |-------+------+-------+------|
 * WIP Instructions
 An instruction for the virtual machine is composed of an *opcode* and,
-potentially, an *operand*.  An /opcode/ represents the behaviour of
-the instruction i.e. what _is_ the instruction.  The /operand/ is a
-datum of one of the /data types/ described previously.
+potentially, an *operand*.  The /opcode/ represents the behaviour of
+the instruction i.e. what _is_ the instruction.  The /operand/ is an
+element of one of the /data types/ described previously.
 
 Some instructions do have /operands/ while others do not.  The former
 type of instructions are called *UNIT* instructions while the latter
-- 
cgit v1.2.3-13-gbd6f