Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fix trivial errors in eep-0036

  • Loading branch information...
commit bdeca9bfb339a7d99eac05fa745202d8b4342ea0 1 parent 289ca8d
@tuncer tuncer authored RaimoNiskanen committed
Showing with 3 additions and 3 deletions.
  1. +3 −3 eeps/eep-0036.md
View
6 eeps/eep-0036.md
@@ -210,7 +210,7 @@ dictionary. When an exception occurs, the line number can be
retrieved and presented.
One problem with this approach is that the test suite will run slower,
-which can cause test cases to fail if timeouts expires in the system
+which can cause test cases to fail if timeouts expire in the system
being tested. Another problem is that by default the parse transform
is only run on the test modules themselves, and therefore exceptions
that occur in other parts of the code (support libraries for testing
@@ -253,7 +253,7 @@ and ETS table. Therefore, the 10 percent increase of the code size
most users, but the benefit of having line number information is
potentially huge.
-* Newcomers to Erlang have the best the need for line number information
+* Newcomers to Erlang have the most need for line number information
and they should get it without giving any special option. If an option
is needed, questions to the mailing lists about how to find from which
source line an exception was caused will continue to waste time.
@@ -292,7 +292,7 @@ Here is an overview of the implementation:
The BEAM compiler inserts a `line` instruction before every construct
that may generate an exception and before every call that will be
included in the stacktrace. (Local tail-recursive calls need no `line`
-instruction, but external tail-recursive calls need a `lien`
+instruction, but external tail-recursive calls need a `line`
instruction because they may be calls to BIFs.)
The `line` instruction has a single operand, an index into a line
Please sign in to comment.
Something went wrong with that request. Please try again.