Adding the section describing prefixes and the configuration of WINE with the winecfg utility.
I like the writing (content, size, well written). We just need to fix a few style things, then it is ready.
Nothing major really, I've included a couple of links to the FDP primer.
Is there a "that" missing between "applications" and "run"?
You can replace the > with > and the < with < here.
update -> updates
and "will" automatically update
You can mark them up as directories as described in section 9.6.6 here:
The & can also be safely replaced with &.
These <emphasis> tags would better be replaced with <filename>.
You can mark "drive_c" up with <filename> as well.
You can use <varname> here instead of <emphasis>.
Yes, this is a correctly indented <para>. The lines below align under the first "a" of <para>.
Sentences need to start right after <para>. The closing </para> also needs to be right after the last word of the sentence. If that should be too long, then break the whole word (with </para> right behind it) into the next line.
Another <filename> markup here for dosdevices/.
Also, you don't need to provide <directory> here, since it is clear from the markup (and the / at the end). See the /etc/rc.local example here:
Use <filename> tags around /mnt/cdrom
There is a superfluous space after "Browse" and the closing tag.
Updates per feedback, a couple of outstanding questions.
I can add it, although the connotation is actually "applications that have been run through WINE," a structure which I usually shorten to just the verb.
@bcr, can you clarify the fix to be made here? I did move the closing </para> up to the previous line (which was also missing a colon), is there something else?
OK, this looks better. Just a few more things to flesh out before it's ready.
OK, that makes sense to me. Then leave it as it is.
They're still in the updated patch.
See here on how the <para> tags should be used and aligned:
It seems that the </para> still needs to be moved up right after &os; to look like this: &os;</para>
If you have FreeBSD, you can install textproc/igor and run "igor chapter.xml" over it. It will tell you some of the common style errors and suggests fixes.