--no commit message

--no commit message

h2/src/test/org/h2/test/todo/supportTemplates.txt

@@ -52,30 +52,31 @@ I am sorry to say that, but it looks like a corruption problem. I am very intere
 
 - Could you send the full stack trace of the exception including message text?
 - What is your database URL?
-- Do you use Tomcat or another web server? Do you unload or reload the web application?
+- Do you use Tomcat or another web server? 
+    Do you unload or reload the web application?
 - You can find out if the database is corrupted when running
     SCRIPT TO 'test.sql'
 - What version H2 are you using?
 - Did you use multiple connections?
 - The first workarounds is: append ;RECOVER=1 to the database URL.
     Does it work when you do this?
-- The second workarounds is: delete the index.db file
-    (it is re-created automatically) and try again. Does it work when you do this?
+- The second workarounds is: delete the index.db file (it is re-created 
+    automatically) and try again. Does it work when you do this?
 - The third workarounds is: use the tool org.h2.tools.Recover to create
     the SQL script file, and then re-create the database using this script.
     Does it work when you do this?
 - With which version of H2 was this database created?
     You can find it out using:
     select * from information_schema.settings where name='CREATE_BUILD'
-- Do you use any settings or special features (for example, the setting LOG=0,
-    or two phase commit, linked tables, cache settings)?
+- Do you use any settings or special features (for example, the setting 
+    LOG=0, or two phase commit, linked tables, cache settings)?
 - Is the application multi-threaded?
 - What operating system, file system, and virtual machine
     (java -version) do you use?
 - Is it (or was it at some point) a networked file system?
 - How big is the database (file sizes)?
-- Is the database usually closed normally, or is process terminated forcefully
-    or the computer switched off?
+- Is the database usually closed normally, or is process terminated 
+    forcefully or the computer switched off?
 - Is it possible to reproduce this problem using a fresh database
     (sometimes, or always)?
 - Are there any other exceptions (maybe in the .trace.db file)?

h2/src/tools/org/h2/build/doc/dictionary.txt

@@ -590,4 +590,4 @@ overall httpdocs tigris eclemma separates underscore yajsw she her truncating
 relocating smtps smtp osde joist catching guesses delimiters shortlist sheet
 rowspan cheat partitioning datepart dreamsource toussi locates fred
 longnvarchar collate localdb nan bootclasspath bcp retrotranslator iterable
-ops
+ops jopr googlegroups