--no commit message

--no commit message

h2/src/docsrc/html/roadmap.html

@@ -127,7 +127,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Default date format for input and output (local date constants).
 </li><li>Support custom Collators.
 </li><li>Document ROWNUM usage for reports: SELECT ROWNUM, * FROM (subquery).
-</li><li>MS SQL Server compatibility: support 1+'2'=3, '1'+'2'='12'
+</li><li>MS SQL Server compatibility: support string concatenation using +: 1+'2'=3, '1'+'2'='12'
 </li><li>Clustering: when a database is back alive, automatically synchronize with the master.
 </li><li>File system that writes to two file systems (replication, replicating file system).
 </li><li>Standalone tool to get relevant system properties and add it to the trace output.

h2/src/docsrc/html/tutorial.html

@@ -631,9 +631,10 @@ need to be available on the server side.
 <p>
 The <code>BACKUP</code> SQL statement and the <code>Backup</code> tool both create a zip file
 with all database files. However, the contents of this file are not human readable.
-Other than the SCRIPT statement, the <code>BACKUP</code> statement does not lock the
-database objects, and therefore does not block other users. The resulting
-backup is transactionally consistent:
+</p><p>
+Unlike than the SCRIPT statement, the <code>BACKUP</code> statement does not lock the
+database objects when using the multi-threaded mode, and therefore does not block other users. 
+The resulting backup is transactionally consistent:
 </p>
 <pre>
 BACKUP TO 'backup.zip'
@@ -643,8 +644,8 @@ The <code>Backup</code> tool (<code>org.h2.tools.Backup</code>) can not be used
 the database must not be in use while running this program.
 </p>
 <p>
-Creating a backup while the database is running is not supported, except
-if the file systems support creating snapshots. The problem is that it can't
+Creating a backup by copying the database files while the database is running is not supported, 
+except if the file systems support creating snapshots. The problem is that it can't
 be guaranteed that the data is copied in the right order.
 </p>
 

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

@@ -636,4 +636,5 @@ jdt continuation codegen parenthesized tabulation ellipsis imple inits guardian
 postfix iconified deiconified deactivated activated worker frequent utilities
 workers appender recovers balanced serializing breaking austria wildam
 census genealogy scapegoat gov compacted migrating dies typtypmod latch await
-counting dtest fallback infix places formal extern 
+counting dtest fallback infix places formal extern destination stdout memmove
\ No newline at end of file
+stdio printf
\ No newline at end of file