X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=mcs%2Fclass%2FSystem.Drawing%2FREADME;h=8105c140e8be5b47cb3de4060e02e898dcfa9cc1;hb=b1f84a518a8d35ea03da9c25559cf4285a1a8c75;hp=b0ea60430cc14201d77c26247226f9d93556bab0;hpb=6daf8ea6644207ba23441eaf150739970cd894b9;p=mono.git

diff --git a/mcs/class/System.Drawing/README b/mcs/class/System.Drawing/README
index b0ea60430cc..8105c140e8b 100644
--- a/mcs/class/System.Drawing/README
+++ b/mcs/class/System.Drawing/README
@@ -30,11 +30,11 @@
  file. Please follow the alphabetical order while adding the name of your test
  class.
 
- Samples are independent C# programs with a Main method. Sample are supposed
+ Samples are independent C# programs with a Main method. Samples are supposed
  to solve two purposes. First, samples expose the bugs that are not captured
- by Nunit tests. To achieve this, it is advisable that we don't repeat the
- code in a test and sample for any class until unless required. Second, samples
- help System.Drawing users in understanding System.Drawing components as well
- as in writing System.Drawing applications. Writing too trivial samples for
- well known classes might not be really helpful for the users. It is better
- to write a sample to solve a particular problem.
+ by Nunit tests. To achieve this, it is advisable not to repeat the code in a
+ test and a sample for any class until unless required. Second, samples help
+ System.Drawing users in understanding System.Drawing components as well as in
+ writing System.Drawing applications. Writing too trivial samples for well known
+ classes might not be really helpful for the users. It is better to write a sample
+ to solve a particular problem.