[WINEHQ] Capitalize Wine when referring to the project

Francois Gouget fgouget at free.fr
Mon Jan 10 05:55:19 CST 2005 

When referring to the binary or to the Debian/RPM package name, then 
wine should be lowercase. But when referring to the project we should 
standardize on the capitalized form, at least in the more static 
parts of the web site (i.e. I'm excluding the Wine Weekly News because 
I don't want to go through the 250+ issues<g>).


Changelog:

  * site
    templates/en/contributing.template
    templates/en/download-deb.template
    templates/en/fun_projects.template
    templates/en/helping-applications.template
    templates/en/home_about.template
    templates/en/howto.template
    templates/en/janitorial.template
    templates/en/myths.template
    templates/en/sending_patches.template
    templates/en/status_porting.template
    templates/en/status_todo.template
    templates/en/supported_applications.template
    templates/en/todo_lists.template
    templates/en/who.template
    templates/en/winelib.template
    wwn/wn19990620_1.xml

    Capitalize Wine when referring to the project.


-- 
Francois Gouget         fgouget at free.fr        http://fgouget.free.fr/
                   In a world without fences who needs Gates?
-------------- next part --------------
Index: site
===================================================================
RCS file: /var/cvs/lostwages/site,v
retrieving revision 1.6
diff -u -r1.6 site
--- site	3 Dec 2004 21:32:23 -0000	1.6
+++ site	5 Jan 2005 21:35:18 -0000
@@ -116,7 +116,7 @@
 	return $text;
 }
 
-// load the annouce file for latest version of wine
+// load the announce file for latest version of Wine
 function view_announce ($ver)
 {
     global $file_root, $config, $html;
@@ -209,7 +209,7 @@
     return $news_body;
 }
 
-// load the annouce file for latest version of wine
+// load the announce file for latest version of Wine
 function view_screenshots ($x)
 {
     global $file_root, $config, $html;
Index: templates/en/contributing.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/contributing.template,v
retrieving revision 1.20
diff -u -r1.20 contributing.template
--- templates/en/contributing.template	8 Dec 2004 16:18:31 -0000	1.20
+++ templates/en/contributing.template	5 Jan 2005 19:33:47 -0000
@@ -24,7 +24,7 @@
 
    <ol>
     <li><a href="#web">Web site maintenance</a>
-    </li><li><a href="#draw">Draw icons for wine</a>
+    </li><li><a href="#draw">Draw icons for Wine</a>
     </li><li><a href="#app_owners">Application owners</a>
     </li><li><a href="#support">Bug hunting and support</a>
    </li></ol>
@@ -35,7 +35,7 @@
     </li><li><a href="#conf_tests">Conformance tests</a>
     </li><li><a href="#doc_win_api">Documentation of the windows API functions</a>
 
-    </li><li><a href="#port_app">Port your windows application to wine</a>
+    </li><li><a href="#port_app">Port your Windows application to Wine</a>
     </li><li><a href="#code_review">Perform a focused code review</a>
    </li></ol>
   </li><li><a href="#docu">Miscellaneous</a>
@@ -373,7 +384,7 @@
     and also the man pages and other files in the documentation/ directory.
     </p>
     <p>Your job would be to make sure that every patch a developer submits
-    that changes wine configuration behaviour in any way
+    that changes the Wine configuration behaviour in any way
     gets documented properly as soon as possible.
     This would be done through testing new functionality and optionally
     asking developers about what their patch truly does.
Index: templates/en/download-deb.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/download-deb.template,v
retrieving revision 1.1
diff -u -r1.1 download-deb.template
--- templates/en/download-deb.template	8 Dec 2004 16:18:31 -0000	1.1
+++ templates/en/download-deb.template	5 Jan 2005 17:24:35 -0000
@@ -8,7 +8,7 @@
 the needed dependencies for a software package, as well as keep the package 
 up to date, by scanning what are known as APT repositories.  Debian based 
 distributions have their own repositories of software, many of which include
-wine, however we keep the latest available packages here for download.
+Wine, however we keep the latest available packages here for download.
 </p>
 
 <p>Packages here are designed to function on Debian unstable, and are meant to 
@@ -20,17 +20,17 @@
 
 <h2>Installing from the WineHQ APT Repository with Synaptic:</h2>
 
-<p>To install wine from the WineHQ APT repository, you need to configure APT to
-look in the right place for the wine packages.  On Ubuntu systems, and those 
+<p>To install Wine from the WineHQ APT repository, you need to configure APT to
+look in the right place for the Wine packages.  On Ubuntu systems, and those 
 using the Synaptic Package Manager, this can be done easily by opening up 
 Synaptic and selecting Settings->Repositories.  Then click add and enter the 
 following information:</p>
 
 <img src="{$root}/images/distro/synaptic-repository-deb.png" alt="Synaptic Package Repository Screenshot" border="0">
 
-<p>Then, simply click reload and search for the package wine for installation. 
-If you already have a wine package installed, selecting mark all upgrades and
-opting for the "smart upgrade" option should update wine to the newest version.
+<p>Then, simply click reload and search for the package 'wine' for installation. 
+If you already have a 'wine' package installed, selecting mark all upgrades and
+opting for the "smart upgrade" option should update Wine to the newest version.
 </p>
 
 <h2>Installing from the WineHQ APT Repository with the console:</h2>
@@ -43,7 +43,7 @@
 deb-src http://wine.sourceforge.net/Ubuntu/apt/ source/</p>
 
 <p>Then, you can run apt-get update to update APT's package information. 
-Finally, to install wine, do apt-get install wine.</p>
+Finally, to install Wine, do 'apt-get install wine'.</p>
 
 <h2>Building the Wine Package from Source using APT:</h2>
 
@@ -51,11 +51,11 @@
 there is no binary package available for your architecture, or if you wish to 
 create a fresh .deb file from scratch.  To do this, first follow the 
 instructions for installing from the console above, except instead of running
-apt-get install wine run apt-get build-dep wine.  This will download the needed
+'apt-get install wine' run 'apt-get build-dep wine'.  This will download the needed
 development packages for your system to make the wine package.  Then, run 
-apt-get --build source wine, have a snack, and wait for the compiling to finish.
+'apt-get --build source wine', have a snack, and wait for the compiling to finish.
 </p>
 
 <p>To install your newly created package (which should be in whatever directory
-you were in when you ran apt-get --build source), run dpkg -i wine*.deb as root.
+you were in when you ran apt-get --build source), run 'dpkg -i wine*.deb' as root.
 </p>
Index: templates/en/fun_projects.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/fun_projects.template,v
retrieving revision 1.21
diff -u -r1.21 fun_projects.template
--- templates/en/fun_projects.template	3 Jan 2005 23:27:30 -0000	1.21
+++ templates/en/fun_projects.template	5 Jan 2005 19:35:21 -0000
@@ -452,7 +452,7 @@
   lazy to integrate the program that processed that into a table so
   far.  :)  Right now it requires dumpbin (Visual C++)  I plan to add pedump
   or winedump support so more people are able to use it.  It is also
-  analyzing the wine .spec files to determine if each API has an entry and
+  analyzing the Wine .spec files to determine if each API has an entry and
   reports whether it's a stub, unimplemented (not in spec files), etc.
 
 
Index: templates/en/helping-applications.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/helping-applications.template,v
retrieving revision 1.3
diff -u -r1.3 helping-applications.template
--- templates/en/helping-applications.template	4 Jan 2005 20:42:41 -0000	1.3
+++ templates/en/helping-applications.template	5 Jan 2005 17:22:30 -0000
@@ -4,7 +4,7 @@
 you should do is register yourself in the
 <a href="http://appdb.winehq.org/">applications database</a> and use one
 of your votes to indicate that you'd like more effort to be spent on
-the application.  Every once in a while, a wine developer will finish a
+the application.  Every once in a while, a Wine developer will finish a
 project and look for something to do - combing through the higher voted
 apps to find one that people need work on is a great way to spend one's
 time and fill up a todo list.</p>
@@ -13,7 +13,7 @@
 applications database, there is an easy to use form available for you to
 add it. <!-- link to form -->  If the application is in the database, but
 lacks a maintainer, you should consider becoming one.  If you are
-familiar with wine and have a desire to test the application and help get
+familiar with Wine and have a desire to test the application and help get
 or keep it working, please apply by clicking the link in the application's
 page.  Each application should have a supermaintainer, and, if different
 versions of the application are substantially different (such as in
@@ -24,21 +24,21 @@
 
 <p>If you are the developer or publisher of the application, you
 obviously have a very big incentive to help get your application working
-under wine.  Fortunately, there are many options available to you other
+under Wine.  Fortunately, there are many options available to you other
 than reporting bugs and hoping someone will fix them. By far the easiest
-way is to simply send free copies of your software to wine developers and
+way is to simply send free copies of your software to Wine developers and
 hope they'll take an interest in getting it working.  You'd be amazed how
 effective this approach can be, particularly for games. An alternative
-option, perhaps more effective and expensive, is to pay wine developers
+option, perhaps more effective and expensive, is to pay Wine developers
 for their work on your application, either directly through a negotiated
-contract or indirectly by posting a bounty. Codeweavers, a major wine
+contract or indirectly by posting a bounty. CodeWeavers, a major Wine
 developer, offers a special section for pledges at
 <a href="http://www.codeweavers.com/site/compatibility/">their compatibility
 center</a> website. The most direct method, however, is to help develop
-wine itself and contribute code directly, which is exactly what Corel did
+Wine itself and contribute code directly, which is exactly what Corel did
 for WordPerfect several years ago.  In any case, making a post on the
-wine developers <a href="http://www.winehq.org/site/forums">email
-list</a> can go a long way.
+Wine developers <a href="http://www.winehq.org/site/forums">email
+list</a> can go a long way.</p>
 
 <h2>If your application doesn't work:</h2>
 
@@ -46,16 +46,16 @@
 to even run at all, there are a number of steps you can take to help us.
 The most important thing is to find out where exactly the application is
 failing. To diagnose application problems, the first step is to run the
-program from the console using wine, rather than from a gui shortcut.
-This will allow wine to output error messages to the console, the
+program from the console using Wine, rather than from a gui shortcut.
+This will allow Wine to output error messages to the console, the
 understanding of which are key to solving the problem and getting the
 application to work.</p>
 
 <p>An application may not work because Wine doesn't yet fully implement
 one of the DLL files the application is trying to use.  If you encounter
 a DLL not found error, or see a lot of "FixMe:" messages while running the
-application in wine, this is likely the case. When this occurs, you can
-try using native (non-wine) DLL files in place of Wine's builtin ones.
+application in Wine, this is likely the case. When this occurs, you can
+try using native (non-Wine) DLL files in place of Wine's builtin ones.
 Check the application database page for the program. There may be
 special configuration options or instructions for installing native DLL
 files there that you can try to get the application working. For
@@ -70,12 +70,12 @@
 a programmer, we'd really like it if you tried to help us directly;
 please read the
 <a href="http://www.winehq.org/site/developer-cheatsheet">getting
-started with wine development guide</a> if you're interested.</p>
+started with Wine development guide</a> if you're interested.</p>
 
 
 <h2>If your application does work, but with some difficulty:</h2>
 
-<p>Sometimes, applications run under wine but don't function quite as
+<p>Sometimes, applications run under Wine but don't function quite as
 smoothly as they do in windows.  They may have display errors, a feature
 may be broken, or they may run unusually slow.  These applications should
 receive a lower rating from their maintainers of between 2 and 4 stars in
@@ -91,15 +91,15 @@
 
 
 <h2>If your application used to work, but has since broken in a new
-version of wine:</h2>
+version of Wine:</h2>
 
 <p>Wine is a large and complex project, composed of many files written
 by different authors.  Sometimes, an attempt to change a file and expand
 support for one application will unexpectedly cause another application
 to stop functioning.  These changes are known as "regressions", and they
-are unfortunately sometimes found in the wine source code because the
+are unfortunately sometimes found in the Wine source code because the
 author of a patch that causes a regression is quite simply unaware of it.
-Since the wine developers can't possibly test every application with every
+Since the Wine developers can't possibly test every application with every
 patch, we have to rely on the community to inform us of when regressions
 occur so that the problem can be easily identified and ultimately fixed.
 Without community involvement, regressions can go unfixed for potentially
@@ -109,7 +109,7 @@
 provide us with as much information as you can about when and how it
 broke.  This allows us to isolate the exact thing we screwed up in the
 code and provide a fix.  Please provide as much as you know about which
-version of wine worked, and which version didn't, including the version
+version of Wine worked, and which version didn't, including the version
 number and how you installed it (from source, binary packages, etc.)
 Finally, please post these things in the Application Database page for the
 app.</p>  
@@ -118,7 +118,7 @@
 patch which broke your application.  This takes quite a bit of time and
 effort, but it is quite simply the best way to get your application
 working again.  When it comes to fixing regressions, the only thing more
-helpful to the wine developers than knowing exactly which patch caused a
+helpful to the Wine developers than knowing exactly which patch caused a
 regression is receiving a fix for the patch itself.  For help with
 isolating problem patches, please see the documentation on
 <a href="http://www.winehq.org/site/docs/wine-devel/x1375">regression
Index: templates/en/home_about.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/home_about.template,v
retrieving revision 1.18
diff -u -r1.18 home_about.template
--- templates/en/home_about.template	21 Dec 2004 22:14:10 -0000	1.18
+++ templates/en/home_about.template	5 Jan 2005 19:37:49 -0000
@@ -19,7 +19,7 @@
 is so important</a>, and <a href="{$root}/site/myths">Debunking Wine Myths</a>.
 If you are wondering how well a particular application works in Wine, please 
 examine the <a href="http://appdb.winehq.org/">Applications Database</a>.  For 
-installation instructions and step-by-step help with running wine, take a look
+installation instructions and step-by-step help with running Wine, take a look
 at the <a href="{$root}/site/docs/wine-user/index">User Guide</a>.
 </p>
 
Index: templates/en/howto.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/howto.template,v
retrieving revision 1.13
diff -u -r1.13 howto.template
--- templates/en/howto.template	18 Jun 2004 15:08:41 -0000	1.13
+++ templates/en/howto.template	5 Jan 2005 19:38:12 -0000
@@ -11,7 +11,7 @@
 version and install a newer one. Refer to your distributions documentation
 on how to remove packages.</p>
 
-<p>YYYYMMDD is the version of wine in Year Month Day format. Wine
+<p>YYYYMMDD is the version of Wine in Year Month Day format. Wine
 releases are generally not subject to QA, older releases are not
 really any more stable so you should always install the very latest
 one. When upgrades come out, try them, normally they will be fine but
Index: templates/en/janitorial.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/janitorial.template,v
retrieving revision 1.54
diff -u -r1.54 janitorial.template
--- templates/en/janitorial.template	6 Jan 2005 16:48:31 -0000	1.54
+++ templates/en/janitorial.template	6 Jan 2005 22:55:34 -0000
@@ -502,7 +502,7 @@
   From Eric: <i>there's lot of code which relies on HeapReAlloc would allocate 
   a block if the block to reallocate is NULL (as realloc does in stdlib);
   this is not the case in windows, and we should fix it (and first, fix 
-  all the wine code relying on this)</i>
+  all the Wine code relying on this)</i>
   <ul>
     <li>workers: Oleg Prokhorov, Dimitrie O. Paun
     <li>completed: <span class="done">Mar 10, 2004</span>
Index: templates/en/myths.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/myths.template,v
retrieving revision 1.7
diff -u -r1.7 myths.template
--- templates/en/myths.template	16 Feb 2004 17:00:40 -0000	1.7
+++ templates/en/myths.template	5 Jan 2005 19:39:07 -0000
@@ -263,7 +263,7 @@
 Currently in the LGPL Wine tree you can find support for
 SafeDisc 1 with SafeDisc 2 on the way.  The caveat being
 that Wine must run in NT mode (configure winver &quot;nt40&quot;
-in the wine config file).
+in the Wine config file).
 
 <hr>
 <table width="100%" border=0 cellpadding=0 cellspacing=0>
Index: templates/en/sending_patches.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/sending_patches.template,v
retrieving revision 1.7
diff -u -r1.7 sending_patches.template
--- templates/en/sending_patches.template	2 Sep 2004 19:07:07 -0000	1.7
+++ templates/en/sending_patches.template	5 Jan 2005 19:40:30 -0000
@@ -62,7 +62,7 @@
  </td></tr>
  </table>
  
-<p>to generate the patch from the top wine directory and save the output to a file.
+<p>to generate the patch from the top source directory and save the output to a file.
 <code>cvs diff</code> will always ignore newly added files, so you'll
 need to do something like:</p>
 
Index: templates/en/status_porting.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/status_porting.template,v
retrieving revision 1.4
diff -u -r1.4 status_porting.template
--- templates/en/status_porting.template	26 Mar 2004 00:02:11 -0000	1.4
+++ templates/en/status_porting.template	5 Jan 2005 19:37:07 -0000
@@ -13,7 +13,7 @@
 	<th align=center>msvc</th>
 	<th align=center>mingw</th>
 	<th align=center>suncc</th>
-	<th align=center>wine</th>
+	<th align=center>Wine</th>
 	<th align=center>psdk</th>
 	<th align=center>w32api</th>
 	<th align=center>Linux</th>
Index: templates/en/status_todo.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/status_todo.template,v
retrieving revision 1.11
diff -u -r1.11 status_todo.template
--- templates/en/status_todo.template	18 Aug 2004 20:33:19 -0000	1.11
+++ templates/en/status_todo.template	5 Jan 2005 19:43:00 -0000
@@ -6,7 +6,7 @@
 
 <ul>
 <li>Rewrite Wine's window management code to be able to change the visual of an X window once the window has been created.</li>
-<li>In Desktop Mode all processes started from one wine invocation should be confined to one desktop window.</li>
+<li>In Desktop mode all processes started from one Wine invocation should be confined to one desktop window.</li>
 <li>Window management needs proper inter-process handling of activation, focus, repaint.</li>
 <li>Workaround for the "no keyboard without Desktop mode" problem.</li>
 
@@ -36,7 +36,8 @@
 <h3><a name="Registry"></a>Registry contents<br></h3>
 
 <ul>
-<li>Implement DllRegisterServer for all COM components so that they can register the appropriate keys in the registry when wine is installed</li>
+<li>Implement DllRegisterServer for all COM components so that they can
+  register the appropriate keys in the registry when Wine is installed</li>
 <li>we also need to link that functionality into the wine install script</li>
 </ul>
 
@@ -99,7 +100,7 @@
 <h3><a name="Tools_"></a>Tools<br></h3>
 
 <ul>
-<li>Wine installation process should install and configure wine</li>
+<li>Wine installation process should install and configure Wine</li>
 <li>Perform Windows' reboot operations automatically when required</li>
 <li>Winemaker fixes</li>
 <li>Run C regression tests on Windows with MSVC</li>
@@ -199,7 +200,7 @@
     * Some real RPC tests,although there are some tests of some peripheral rpcrt4 API's -- no actual RPC's are tested.
     * Implement /Oicf "stubless" marshalling
     * Implement full stub/proxy support for widl
-    * Get Wine's DCOM to use wine's RPC as appropriate.
+    * Get Wine's DCOM to use Wine's RPC as appropriate.
     * Fix the wire protocol
      - Implement the OXID resolver and other ORPC peccadilloes
 </pre>
@@ -299,7 +300,7 @@
 
 [Dmscript]
     * VB script execution support (actually only source is loaded). Maybe using a 
-      generic wine VB script kernel (as the vbscript.dll seems to provide on 
+      generic Wine VB script kernel (as the vbscript.dll seems to provide on 
       windows) using ole32/com (most of the needs are already here)
 
 [DirectInput] 
Index: templates/en/supported_applications.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/supported_applications.template,v
retrieving revision 1.12
diff -u -r1.12 supported_applications.template
--- templates/en/supported_applications.template	26 May 2004 16:03:07 -0000	1.12
+++ templates/en/supported_applications.template	5 Jan 2005 21:39:37 -0000
@@ -138,7 +138,7 @@
      (Dlls installed atl.dll,msvcrt.dll)
    <li> Run: No, required comctl32 (imagelist proble) and riched32 native.
      (it wasn't able to add users to contact list even with this native
-      dlls, i don't know if it was a different problem, or wine related)
+      dlls, I don't know if it was a different problem, or Wine related)
    <li> Tucows top 100 ladder: 5
   </ul>
 </dd>
Index: templates/en/todo_lists.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/todo_lists.template,v
retrieving revision 1.53
diff -u -r1.53 todo_lists.template
--- templates/en/todo_lists.template	5 Jan 2005 19:15:56 -0000	1.53
+++ templates/en/todo_lists.template	6 Jan 2005 22:55:34 -0000
@@ -125,7 +125,7 @@
 	    <li> status: <a href="http://www.winehq.org/hypermail/wine-patches/2004/10/0141.html">update</a> committed.
 	    <li> updated: Dec 7, 2004
 	  </ul>
-	<li> Revise the getting wine chapter <span class="inprogress">[IN PROGRESS]</span>
+	<li> Revise the 'Getting Wine' chapter <span class="inprogress">[IN PROGRESS]</span>
 	  <ul>
 	    <li> worker: <a href="mailto:scott at open-vote.org">Scott Ritchie</a>
 	    <li> status: rewriting until things stop changing
Index: templates/en/who.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/who.template,v
retrieving revision 1.22
diff -u -r1.22 who.template
--- templates/en/who.template	16 Jun 2004 13:43:22 -0000	1.22
+++ templates/en/who.template	5 Jan 2005 19:45:38 -0000
@@ -288,7 +288,7 @@
     <td></td></tr></table>
 
     <p>    
-    Tony got involved with wine in 2002 trying to get his childrens games
+    Tony got involved with Wine in 2002 trying to get his children's games
     to run. His first patch was in ddraw clearing up some screen corruption
     in SimCity. He has worked at cleaning up the documentation, various 
     janitorial projects and the care and feeding of Bugzilla. His latest
@@ -568,10 +568,10 @@
     <b>Email:</b> gmturner007 -at- ameritech dot net</td>
     <td></td></tr></table>
     <p>
-    An on-again, off-again contributor to wine since around 2002, Greg gets
+    An on-again, off-again contributor to Wine since around 2002, Greg gets
     his patches in in bursts, when he has the time to sit down and do some real
     hacking. He's worked mostly on rpcrt4.dll, rpcss.exe and cabinet.dll.
-    Eventually, Greg would like to see wine talking RPC to real Windows, and
+    Eventually, Greg would like to see Wine talking RPC to real Windows, and
     running MS SQL Server.  Greg works as a computer consultant and programmer 
     in Chicago, IL, mostly doing web programming, .NET, and database
     development.
Index: templates/en/winelib.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/winelib.template,v
retrieving revision 1.15
diff -u -r1.15 winelib.template
--- templates/en/winelib.template	2 Sep 2004 19:09:22 -0000	1.15
+++ templates/en/winelib.template	5 Jan 2005 19:46:01 -0000
@@ -140,7 +140,7 @@
   <i>It is a tex-shell like kde's "kile".</i>
   <ul>
     <li>worker: <a href="mailto:jahn.matthias at freenet.de">Matthias Jahn</a>
-    <li>status: runs with wine, now i try to port it with Winelib
+    <li>status: runs with Wine, now I try to port it with Winelib
     <li>updated: Apr 20, 2003
     <li>homepage: <a href="http://www.toolscenter.org/products/texniccenter/">www.toolscenter.org/products/texniccenter</a>
   </ul>
Index: wwn/wn19990620_1.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn19990620_1.xml,v
retrieving revision 1.2
diff -u -r1.2 wn19990620_1.xml
--- wwn/wn19990620_1.xml	18 Jul 2003 20:50:49 -0000	1.2
+++ wwn/wn19990620_1.xml	5 Jan 2005 21:35:36 -0000
@@ -14,7 +14,7 @@
 goal is to distribute widely what's going on around Wine (the Un*x Windows
 emulator).
 
-<p />Bertho Stultiens annouced that the Wine's CVS server should be up and
+<p />Bertho Stultiens announced that Wine's CVS server should be up and
 running again, after he upgraded the Linux kernel of the server.
 
 </intro>

More information about the wine-patches mailing list