[docs] winedev: Update architecture chapter

[André Hentschel]

---
 en/winedev-architecture.sgml | 20 +++++++-------------
 1 file changed, 7 insertions(+), 13 deletions(-)

diff --git a/en/winedev-architecture.sgml b/en/winedev-architecture.sgml
index bb8638b..9baf0db 100644
--- a/en/winedev-architecture.sgml
+++ b/en/winedev-architecture.sgml
@@ -218,8 +218,8 @@
 	  exist, as Windows has support for different VDM (Virtual Dos
 	  Machines) in order to have Win16 processes running in different
 	  address spaces. Wine also uses the same architecture to run DOS
-	  programs (in this case, the DOS emulation is provided by a Wine only
-	  DLL called <filename>winedos</filename>.
+	  programs (in this case, the DOS emulation is provided by
+	  <filename>KRNL386.EXE</filename>).
 	</para>
       </sect2>
     </sect1>
@@ -368,7 +368,7 @@
 +---------------------------------------+  +--------+
 
 +---------------------------------------+               \
-|   Wine executable (wine-?thread)      |                } unix executable
+|            Wine executable            |                } unix executable
 +---------------------------------------+               /
 +---------------------------------------------------+   \
 |                   Wine drivers                    |    } Wine specific DLLs
@@ -418,7 +418,7 @@
 	  provide a driver (in Windows sense) to a physical hardware
 	  device. This driver will be a proxy to the Unix driver
 	  (this is the case, for example, for the graphical part
-	  with X11 or SDL drivers, audio with OSS or ALSA drivers...).
+	  with X11 or Mac drivers, audio with OSS or ALSA drivers...).
 	</para>
 	<para>
 	  All DLLs provided by Wine try to stick as much as possible
@@ -452,12 +452,7 @@
 	  terminated).
 	</para>
 	<para>
-	  In earlier versions of Wine the master socket mentioned
-	  above was actually created in the configuration directory;
-	  either your home directory's <filename>/wine</filename>
-	  subdirectory or wherever the
-	  <envar>WINEPREFIX</envar> environment variable points>.
-	  Since that might not be possible the socket is actually
+	  The master socket mentioned above is actually
 	  created within the <filename>/tmp</filename> directory
 	  with a name that reflects the configuration directory.
 	  This means that there can actually be several separate
@@ -545,8 +540,7 @@
 	</para>
 	<para>
 	  The DLL descriptor and entry point table is generated by
-	  the <command>winebuild</command> tool (previously just
-	  named <command>build</command>), taking DLL specification
+	  the <command>winebuild</command> tool, taking DLL specification
 	  files with the extension <filename>.spec</filename> as
 	  input. Resources (after compilation by
 	  <command>wrc</command>) or message tables (after
@@ -730,7 +724,7 @@
 	    work much worse than the corresponding built-in one, if at
 	    all. For example, the native Windows <filename>GDI</filename>
 	    library must be paired with a Windows display driver, which
-	    of course is not present under Intel Unix and Wine.
+	    of course is not present under Unix and Wine.
 	  </para>
 	  <para>
 	    Finally, occasionally built-in Wine DLLs implement more
-- 
1.8.1.2