Index: pages/download.in
==================================================================
--- pages/download.in
+++ pages/download.in
@@ -102,10 +102,11 @@
 
 
 Product {snapshot/sqlite-snapshot-DATE.tar.gz} {
   The [amalgamation] source code, the [command-line shell] source code,
   configure/make scripts for unix, and a Makefile.msc for Windows.
+  [https://www.sqlite.org/draft/releaselog/current.html|Change log].
 }
 Product {snapshot/sqlite-amalgamation-DATE.zip} {
   The [amalgamation]: complete source code a single "sqlite3.c" file.
 }
 #  The [amalgamation] as of VERSION.

Index: pages/wal.in
==================================================================
--- pages/wal.in
+++ pages/wal.in
@@ -36,11 +36,11 @@
 <li>All processes using a database must be on the same host computer;
     WAL does not work over a network filesystem.
 <li>Transactions that involve changes against multiple [ATTACH | ATTACHed]
     databases are atomic for each individual database, but are not
     atomic across all databases as a set.
-<li>It is not possible to change the database page size after entering WAL
+<li>It is not possible to change the [page_size] after entering WAL
     mode, either on an empty database or by using [VACUUM] or by restoring
     from a backup using the [backup API].  You must be in a rollback journal
     mode to change the page size.
 <li>It is not possible to open [read-only WAL databases].
     The opening process must have write privileges for "<tt>-shm</tt>"
@@ -55,11 +55,10 @@
     database, which can make SQLite less appealing for use as an 
     [application file-format].
 <li>There is the extra operation of [checkpointing] which, though automatic
     by default, is still something that application developers need to
     be mindful of.
-<li>The [page_size] of the database file cannot be changed while in WAL mode.
 <li><s>WAL works best with smaller transactions.  WAL does
     not work well for very large transactions.  For transactions larger than
     about 100 megabytes, traditional rollback journal modes will likely
     be faster.  For transactions in excess of a gigabyte, WAL mode may 
     fail with an I/O or disk-full error.