docs/en winedev-debugger.sgml winedev-graphica ...
Francois Gouget
fgouget at users.sourceforge.net
Tue Sep 11 06:50:44 CDT 2007
ChangeSet ID: 118951144495071634424767
CVSROOT: /cvsroot/wine
Module name: docs
Changes by: fgouget at sc8-pr-cvs9.sourceforge.net 2007/09/11 04:50:44
Modified files:
en : winedev-debugger.sgml winedev-graphical.sgml
winedev-kernel.sgml winedev-opengl.sgml
winedev-otherdebug.sgml wineusr-running.sgml
Log message:
Assorted spelling fixes.
Old revision New revision Changes Path
1.5 1.6 +5 -5 docs/en/winedev-debugger.sgml
1.2 1.3 +2 -2 docs/en/winedev-graphical.sgml
1.2 1.3 +2 -2 docs/en/winedev-kernel.sgml
1.3 1.4 +1 -1 docs/en/winedev-opengl.sgml
1.5 1.6 +1 -1 docs/en/winedev-otherdebug.sgml
1.5 1.6 +1 -1 docs/en/wineusr-running.sgml
Index: docs/en/winedev-debugger.sgml
diff -u -p docs/en/winedev-debugger.sgml:1.5 docs/en/winedev-debugger.sgml:1.6
--- docs/en/winedev-debugger.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -408,7 +408,7 @@ winedbg hl.exe -windowed
<para>
You can also set a breakpoint for that function. Start wine
using <command>winedbg</command> instead of
- <command>wine</command>. Once the debugger is is running enter
+ <command>wine</command>. Once the debugger is running enter
<command>break</command> <parameter>KERNEL_LSTRLEN</parameter>
(replace by function you want to debug, CASE IS RELEVANT)
to set a breakpoint. Then
@@ -617,7 +617,7 @@ call KERNEL.LSTRLEN
| |temporary name ~docXXXX.tmp
|Force use of Drive C:.
-|Warning: GetTempFileName returns 'C:~doc9281.tmp', which doesn't seem to be writeable.
+|Warning: GetTempFileName returns 'C:~doc9281.tmp', which doesn't seem to be writable.
|Please check your configuration file if this generates a failure.
</screen>
<para>
@@ -653,7 +653,7 @@ In 32 bit mode.
Wine-dbg>
</screen>
<para>
- The code seems to find a writeable harddisk and tries to create
+ The code seems to find a writable harddisk and tries to create
a file there. To work around this bug, you can define
<medialabel>C:</medialabel> as a networkdrive, which is ignored
by the code above.
@@ -1028,7 +1028,7 @@ winedbg myprog.exe
<term>Auto</term>
<listitem>
<para>
- if this value is zero, a message box will ask the
+ If this value is zero, a message box will ask the
user if he/she wishes to launch the debugger when an
unhandled exception occurs. Otherwise, the debugger
is automatically started.
@@ -1049,7 +1049,7 @@ winedbg myprog.exe
<note>
<title>Note 1</title>
<para>
- creating this key is mandatory. Not doing so will not
+ Creating this key is mandatory. Not doing so will not
fire the debugger when an exception occurs.
</para>
</note>
Index: docs/en/winedev-graphical.sgml
diff -u -p docs/en/winedev-graphical.sgml:1.2 docs/en/winedev-graphical.sgml:1.3
--- docs/en/winedev-graphical.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -25,8 +25,8 @@
In the past, all calls to X used to go through a wrapper called
<function>TSX...()</function> (for "Thread Safe X ...").
While it is still being used in the code, it's inefficient
- as the lock is potentially aquired and released unnecessarily.
- New code should explicitly aquire the lock.
+ as the lock is potentially acquired and released unnecessarily.
+ New code should explicitly acquire the lock.
</para>
</sect2>
</sect1>
Index: docs/en/winedev-kernel.sgml
diff -u -p docs/en/winedev-kernel.sgml:1.2 docs/en/winedev-kernel.sgml:1.3
--- docs/en/winedev-kernel.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -929,7 +929,7 @@ if (res != ERROR_SUCCESS) return res;
expect to be able to crash themselves and recover later without the
user noticing, some contain buggy binary-only components from third
parties and use SEH to swallow crashes, and still others execute
- priviledged (kernel-level) instructions and expect it to work. In
+ privileged (kernel-level) instructions and expect it to work. In
fact, at least one set of APIs (the <function>IsBad*Ptr()</function>
series) can only be implemented by performing an operation that may
crash and returning <constant>TRUE</constant> if it does, and
@@ -2589,7 +2589,7 @@ if (res != ERROR_SUCCESS) return res;
not possible (like when someone else is already using this area), the
DOS support is not possible. Not also that by doing so, access to
linear address 0 is enabled (as it's also real mode address 0 which is
- valid). Hence, NULL pointer derefence faults are no longer catched.
+ valid). Hence, NULL pointer dereference faults are no longer caught.
</para>
</sect2>
</sect1>
Index: docs/en/winedev-opengl.sgml
diff -u -p docs/en/winedev-opengl.sgml:1.3 docs/en/winedev-opengl.sgml:1.4
--- docs/en/winedev-opengl.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -175,7 +175,7 @@
The first is the path to the OpenGL registry. Now, you
will all ask 'but what is the OpenGL registry ?' :-)
Well, it's part of the OpenGL sample implementation
- source tree from SGI (more informations at this URL :
+ source tree from SGI (more information at this URL :
<ulink url="http://oss.sgi.com/projects/ogl-sample/">
http://oss.sgi.com/projects/ogl-sample/</ulink>.
</para>
Index: docs/en/winedev-otherdebug.sgml
diff -u -p docs/en/winedev-otherdebug.sgml:1.5 docs/en/winedev-otherdebug.sgml:1.6
--- docs/en/winedev-otherdebug.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -19,7 +19,7 @@
</para>
<para>
Presuming that you have compiled and installed wine the first
- thing to do is is to enable direct hardware access to your
+ thing to do is to enable direct hardware access to your
parallel port. To do this edit <filename>config</filename>
(usually in <filename>~/.wine/</filename>) and in the
ports section add the following two lines
Index: docs/en/wineusr-running.sgml
diff -u -p docs/en/wineusr-running.sgml:1.5 docs/en/wineusr-running.sgml:1.6
--- docs/en/wineusr-running.sgml 11 Sep 2007 11:50:44 -0000
+++ /dev/null 11 Sep 2007 11:50:44 -0000
@@ -306,7 +306,7 @@ Path="c:\windows;c:\windows\system;e:\;e
<prompt>$</prompt> <userinput>WINEDLLOVERRIDES="ole32,oleaut32,rpcrt4=n" wine <replaceable>program_name</replaceable></userinput>
</screen>
<para>
- For more informations about DLL overrides, please refer to the <link
+ For more information about DLL overrides, please refer to the <link
linkend="winecfg-dll-overrides">DLL overrides</link> section of this guide.
</para>
</sect2>
More information about the wine-cvs
mailing list