Peers are lazy vals now

1 files changed, 3 insertions, 4 deletions

diff --git a/src/swing/doc/README b/src/swing/doc/README
index df3565e276..00aebe7b19 100644
--- a/src/swing/doc/README
+++ b/src/swing/doc/README
@@ -1,8 +1,7 @@
 scala.swing
 
 This is a UI library that will wrap most of Java Swing for Scala in a straightforward manner. 
-The widget class hierarchy loosely resembles that of Java Swing. In a few places we decided 
-to chose to depart from Java Swing's architecture. The main differences are:
+The widget class hierarchy loosely resembles that of Java Swing. The main differences are:
 
   In Java Swing all components are containers per default. This doesn't make much sense for 
   a number of components, like TextField, CheckBox, RadioButton, and so on. Our guess is that 
@@ -12,7 +11,7 @@ to chose to depart from Java Swing's architecture. The main differences are:
   Layout managers and panels are coupled. There is no way to exchange the layout manager 
   of a panel. As a result, the layout constraints for widgets can be typed. 
   (Note that you gain more type-safety and don't loose much flexibility here. Besides 
-  that it is not a common operation, exchanging the layout manager of a panel in Java 
+  being not a common operation, exchanging the layout manager of a panel in Java 
   Swing almost always leads to exchanging the layout constraints for every of the panel's 
   child component. In the end, it is not more work to move all children to a newly created 
   panel.)
@@ -23,7 +22,7 @@ to chose to depart from Java Swing's architecture. The main differences are:
 The library comprises three main packages:
 
   scala.swing
-    All essential widget classes and traits.
+    All widget classes and traits.
     
   scala.swing.event
     The event hierarchy.