Module: docs Branch: master Commit: 0b01467a56abee4062ff996a0e3cd67b173d9fff URL: http://source.winehq.org/git/docs.git/?a=commit;h=0b01467a56abee4062ff996a0e...
Author: André Hentschel nerv@dawncrow.de Date: Wed Feb 16 19:08:56 2011 +0100
wineusr: Fix more typos.
As spotted by Andrew Singleton.
---
en/wineusr-configuring.sgml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/en/wineusr-configuring.sgml b/en/wineusr-configuring.sgml index 6bfc27e..56f7923 100644 --- a/en/wineusr-configuring.sgml +++ b/en/wineusr-configuring.sgml @@ -294,7 +294,7 @@ see buttons to add and remove available drives. When you choose to add a drive, a new entry will be made and a default drive mapping will appear. You can change where - this drives points to by changing what's in the + this drive points to by changing what's in the <emphasis>Path:</emphasis> box. If you're unsure of the exact path you can choose "Browse" to search for it. Removing a drive is as easy as selecting the drive and @@ -390,13 +390,13 @@ of applications and the operating system. Likewise, Wine implements a registry and some settings not found in Winecfg can be changed within it. (There's actually more of a chance - you'll need to dip into the registry to change an applications' + you'll need to dip into the registry to change an application's settings than Wine itself.) </para> <para> Now, the fact that Wine itself uses the registry to store settings has been controversial. Some people argue that it's too much like - Windows. To counter this, there's several things to consider. + Windows. To counter this there are several things to consider. First, it's impossible to avoid implementing a registry simply because applications expect to be able to store their settings there. In order for Wine to store and access settings in a separate