diff --git a/ivlpp/ivlpp.txt b/ivlpp/ivlpp.txt
index fe6071f53..a95d05126 100644
--- a/ivlpp/ivlpp.txt
+++ b/ivlpp/ivlpp.txt
@@ -95,7 +95,7 @@ keys, with their corresponding values, are:
       This is exactly the same as the "-Dname=<value>" described above.
 
    I:<dir>
-      This is exctly the same as "-I<dir>".
+      This is exactly the same as "-I<dir>".
 
    relative include:<flag>
       The <flag> can be "true" or "false". This enables "relative
diff --git a/tgt-vvp/README.txt b/tgt-vvp/README.txt
index 4242b1b09..f07323021 100644
--- a/tgt-vvp/README.txt
+++ b/tgt-vvp/README.txt
@@ -3,7 +3,7 @@ THE VVP TARGET
 
 SYMBOL NAME CONVENTIONS
 
-There are some naming conventions that the vp target uses for
+There are some naming conventions that the vvp target uses for
 generating symbol names.
 
 * wires and regs
@@ -30,4 +30,4 @@ the drivers are first fed into a resolver (or a tree of resolvers) to
 form a single output that is the nexus.
 
 The nexus, then, feeds its output to the inputs of other gates, or to
-the .net objects in the design.
\ No newline at end of file
+the .net objects in the design.
diff --git a/vvp/README.txt b/vvp/README.txt
index 27827d9eb..b1a98768d 100644
--- a/vvp/README.txt
+++ b/vvp/README.txt
@@ -218,8 +218,8 @@ only.
 
 The function of a UDP is defined via a table.  The rows of the table
 are strings which describe input states or edges, and the new output
-state.	Combinatorial UDPs require one character for each input, and
-one character at the end for the output state.	Sequential UDPs need
+state.  Combinatorial UDPs require one character for each input, and
+one character at the end for the output state.  Sequential UDPs need
 an additional char for the current state, which is the first char of
 the row.
 
@@ -227,7 +227,7 @@ Any input transition or the new state must match at most one row (or
 all matches must provide the same output state).  If no row matches,
 the output becomes 1'bx.
 
-The output state can be specified as "0", "1", or "x".	Sequential
+The output state can be specified as "0", "1", or "x".  Sequential
 UDPs may also have "-": no change.
 
 An input or current output state can be
@@ -256,7 +256,7 @@ A combinatorial UDP is defined like this:
 	<type> .udp/comb "<name>", <number>, "<row0>", "<row1>", ... ;
 
 <type> is a label that identifies the UDP.  <number> is the number of
-inputs.	 "<name>" is there for public identification.  Sequential UDPs
+inputs.  "<name>" is there for public identification.  Sequential UDPs
 need an additional initialization value:
 
 	<type> .udp/sequ "<name>", <number>, <init>, "<row0>", "<row1>", ... ;
@@ -535,8 +535,8 @@ implicit from these numbers. The <symbol> is then the input source.
 
 SUBSTITUTION STATEMENTS:
 
-The substition statement doesn't have a direct analog in Verilog, it
-only turns up in synthesis. It is a sorthand for forms like this:
+The substitution statement doesn't have a direct analog in Verilog, it
+only turns up in synthesis. It is a shorthand for forms like this:
 
    foo = <a>;
    foo[n] = <s>;
diff --git a/vvp/opcodes.txt b/vvp/opcodes.txt
index bef0c887b..97ae6100f 100644
--- a/vvp/opcodes.txt
+++ b/vvp/opcodes.txt
@@ -118,7 +118,7 @@ event control registers to determine when to perform the assign.
 %evctl is used to set the event control information.
 
 * %assign/v0 <var-label>, <delay>, <bit> (XXXX Old description)
-* %assign/v0/d <var-label>, <delayx>, <bit> (XXXX Old description
+* %assign/v0/d <var-label>, <delayx>, <bit> (XXXX Old description)
 * %assign/v0/e <var-label>, <bit> (XXXX Old description)
 
 The %assign/v0 instruction is a vector version of non-blocking
@@ -142,8 +142,8 @@ assignments. For blocking assignments, see %set/v.
 * %assign/vec4/d <var-label>, <delayx>
 * %assign/vec4/e <var-label>
 
-The %assign/vec4 instruction if a vec4 version of non-blocking
-assignment, The <delay> is the number lf clock ticks in the future
+The %assign/vec4 instruction is a vec4 version of non-blocking
+assignment. The <delay> is the number of clock ticks in the future
 where the assignment should schedule, and the value to assign is
 pulled from the vec4 stack.
 
@@ -536,7 +536,7 @@ part comes from the width of the popped value, and the <off> is an
 index register that contains the canonical offset where the value
 sets written.
 
-The %foce/vec4/off instruction will test the value if flags[4], and if
+The %force/vec4/off instruction will test the value of flags[4], and if
 it is 1, will suppress the actual assignment. This is intended to help
 with detection of invalid index expressions.