X-Git-Url: http://wamblee.org/gitweb/?a=blobdiff_plain;f=src%2Fsite%2Fxdoc%2Findex.xml;h=fe31114573bb0b90899e5f603ae1751f51f712da;hb=a23e0d23d8097450325b08b1c09ac4fffdde6671;hp=7b5dfe51e78e64064e8c449fab16113aeeb2e020;hpb=233b206571da3d744844bac769e04733112b9dd1;p=utils

diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index 7b5dfe51..fe311145 100644
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -35,7 +35,9 @@
         frameworks but that it is not a good idea to tie into any one of them 
         specifically. Also, the support that one actually needs to develop applications and in
         particular enterprise applications efficiently only requires a few basic support utilities
-        and typically not a big framework. </p>
+        and typically not a big framework. Therefore, you will find a couple of small 
+        utilities that may be familiar in the functionality they offer to what is found 
+        in other frameworks. </p>
       <p>Apart from this, there are many other interesting developments going on: </p>
       <ul>
         <li><em>Java EE 6 dependency injection:</em> Java EE 6 provides a powerful dependency
@@ -53,7 +55,7 @@
         beans, lifecycle management, Contexts and Dependency Injection, used in combination with Enterprise OSGI will
         provide the most powerful way to develop applications in the future. In this. I am making
         only an exception for web frameworks to which I think JSF is not a good solution. I would
-        use <a href="http://wicket.apache.org">Wicket</a> anyday if it's up to me. </p>
+        use <a href="http://wicket.apache.org">Wicket</a> anyday if it were up to me. </p>
 
     </section>
   </body>