--- a/src/site/markdown/java-settings.md	Mon Sep 02 19:32:44 2013 +0200
+++ b/src/site/markdown/java-settings.md	Wed Sep 04 09:08:17 2013 +0200
@@ -9,15 +9,15 @@
 server.
 
 The amount of memory Tomcat (version 5.0) uses is configured by creating a
-"setenv.sh" script with a line
+`setenv.sh` (or `setenbv.bat`) script with a line
 
     CATALINA_OPTS="-Xmx512m"
 
-in Tomcat's `bin` directory (giving 512MB in this case).
+in Tomcat's `bin` directory (giving 512MB RAM in this case).
 
 You can check the amount of memory your digilib instance has available on the
 bottom of the web page `/server/dlConfig.jsp` in your digilib instance (e.g. 
-[http://digilib.mpiwg-berlin.mpg.de/digitallibrary/server/dlConfig.jsp](http://digilib.mpiwg-berlin.mpg.de/digitallibrary/server/dlConfig.jsp)).
+<http://localhost:8080/digilib/server/dlConfig.jsp>
 
 # Installing JAI ImageIO
 
@@ -29,34 +29,27 @@
 
 You can see if the Jai-ImageIO plugin is active by checking for the 
 availability of the TIFF image format under "Supported image types" on the 
-[`/server/dlConfig.jsp`](http://digilib.mpiwg-berlin.mpg.de/digitallibrary/server/dlConfig.jsp)
+[`/server/dlConfig.jsp`](http://localhost:8080/digilib/server/dlConfig.jsp)
 status page.
 
-But sometimes there are classloader issues. Newer versions of Tomcat refuse to load
+Sometimes there are memory issues. Newer versions of Tomcat refuse to load
 the libraries and I found that in some cases digilib stopped reading TIFF files
-after a period of running.
-
-In these cases it helped to install the JAI files in Tomcats `lib/`
-directory or globally in the local Java JDK
+after a period of running. In these cases it helped to install the JAI files in 
+Tomcats `lib/` directory or globally in the local Java JDK
 installation (i.e. in the Java's 'jre/lib/ext/' directory on linux).
 
 # Sample setup
 
 The current digilib setup at the MPIWG (as of December 2010):
 
-*   One frontend server running the lightweight web-multiplexer [pound](http://www.apsis.ch/pound/)
-            on port 80 that distributes requests to three servers runnning digilib
-*   the three servers run digilib under [Jetty](http://www.eclipse.org/jetty/) on port 8080 without Apache
-
-        *   one server is the frontend server (Linux 32bit, Dual
-                2.4GHz Xeon, 2GB RAM)
-    *   the other server is a separate, newer machine (Linux 64bit, Dual 1.8GHz
-                Opteron, 2GB RAM)
-    *   the third server is a separate, newer machine (Linux 32bit, Dual 2.8GHz
-                Xeon, 4GB RAM)
-*   the digilib instances (digilib 2.0b1 as of 12.12.2011) run on Jetty 8.0.4 on Java
-            1.6.0_26 with 1GB of [Java VM memory
-              for digilib](#vm_settings) (-Xmx1024m) with JAI (1.1.3) and JAI-ImageIO (1.1) [installed in the Jetty/lib/ext](#installing_jai)(!)
-*   both digilib servers access all image files over NFS (over GBit
-            Ethernet) from a central file server (Solaris 10, Sun Fire 240, multiple RAIDs
-            on Fibrechannel)
\ No newline at end of file
+* One frontend server running the lightweight web-multiplexer [pound](http://www.apsis.ch/pound/)
+    on port 80 that distributes requests to three servers runnning digilib
+* the three servers run digilib under [Jetty](http://www.eclipse.org/jetty/) on port 8080 without Apache
+   * one server is the frontend server (Linux 32bit, Dual 2.4GHz Xeon, 2GB RAM)
+   * the other server is a separate, newer machine (Linux 64bit, Dual 1.8GHz Opteron, 2GB RAM)
+   * the third server is a separate, newer machine (Linux 32bit, Dual 2.8GHz Xeon, 4GB RAM)
+* the digilib instances (digilib 2.0b1 as of 12.12.2011) run on Jetty 8.0.4 on Java
+   1.6.0_26 with 1GB of Java VM memory for digilib (-Xmx1024m) with JAI (1.1.3) and JAI-ImageIO (1.1)
+   installed in `Jetty/lib/ext`
+* both digilib servers access all image files over NFS (over GBit Ethernet) from a central file server 
+   (Solaris 10, Sun Fire 240, multiple RAIDs on Fibrechannel)
\ No newline at end of file