aboutsummaryrefslogtreecommitdiff
path: root/docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt')
-rw-r--r--docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt b/docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt
index 1c725f5aa715..81ca53919d42 100644
--- a/docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt
+++ b/docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt
@@ -60,11 +60,11 @@ Understood. :)
Yup, I think that this makes a lot of sense. I am still intrigued,
however, by the prospect of a minimally allocated VM representation... I
-think that it could have definate advantages for certain applications
+think that it could have definite advantages for certain applications
(think very small machines, like PDAs). I don't, however, think that our
initial implementations should focus on this. :)
-Here are some other auxilliary goals that I think we should consider:
+Here are some other auxiliary goals that I think we should consider:
1. Primary goal: Support a high performance dynamic compilation
system. This means that we have an "ideal" division of labor between