ChangeSet ID:	17641
CVSROOT:	/opt/cvs-commit
Module name:	lostwages
Changes by:	jnewman@wine.codeweavers.com	2005/05/20 12:57:51

Modified files:
	templates/en   : janitorial.template winelib.template 
	templates/en/wineconf: travel.template 
	wwn            : wn20000904_59.xml wn20020213_115.xml 
	                 wn20021206_147.xml wn20030131_155.xml 
	                 wn20030314_161.xml wn20030418_166.xml 
	                 wn20030502_168.xml wn20030718_179.xml 
	                 wn20031108_195.xml wn20031121_197.xml 
	                 wn20041015_244.xml wn20050325_267.xml 
	                 wn20050503_272.xml 

Log message:
	Francois Gouget <fgouget@free.fr>
	Assorted spelling fixes

Patch: http://cvs.winehq.org/patch.py?id=17641

Old revision  New revision  Changes     Path
 1.77          1.78          +1 -1       lostwages/templates/en/janitorial.template
 1.19          1.20          +2 -2       lostwages/templates/en/winelib.template
 1.14          1.15          +1 -1       lostwages/templates/en/wineconf/travel.template
 1.5           1.6           +1 -1       lostwages/wwn/wn20000904_59.xml
 1.8           1.9           +1 -1       lostwages/wwn/wn20020213_115.xml
 1.9           1.10          +1 -1       lostwages/wwn/wn20021206_147.xml
 1.6           1.7           +6 -6       lostwages/wwn/wn20030131_155.xml
 1.4           1.5           +1 -1       lostwages/wwn/wn20030314_161.xml
 1.7           1.8           +1 -1       lostwages/wwn/wn20030418_166.xml
 1.5           1.6           +1 -1       lostwages/wwn/wn20030502_168.xml
 1.4           1.5           +1 -1       lostwages/wwn/wn20030718_179.xml
 1.4           1.5           +3 -3       lostwages/wwn/wn20031108_195.xml
 1.6           1.7           +1 -1       lostwages/wwn/wn20031121_197.xml
 1.5           1.6           +1 -1       lostwages/wwn/wn20041015_244.xml
 1.3           1.4           +1 -1       lostwages/wwn/wn20050325_267.xml
 1.2           1.3           +20 -20     lostwages/wwn/wn20050503_272.xml

Index: lostwages/templates/en/janitorial.template
diff -u -p lostwages/templates/en/janitorial.template:1.77 lostwages/templates/en/janitorial.template:1.78
--- lostwages/templates/en/janitorial.template:1.77	Thu May 23 03:54:27 2013
+++ lostwages/templates/en/janitorial.template	Thu May 23 03:54:27 2013
@@ -270,7 +270,7 @@
   As of Jan 9, 2005, there were 11 occurrences of <tt>HEAP_strdupWtoA</tt>.
   These functions invocations should go away during the W -&gt; A cross-call
   cleanup. It is better to directly fix that sort of cross call, rather than
-  replace this function by other alternatives. The few of them that can not
+  replace this function by other alternatives. The few of them that cannot
   be eliminated this way, should be replaced by calls to <tt>WideCharToMultiByte</tt>.<p>
   <tt>find dlls -name \*.c -exec grep -q HEAP_strdupWtoA {} \; -ls</tt>
   <ul>

Index: lostwages/templates/en/winelib.template
diff -u -p lostwages/templates/en/winelib.template:1.19 lostwages/templates/en/winelib.template:1.20
--- lostwages/templates/en/winelib.template:1.19	Thu May 23 03:54:27 2013
+++ lostwages/templates/en/winelib.template	Thu May 23 03:54:27 2013
@@ -33,7 +33,7 @@
    All of the above have publicly available source code, and
    most are decent candidates for this project. 
 
-  <p>Obviously, we can not start porting all these applications. We have to pick a
+  <p>Obviously, we cannot start porting all these applications. We have to pick a
      few important ones, and work with those.
 
   <h3>How</h3>
@@ -323,7 +323,7 @@ make<br>
     <li>updated: Nov 27, 2002
     <li>homepage: <a href="http://www.bloodshed.net/dev/devcpp.html">www.bloodshed.net/dev/devcpp.html</a>
   </ul>
-  <p><strong>Update</strong>: This project can not be ported using Winelib, 
+  <p><strong>Update</strong>: This project cannot be ported using Winelib, 
      as it is written in Pascal/Delphi.
      It should be possible to port it to Linux using Kylix relatively easily.
      

Index: lostwages/templates/en/wineconf/travel.template
diff -u -p lostwages/templates/en/wineconf/travel.template:1.14 lostwages/templates/en/wineconf/travel.template:1.15
--- lostwages/templates/en/wineconf/travel.template:1.14	Thu May 23 03:54:27 2013
+++ lostwages/templates/en/wineconf/travel.template	Thu May 23 03:54:27 2013
@@ -171,7 +171,7 @@ Lufthansa has a deal with the Deutsche B
 where selected trains have Lufthansa flight numbers and you check in and
 check out at the Stuttgart main station (far far far less crowded than
 the Frankfurt airport).<br /><br />
-If you can not get one of those "flight by rail" try to get with your
+If you cannot get one of those "flight by rail" try to get with your
 flight a "feeder train ticket". That's a train ticket valid only with
 your plane ticket from the airport to your final destination in Germany.
 It's a fixed fee independent of the distance by train and it's way

Index: lostwages/wwn/wn20000904_59.xml
diff -u -p lostwages/wwn/wn20000904_59.xml:1.5 lostwages/wwn/wn20000904_59.xml:1.6
--- lostwages/wwn/wn20000904_59.xml:1.5	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20000904_59.xml	Thu May 23 03:54:27 2013
@@ -153,7 +153,7 @@ new code areas.
 
 For the time being, one can (partially) do that by reading the diffs
 sent out by Alexandre with each release. However, they are _very_ big,
-and one can not easily separate the logical changes from one another.
+and one cannot easily separate the logical changes from one another.
 
 <p />
 

Index: lostwages/wwn/wn20020213_115.xml
diff -u -p lostwages/wwn/wn20020213_115.xml:1.8 lostwages/wwn/wn20020213_115.xml:1.9
--- lostwages/wwn/wn20020213_115.xml:1.8	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20020213_115.xml	Thu May 23 03:54:27 2013
@@ -412,7 +412,7 @@ license:</p>
 	 In other words, they needed that code. They invested some money do get
 	 it. They are happy with the results. Why not release the code? They have
 	 what they needed in the first place? The reason is clear -- it cost them
-	 to get there, they can not aford to bring everybody there for free. I can
+	 to get there, they cannot afford to bring everybody there for free. I can
 	 100% understand that. But if the code was under the LGPL, it would not
 	 matter, because even if they brought everybody there, other companies
 	 could not step ahead of them, since if they did, they themselves could

Index: lostwages/wwn/wn20021206_147.xml
diff -u -p lostwages/wwn/wn20021206_147.xml:1.9 lostwages/wwn/wn20021206_147.xml:1.10
--- lostwages/wwn/wn20021206_147.xml:1.9	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20021206_147.xml	Thu May 23 03:54:27 2013
@@ -173,7 +173,7 @@ with you. So I think that we should:
 <ul>
   <li> NOT include apps that crash or don't work reasonable well
     Just starting up enough to take a shot is not good enough</li>
-  <li> NOT include apps that can not be tweaked into working with
+  <li> NOT include apps that cannot be tweaked into working with
     a reasonable enough of effort. Apps that _require_ cxoffice
     or WineX have no place on this page</li>
   <li> DO include a warning saying that the apps featured on this

Index: lostwages/wwn/wn20030131_155.xml
diff -u -p lostwages/wwn/wn20030131_155.xml:1.6 lostwages/wwn/wn20030131_155.xml:1.7
--- lostwages/wwn/wn20030131_155.xml:1.6	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20030131_155.xml	Thu May 23 03:54:27 2013
@@ -10,7 +10,7 @@
 <intro>
 <p>This is the 155th release of the Wine's kernel cousin publication. 
 Its main goal is to perpetuate the belief that this incredibly useful
-piece of software is some how nearing beta quality.
+piece of software is somehow nearing beta quality.
 It also serves to inform you of what's going on around Wine (the Un*x 
 Windows emulator).</p>
 </intro>
@@ -130,7 +130,7 @@ He is using a glibc 2.3 headbranch snaps
 confirmed first suspicions.
 </p><p>
 __errno_location and __h_errno_location are no longer weak symbols
-and so can not be overwritten any longer. The internal glibc systemcall
+and so cannot be overwritten any longer. The internal glibc systemcall
 wrappers no longer call the functions by reference, but directly.
 </p><p>
 Investigations and several talks to one of our glibc gurus (Andreas Schwab)
@@ -169,7 +169,7 @@ as not enough memory, no space left on a
 denied.  And by it's nature, glibc is the place where system calls
 live.  So the problem is with what Marcus said, <i>
 __errno_location and __h_errno_location are no longer weak symbols
-and so can not be overwritten any longer</i></p>
+and so cannot be overwritten any longer</i></p>
 
 <p>But wait, why are we even in this mess?  Why doesn't Wine just
 use the standard Unix pthread implementation?  The last time the WINE 
@@ -182,8 +182,8 @@ under Linux is clone(2).  The
 "wineserver" process is what's responsible for waiting on those
 threads and it operates as a single process with a giant poll()
 loop.  So it seems we're back to the age-old question of whether Wine 
-can some how graft Windows' threading into the pthreads model 
-or whether it needs to continue it's own.</p>
+can somehow graft Windows' threading into the pthreads model 
+or whether it needs to continue its own.</p>
 
 <p>This problem is going to be even more apparent in a few months
 when RedHat ships a version of glibc that won't work with Wine.</p>
@@ -196,7 +196,7 @@ Excuse me, but somehow I think this is p
 </p><p>
 I mean, both Wine and glibc are successful (?) OSS projects,
 so they should be able to come up with something much better than this
-terribly embarassing solution (after all everybody knew that
+terribly embarrassing solution (after all everybody knew that
 OSS development was a "superiour" approach, didn't they ? ;-).
 </p><p>
 I for one would feel much better if we simply rejected that particular

Index: lostwages/wwn/wn20030314_161.xml
diff -u -p lostwages/wwn/wn20030314_161.xml:1.4 lostwages/wwn/wn20030314_161.xml:1.5
--- lostwages/wwn/wn20030314_161.xml:1.4	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20030314_161.xml	Thu May 23 03:54:27 2013
@@ -133,7 +133,7 @@ Basically 2 ways are left to go:
 Thanks a lot for any information!
 </p></quote>
 
-<p>Eric Pouech suggested some how working on the first idea might
+<p>Eric Pouech suggested somehow working on the first idea might
 help with the problem.  Florian wrote back with more details:</p>
 <quote who="Florian Schirmer"><p>
 I've added some Enter/LeaveCriticalSections

Index: lostwages/wwn/wn20030418_166.xml
diff -u -p lostwages/wwn/wn20030418_166.xml:1.7 lostwages/wwn/wn20030418_166.xml:1.8
--- lostwages/wwn/wn20030418_166.xml:1.7	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20030418_166.xml	Thu May 23 03:54:27 2013
@@ -9,7 +9,7 @@
 
 <intro>
 <p>This is the 166th release of the Wine's kernel cousin publication. 
- Its main goal is to some how escape the confines of a hard drive
+ Its main goal is to somehow escape the confines of a hard drive
  going bad and be thankful for ancient boot floppies that still
  work.
  It also serves to inform you of what's going on around Wine (the Un*x 

Index: lostwages/wwn/wn20030502_168.xml
diff -u -p lostwages/wwn/wn20030502_168.xml:1.5 lostwages/wwn/wn20030502_168.xml:1.6
--- lostwages/wwn/wn20030502_168.xml:1.5	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20030502_168.xml	Thu May 23 03:54:27 2013
@@ -204,7 +204,7 @@ repository on SourceForge</a>.</p>
 <p>Troy Rollo posted a 
 <a href="http://www.winehq.org/hypermail/wine-patches/2003/04/0268.html">small patch</a> adjusting addressable
 memory that made Borland's free compiler (bcc 5.5) work.
-Initially it sounded like he had managed to some how compile
+Initially it sounded like he had managed to somehow compile
 Wine with it, but really what he was doing was using Wine
 to run it and create executables.  Dimi asked him some
 questions (below in italics) and Troy responded:</p>

Index: lostwages/wwn/wn20030718_179.xml
diff -u -p lostwages/wwn/wn20030718_179.xml:1.4 lostwages/wwn/wn20030718_179.xml:1.5
--- lostwages/wwn/wn20030718_179.xml:1.4	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20030718_179.xml	Thu May 23 03:54:27 2013
@@ -370,7 +370,7 @@ and it needs to be preserved for histori
 I swear, fdi.c is the worst code I ever wrote, period.
 </p><p>
 It's just an absolute graveyard of abandoned code-paths and unused 
-variables... it's downright embarassing... and of course all the stuff I 
+variables... it's downright embarrassing... and of course all the stuff I 
 carelessly brushed over is coming back to haunt me for split cabs...  it 
 doesn't help that this is really boring stuff, absolutely no real challenge 
 to keep it interesting except the pure tediousness of it...  Stuart Caie did 

Index: lostwages/wwn/wn20031108_195.xml
diff -u -p lostwages/wwn/wn20031108_195.xml:1.4 lostwages/wwn/wn20031108_195.xml:1.5
--- lostwages/wwn/wn20031108_195.xml:1.4	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20031108_195.xml	Thu May 23 03:54:27 2013
@@ -429,10 +429,10 @@ code like that in Wine:</p>
 As we've seen with encryption regulations in the past, the issue of 
 control-circumvention law dissolves in the face of open-source software. 
 Moreover, in the face of (L)GPL open-source software, it dissolves by 
-*design* - you can not withhold source-code if you want to release 
+*design* - you cannot withhold source-code if you want to release 
 binaries. IIRC, this was one of the major stumbling blocks for 
-TransGaming and the Wine/LGPL debate - they have copyprotection support 
-that they legally can not dream of releasing source for. Some argue that 
+TransGaming and the Wine/LGPL debate - they have copy-protection support 
+that they legally cannot dream of releasing source for. Some argue that 
 binaries are a form of source code anyway, and that you can "read" them 
 in the sense that you can interpret and modify their operation. However, 
 the lawyers seem reasonably comfortable with that argument - they call it 

Index: lostwages/wwn/wn20031121_197.xml
diff -u -p lostwages/wwn/wn20031121_197.xml:1.6 lostwages/wwn/wn20031121_197.xml:1.7
--- lostwages/wwn/wn20031121_197.xml:1.6	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20031121_197.xml	Thu May 23 03:54:27 2013
@@ -126,7 +126,7 @@ I was wondering what is the relation of
 to WineX, at least part of it, which is covered under the GPL. What I was
 wondering about is, whether this code is the same as Wine or is it more
 advanced? Or is this code only the sutff which is also contained in Wine and
-all the other stuff is (more or less) closed, so that you can not use it for
+all the other stuff is (more or less) closed, so that you cannot use it for
 Wine.</p>
 </quote>
 

Index: lostwages/wwn/wn20041015_244.xml
diff -u -p lostwages/wwn/wn20041015_244.xml:1.5 lostwages/wwn/wn20041015_244.xml:1.6
--- lostwages/wwn/wn20041015_244.xml:1.5	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20041015_244.xml	Thu May 23 03:54:27 2013
@@ -449,7 +449,7 @@ pages suggest (but don't state clearly)
 is the expected behavior.
 </p><p>
 This behavior essentially means that on most Windows systems
-the timer resolution of winmm is 1ms and can not be changed.
+the timer resolution of winmm is 1ms and cannot be changed.
 </p><p>
 So, question #1:  anyone object if I fix the timer resolution at 1 ms?
 </p><p>

Index: lostwages/wwn/wn20050325_267.xml
diff -u -p lostwages/wwn/wn20050325_267.xml:1.3 lostwages/wwn/wn20050325_267.xml:1.4
--- lostwages/wwn/wn20050325_267.xml:1.3	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20050325_267.xml	Thu May 23 03:54:27 2013
@@ -321,7 +321,7 @@ http://img87.exs.cx/my.php?loc=img87.=wi
 <p>Dmitry Timoshkov felt more work needed to go into the
 low-level parts of it,
 <quote who="Dmitry Timoshkov">
- user32 can not depend on uxtheme or any other high level dll. You need to
+ user32 cannot depend on uxtheme or any other high level dll. You need to
  make all the work inside of uxtheme by subclassing/patching every class you
  wish to change the painting for, and do all the painting inside of uxtheme.
  I'm not sure how to do it cleanly without adding an explicit dependency of

Index: lostwages/wwn/wn20050503_272.xml
diff -u -p lostwages/wwn/wn20050503_272.xml:1.2 lostwages/wwn/wn20050503_272.xml:1.3
--- lostwages/wwn/wn20050503_272.xml:1.2	Thu May 23 03:54:27 2013
+++ lostwages/wwn/wn20050503_272.xml	Thu May 23 03:54:27 2013
@@ -30,7 +30,7 @@ went to bed.  WineConf ended earlier in
 I guess I can take solace in the fact ten Wine developers are
 still sitting downstairs and will probably be a lot more tired than me
 in the morning.  I surely won't finish writing this summary tonight,
-but it's nice to look back and reflect on what a great three days its been.
+but it's nice to look back and reflect on what a great three days it has been.
 </p><p>
 Some of you might be looking for the short summary version, so it's
 worth recapping some major highlights.  First, Alexandre has imposed some
@@ -44,7 +44,7 @@ WineConf 2005 unofficially kicked off Fr
 Tangungshotel Stuttgart.  There was a really nice outside
 patio at the hotel and a bar inside.  We spent a little while discussing
 going out somewhere, but we were having too good of a time to be bothered
-trying to leave.  Before we knew it we'd some how consumed a bunch
+trying to leave.  Before we knew it we'd somehow consumed a bunch
 of pizzas Andi Mohr ordered and the bar began shutting down.
 </p><p>
 Saturday morning we kicked off WineConf with a short presentation from
@@ -114,7 +114,7 @@ window manager.  Finally, Marcus Meissne
 plans for 64-bit support. Alexandre said there's no reason 
 not to but it would take someone motivated to do it.	
 </p><p>
-Overall, this is a much more remarkable than last year.  I think 
+Overall, this is much more remarkable than last year.  I think 
 after last year's presentation everyone was left with a sense there
 was a lot more work that needed to be done and it hadn't been
 thought about.  Even worse, only Alexandre could do it.  
@@ -149,7 +149,7 @@ for that would be sometime after 0.9 but
 </p><p>
 Dimi then outlined the key focus of the to do list is
 to standardize on interfaces: UI within Wine, WineHQ
-as a information conduit, file formats and exported
+as an information conduit, file formats and exported
 API's for developers, etc.  As far as that goes, we're
 in great shape.  There's really nothing left to be
 done except move the config into the registry.  
@@ -281,7 +281,7 @@ happen.  He implemented a new wineserver
 reading from a file.  He benchmarked wineserver with a 
 100MB file and various buffer sizes.  He then went
 through and compared this performance with open, 
-Createfile, and Createfile on a mounted SMB share.  
+CreateFile, and CreateFile on a mounted SMB share.  
 He further compared it with the number of clients
 within wineserver to see how well it scaled.  The
 results looked extremely promising.  With regard
@@ -308,7 +308,7 @@ He opened with some questions, such as w
 cooperate on, whether or not we should aim for
 Samba and Wine interoperability, and if we 
 cooperate how we should go about doing it.  Samba
-doesn't about API compatibility but Wine does.
+doesn't care about API compatibility but Wine does.
 Samba doesn't have to worry about object level 
 compatibility, just wire level.  However, both 
 of us need to get the same things right.  We 
@@ -321,7 +321,7 @@ to be most common areas we could look at
 near-term, with the possible exception of the
 talk Andrew Bartlett presented next.
 </p><p>
-The RPC world could present some interesting,
+The RPC world could present some interesting
 areas for working with Samba.
 Looking at IDL compilers, it's apparent Wine's widl
 compiler and Samba's pidl compiler were built for
@@ -382,7 +382,7 @@ The new Samba will contain an interface
 SSPI and can be called from everywhere.  It can sit both on
 the client and server side and handle blob passing.  The 
 library behind this is Andrew's GENSEC.  He thought it might
-be possible to wrap GENSEC into the SSPI API's Wine has to
+be possible to wrap GENSEC into the SSPI APIs Wine has to
 implement.  At the very least GENSEC can provide a way to
 learn about SSPI and would help us build it properly.  
 </p><p>
@@ -398,7 +398,7 @@ gets designed will have to take that int
 </p><p>
 After that we wrapped up and meandered back to the hotel to
 get ready for the night.  We headed downtown to the Rosenau for
-a dinner put on by CodeWeaver's.  We had a fantastic time.
+a dinner put on by CodeWeavers.  We had a fantastic time.
 I had an interesting conversation with Jerry Carter and Ira 
 Krakow about the dynamics of open source projects as well
 as other random stuff.  We stayed at the restaurant fairly
@@ -410,7 +410,7 @@ were the last ones to get to bed.
 Breakfast came really early.  To start out the agenda we
 had Steven Edwards and Hyperion from the ReactOS project
 show off their latest work.  Things really seem to have
-improved from last year.  Rather running it in VMWare, 
+improved from last year.  Rather than running it in VMWare, 
 Steven actually booted his laptop into ROS.  The running
 joke seemed to be something like Samba is hard, Wine is
 daunting, and the ROS guys are just crazy.  They aim to
@@ -419,7 +419,7 @@ system, including support for devices an
 always raises the question of why bother, but I like to
 think back to something Steven mentioned a few years ago:
 Linux was just trying to be a free replacement for Unix,
-so ROS is just trying to be a free replacement of Windows.
+so ROS is just trying to be a free replacement for Windows.
 </p><p>
 A lot of things work this year and many areas are progressing.  
 Thanks to Wine they can
@@ -427,7 +427,7 @@ run applications like OpenOffice, AbiWor
 have driver support now for nvidia and ATI.  Under development
 they have more networking support, OpenGL/DirectX, and 
 plug 'n play support.  The kernel is getting more stable,
-but they need to a better job at things like syscall and return value
+but they need to do a better job at things like syscall and return value
 checking in order to get more stable.  Many large projects
 haven't been started yet though, including a printing 
 subsystem, security subsystem, NTFS support, etc.  
@@ -485,10 +485,10 @@ to package up calls and maybe pass them
 </p><p>
 So where are we at?  Wine's Direct3D 8 code is relatively 
 complete.  D3D9 won't be a massive change and centers around 
-adding shader support.  Things aren't in that good of shape at
+adding shader support.  Things aren't in that good of a shape at
 the moment though.  The new wined3d library was implemented
 for combining D3D8 and D3D9 code.  However, only part of the
-code has been moved into the library.  It's goal right now is
+code has been moved into the library.  Its goal right now is
 to implement D3D9 on top of it and then switch D3D8 over to it.
 But that process remains to be done.  Oliver Stieber's work
 has been written with wined3d in mind, but it needs to get
@@ -514,7 +514,7 @@ you need to do really impressive stuff.
 a demo of the game <i>Mafia</i> with all kinds of cool D3D
 effects.  Equally impressive were some of the demos with
 3DMark.  Jason pointed out that due to rebuilding his system
-we were actually the demos running on CVS code rather than
+the demos were actually running on CVS code rather than
 his development tree.
 </p><p>
 --
@@ -606,7 +606,7 @@ For a couple of years Wine, or at least
 develop an automated testing suite that tests graphical apps.  Right now
 the Wine test suite is great for testing API's, but it doesn't do any
 good for actually testing a real world application and finding regressions.
-The idea is to some how run a graphical program, make it do things, and
+The idea is to somehow run a graphical program, make it do things, and
 then test to make sure those things were done correctly.  If someone
 fails, then you can begin looking at patches to figure out which one 
 caused the regression.
@@ -618,7 +618,7 @@ If that sounds difficult, it's because i
 spent a year just looking for a solution before deciding on the elements of
 CXTest.  Now it appears 
 <a href="http://www.cxtest.org">CXTest</a> is ready for widespread use.
-Besides just testing different programs and Wine, it let's us test things
+Besides just testing different programs and Wine, it lets us test things
 against different distros and kernels.  It's completely possible a new
 kernel could break things.  If you're interested in the technical details 
 of CXTest and how to go about running it, check out the CXTest 
@@ -630,14 +630,14 @@ capture a picture, send key strokes, cap
 an automated way to control graphical elements you'd normally never have
 control over.  The components involved include scripts and some custom
 Winelib stuff (part of the package and GPL'ed.)  
-elements and click on different things.  The reporting side can send test 
+to click on different things.  The reporting side can send test 
 results to a central website and get formatted nicely.  
 </p><p>
 A large discussion ensued about how useful it would be for Wine.  What
 we seem to have learned is we're decent at collecting bug reports and
 finding which patch caused a regression.  However, we're not that great
 at responding to such reports.  Whether or not we need a lot more data
-is debatable.  In the end it seems running the tests are easy, so maybe
+is debatable.  In the end it seems running the tests is easy, so maybe
 we just need to do it.
 </p><p>
 --
@@ -660,7 +660,7 @@ Another area we could improve upon are j
 window manager extensions would help, but we also know things we could
 do.  For example, a DIB renderer is needed and theming support integrated
 with the desktop would be nice as well.  Dimi also brought up his
-(healthy) obsession with DLL's.  All this is important just because it's
+(healthy) obsession with DLLs.  All this is important just because it's
 what the user ends up seeing - it can easily project a bad image.
 </p><p>
 Better desktop integration could also be done.  For instance, mapping