Repository: tomee
Updated Branches:
  refs/heads/master e893b19b6 -> 354b14a3b


Corrected errors in text


Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/372e5213
Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/372e5213
Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/372e5213

Branch: refs/heads/master
Commit: 372e52137e5fc0dcc54946915f66df21f11a0c58
Parents: f032a7f
Author: Richard Monson-Haefel <[email protected]>
Authored: Tue Nov 20 14:03:02 2018 -0600
Committer: Richard Monson-Haefel <[email protected]>
Committed: Tue Nov 20 14:03:02 2018 -0600

----------------------------------------------------------------------
 examples/cdi-basic/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tomee/blob/372e5213/examples/cdi-basic/README.md
----------------------------------------------------------------------
diff --git a/examples/cdi-basic/README.md b/examples/cdi-basic/README.md
index a103135..6518ae0 100644
--- a/examples/cdi-basic/README.md
+++ b/examples/cdi-basic/README.md
@@ -4,7 +4,7 @@ To use `@Inject`, the first thing you need is a 
`META-INF/beans.xml` file in the
 or jar.  This effectively turns on CDI and allows the `@Inject` references to 
work.
 No `META-INF/beans.xml` no injection, period.  This may seem overly strict,
 but it is not without reason.  The CDI API is a bit greedy and does consume a 
fair
-about of resources by design.
+amount of resources by design.
 
 When the container constructs a bean with an `@Inject` reference,
 it will first find or create the object that will be injected.  For the sake of
@@ -23,10 +23,10 @@ then the `Faculty` instance will be injected into the 
`Course` bean.  Finally, t
 have been created.
 
 The `CourseTest` test case drives this creation process by having `Course` 
injected
-into it in its `@Setup` method.  By the time our `@Test` method is invoked,
+in its `@Setup` method.  By the time our `@Test` method is invoked,
 all the real work should be done and we should be ready to go.  In the test 
case we do
 some basic asserts to ensure everything was constructed, all `@PostConstruct` 
methods
-called and everyting injected.
+were called and everyting injected.
 
 ## Faculty <small>a basic injectable pojo</small>
 

Reply via email to