Changelog:
* dlls/cabinet/fdi.c,
dlls/dmloader/loader.c,
documentation/faq.sgml
A few spelling fixes.
Index: dlls/cabinet/fdi.c
===================================================================
RCS file: /home/wine/wine/dlls/cabinet/fdi.c,v
retrieving revision 1.14
diff -u -r1.14 fdi.c
--- dlls/cabinet/fdi.c 18 Aug 2003 19:50:14 -0000 1.14
+++ dlls/cabinet/fdi.c 4 Sep 2003 08:09:45 -0000
@@ -2166,7 +2166,7 @@
* pfdin. The only part of that structure which is assigned for every callback
* is the pv element, which contains the arbitrary value which was passed to
* FDICopy in the pvUser argument (psz1 is also used each time, but its meaning
- * is highly dependant on fdint).
+ * is highly dependent on fdint).
*
* If you encounter unknown notifications, you should return zero if you want
* decompression to continue (or -1 to abort). All strings used in the
Index: dlls/dmloader/loader.c
===================================================================
RCS file: /home/wine/wine/dlls/dmloader/loader.c,v
retrieving revision 1.2
diff -u -r1.2 loader.c
--- dlls/dmloader/loader.c 22 Aug 2003 23:53:28 -0000 1.2
+++ dlls/dmloader/loader.c 4 Sep 2003 08:09:51 -0000
@@ -179,7 +179,7 @@
desc.dwSize = sizeof (DMUS_OBJECTDESC);
IDirectMusicObject_GetDescriptor (pObject, &desc);
- /* tests with native dlls show that descriptor, which is recieved by GetDescriptor doesn't contain filepath
+ /* tests with native dlls show that descriptor, which is received by GetDescriptor doesn't contain filepath
therefore we must copy it from input description */
if (pDesc->dwValidData & DMUS_OBJ_FILENAME || desc.dwValidData & DMUS_OBJ_OBJECT) {
DMUS_PRIVATE_CACHE_ENTRY CacheEntry;
Index: documentation/faq.sgml
===================================================================
RCS file: /home/wine/wine/documentation/faq.sgml,v
retrieving revision 1.19
diff -u -r1.19 faq.sgml
--- documentation/faq.sgml 2 Sep 2003 18:19:09 -0000 1.19
+++ documentation/faq.sgml 4 Sep 2003 07:26:49 -0000
@@ -160,7 +160,7 @@
on non-x86 platforms: run both Wine and the application inside the
CPU emulator. As long as the emulator provides a standard Unix
environment, Wine should only need minimal modifications. What
- performance you loose due to Wine running inside the emulator
+ performance you lose due to Wine running inside the emulator
rather than natively, you gain in complexity inside of Wine.
Furthermore, if the emulator is fast enough to run Windows
applications, Photoshop for instance, then it should be fast enough
@@ -1343,7 +1357,7 @@
<qandaentry>
<question id="bash-wine-Command-not-found-What-can-I-do">
- <para>bash "wine: Command not found" What can I do?</para>
+ <para>bash says "wine: Command not found" What can I do?</para>
</question>
<answer>
<para>
--
Francois Gouget fgouget@free.fr http://fgouget.free.fr/
The software said it requires Win95 or better, so I installed Linux.
