[docs] wineusr: Assorted spelling fixes
Frédéric Delanoy
frederic.delanoy at gmail.com
Mon Jul 1 09:24:40 CDT 2013
---
en/wineusr-bugs.sgml | 34 +++++++++++++++++-----------------
en/wineusr-configuring.sgml | 16 ++++++++--------
en/wineusr-running.sgml | 6 +++---
3 files changed, 28 insertions(+), 28 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml
index b7df91e..4ed4f99 100644
--- a/en/wineusr-bugs.sgml
+++ b/en/wineusr-bugs.sgml
@@ -10,7 +10,7 @@
while doing the Devil's Dance, yet nothing helped to make some damn
program work on some Wine version.
Don't despair, we're here to help you...
- (in other words: how much do you want to pay ?)
+ (in other words: how much do you want to pay?)
</para>
<sect2>
@@ -18,10 +18,10 @@
<para>
Look at the output from <prompt>$ </prompt>
<userinput>wine --version</userinput> to make sure you're running
- a recent version of Wine. Launch winecfg and look over the
+ a recent version of Wine. Launch winecfg and look over the
settings to make sure you have settings that look normal. Look
- in <filename>~/.wine/dosdevices</filename> to make sure you're
- c: points to where you think it should.
+ in <filename>~/.wine/dosdevices</filename> to make sure your
+ c: points to where you think it should.
</para>
</sect2>
@@ -62,11 +62,11 @@
</sect2>
<sect2>
- <title>Check your system environment !</title>
+ <title>Check your system environment!</title>
<para>
Just an idea: could it be that your Wine build/execution
- environment is broken ?
+ environment is broken?
Make sure that there are no problems whatsoever with the
packages
@@ -84,10 +84,10 @@
</sect2>
<sect2>
- <title>Check your app !</title>
+ <title>Check your app!</title>
<para>
- Maybe your app is using some kind of copy protection ?
+ Maybe your app is using some kind of copy protection?
Many copy protections currently don't work on Wine.
Some might work in the future, though.
@@ -125,7 +125,7 @@
<itemizedlist>
<listitem>
<para>
- Search <ulink url="http://appdb.winehq.org">WineHQ's
+ Search <ulink url="http://appdb.winehq.org">WineHQ
Application Database</ulink> to check for any tips
relating to the program. If your specific version of
the program isn't listed you may find a different one
@@ -152,7 +152,7 @@
<listitem>
<para>
If you have a program that requires a redistributable runtime
- to be installed, eg for mfc42.dll, Visual Basic and so on, winetricks
+ to be installed, e.g. for mfc42.dll, Visual Basic and so on, winetricks
can be used to supply this. Note, these components are subject to
their own license and are not part of the Wine project.
@@ -161,7 +161,7 @@
</listitem>
<listitem>
<para>
- Wine's <ulink url="http://www.winehq.org/site/forums#ml">mailing
+ Wine <ulink url="http://www.winehq.org/site/forums#ml">mailing
lists</ulink> may also help, especially wine-users. The
wine-devel list may be appropriate depending on the type of
problem you are experiencing. If you post to wine-devel you
@@ -187,9 +187,9 @@
Finding the source of your problem is the next step to take.
There is a wide spectrum of possible problems
ranging from simple configurations issues to completely unimplemented
- functionality in Wine. The next section will describe how to
+ functionality in Wine. The next section will describe how to
file a bug report and how to begin debugging a crash. For more
- information on using Wine's debugging facilities be sure to read
+ information on using Wine debugging facilities be sure to read
the Wine Developers Guide.
</para>
</sect2>
@@ -232,7 +232,7 @@
<listitem>
<para>
The name of the Operating system you're using, what distribution (if
- any), and what version. (i.e., Linux Red Hat 7.2)
+ any), and what version (e.g. Linux Red Hat 7.2).
</para>
</listitem>
<listitem>
@@ -252,7 +252,7 @@
<listitem>
<para>
The exact command line you used to start wine.
- (i.e., <command>wine "C:\Program Files\Test\program.exe"</command>).
+ (e.g. <command>wine "C:\Program Files\Test\program.exe"</command>).
</para>
</listitem>
<listitem>
@@ -265,7 +265,7 @@
<para>
Useful terminal output
contains a backtrace with debug symbols, see the
- <ulink url="http://wiki.winehq.org/Backtraces">Backtraces wiki entry</ulink>
+ <ulink url="http://wiki.winehq.org/Backtraces">Backtraces wiki entry</ulink>.
</para>
</listitem>
<listitem>
@@ -294,7 +294,7 @@
<listitem>
<para>
You may be asked to re-run the program with the WINEDEBUG environment variable <parameter>
- WINEDEBUG=+relay,+seh,+tid</parameter> option (i.e., <command>WINEDEBUG=+relay,+seh,+tid
+ WINEDEBUG=+relay,+seh,+tid</parameter> option (e.g. <command>WINEDEBUG=+relay,+seh,+tid
wine sol.exe &> log.txt</command>).
</para>
<para>
diff --git a/en/wineusr-configuring.sgml b/en/wineusr-configuring.sgml
index ddc896e..0db8eed 100644
--- a/en/wineusr-configuring.sgml
+++ b/en/wineusr-configuring.sgml
@@ -81,7 +81,7 @@
Note: The Applications, Libraries, and Graphics tabs are linked
together! If you have Default Settings selected under Applications,
all of the changes made within the Libraries and Graphics tabs will
- be changed for all applications. If you've configured a specfic
+ be changed for all applications. If you've configured a specific
application under the Applications tab and have it selected, then
any changes made in Libraries or Graphics will affect only that
application. This allows for custom settings for specific
@@ -247,7 +247,7 @@
<para>
The first setting primarily affect games and is somewhat
self-explanatory. You can prevent the mouse from leaving the
- window of a full-screen program (i.e. a game.) and the default
+ window of a full-screen program (e.g. a game) and the default
is to not have that box checked. That is mostly needed when using
a virtual desktop.
</para>
@@ -375,7 +375,7 @@
because applications expect to be able to store their settings there.
In order for Wine to store and access settings in a separate
configuration file would require a separate set of code to basically
- do the same thing as the Win32 API's Wine already implements.
+ do the same thing as the Win32 APIs Wine already implements.
</para>
<sect2>
<title>Registry Structure</title>
@@ -627,7 +627,7 @@
</programlisting>
to make it available in wine (don't forget to create the unc
- directory if it doesn't alrady exist).
+ directory if it doesn't already exist).
</para>
</sect2>
<sect2>
@@ -644,9 +644,9 @@
<para>
Wine can interact directly with the local CUPS printing system to
find the printers available on your system. Configuring
- printers with Wine is as simple as making sure your CUPS
+ printers with Wine is as simple as making sure your CUPS
configuration works. Wine still needs the command
- <userinput>lpr</userinput>(from CUPS), when printing a Document.
+ <userinput>lpr</userinput> (from CUPS), when printing a document.
</para>
<para>
If you do not use CUPS, the old BSD-Printing system is used:
@@ -663,7 +663,7 @@
</listitem>
<listitem>
<para>
- The command <userinput>lpr</userinput> is called when printing a Document
+ The command <userinput>lpr</userinput> is called when printing a document
</para>
</listitem>
</itemizedlist>
@@ -741,7 +741,7 @@
before running wine to trace what is happening. One word of
warning. Some programs actually cheat a little and bypass the ODBC
library. For example the Crystal Reports engine goes to the registry
- to check on the DSN. The fix for this is documented at unixODBC's
+ to check on the DSN. The fix for this is documented at unixODBC
site where there is a section on using unixODBC with Wine.
</para>
</sect3>
diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml
index a1d7022..95416a6 100644
--- a/en/wineusr-running.sgml
+++ b/en/wineusr-running.sgml
@@ -242,7 +242,7 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
<title>WINEDLLOVERRIDES=[DLL Overrides]</title>
<para>
It's not always possible to run an application on builtin
- DLL's. Sometimes native DLL's simply work better. Altough
+ DLLs. Sometimes native DLLs simply work better. Although
these DLL overrides can be set using winecfg you might want
to use the WINEDLLOVERRIDES environment variable to set them.
</para>
@@ -478,7 +478,7 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
</itemizedlist>
</para>
<para>The names here are a bit obscure. "bare streams" means
- that no extra support of wine is provide to map between the
+ that no extra support of wine is provided to map between the
unix console access and Windows console access. The two other
ways require the use of a specific Wine program (wineconsole)
which provide extended facilities. The following table
@@ -688,7 +688,7 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
window is always smaller or of the same size than
the screen buffer. Having a strictly smaller window
size will put on scrollbars on the window so that
- you can see the whole screenbuffer's content.
+ you can see the whole screenbuffer content.
</entry>
</row>
<row>
--
1.8.2
More information about the wine-patches
mailing list