Tweak README

README.md

@@ -39,7 +39,7 @@ KeyError(:b)
 ### Error trace
 
 Consider an example where an error "bubbles up" from a deep stack of function
-call:
+calls:
 
 ```JULIA
 julia> using Try
@@ -51,8 +51,8 @@ julia> f2(x) = f1(x);
 julia> f3(x) = f2(x);
 ```
 
-Since Try.jl represents an error as simple Julia value, there is no information
-on the source this error:
+Since Try.jl represents an error simply as a Julia value, there is no
+information on the source this error:
 
 ```JULIA
 julia> f3(false)
@@ -93,10 +93,10 @@ KeyError(:b)
 That is to say, the stacktrace is simply attached as "metadata" and
 `Try.enable_errortrace()` does not alter how `Err` values behave.
 
-Limitation/implementation details: To eliminate the cost of stacktrace capturing
-when it is not used, `Try.enable_errortrace()` is implemented using method
-invalidation. Thus, error trace cannot be enabled for `Task`s that have been
-already started.
+**Limitation/implementation details**: To eliminate the cost of stacktrace
+capturing when it is not used, `Try.enable_errortrace()` is implemented using
+method invalidation. Thus, error trace cannot be enabled for `Task`s that have
+been already started.
 
 ### EAFP