Index: pages/pragma.in
==================================================================
--- pages/pragma.in
+++ pages/pragma.in
@@ -1173,13 +1173,19 @@
     <dd>
     ^When synchronous is NORMAL (1), the SQLite database
     engine will still sync at the most critical moments, but less often
     than in FULL mode.  There is a very small (though non-zero) chance that
     a power failure at just the wrong time could corrupt the database in
-    NORMAL mode.  But in practice, you are more likely to suffer
-    a catastrophic disk failure or some other unrecoverable hardware
-    fault.  Many applications choose NORMAL when in [WAL mode].</dd>
+    [journal_mode]=DELETE on an older filesystem.
+    [WAL mode] is safe from corruption with synchronous=NORMAL, and probably
+    DELETE mode is safe too on modern filesystems.  WAL mode is always consistent
+    with synchronous=NORMAL, but WAL mode does lose durability.  A transaction
+    committed in WAL mode with synchronous=NORMAL might roll back following
+    a power loss or system crash.  Transactions are durable across application
+    crashes regardless of the synchronous setting or journal mode.
+    The synchronous=NORMAL setting is a good choice for most applications
+    running in [WAL mode].</dd>
     <dt><b>OFF</b> (0)</dt>
     <dd>
     ^With synchronous OFF (0), SQLite continues without syncing
     as soon as it has handed data off to the operating system.
     If the application running SQLite crashes, the data will be safe, but

Index: pages/sqlar.in
==================================================================
--- pages/sqlar.in
+++ pages/sqlar.in
@@ -119,10 +119,20 @@
 ([https://sqlite.org/src/file/ext/misc/sqlar.c]) to handle the compression
 and decompression of content.  Even this tiny extension can be omitted
 if the files in the archive are uncompressed.  In contrast, supporting
 ZIP Archives and/or Tarballs requires either separate libraries or
 lots of extra custom code, or sometimes both.
+
+<li><p>
+An SQLite Archive can work around firewall-imposed censorship.
+For example, certain file types that are considered "dangerous" 
+(examples: DLLs) will be
+[https://support.google.com/mail/answer/6590|blocked by Gmail]
+and probably many other email services and firewall, even if those
+files are wrapped inside a ZIP Archive or Tarball.
+But these firewall usually do not care about SQLite Archives and
+so content can be put inside an SQLite Archive to evade censorship.
 </ol>
 
 <h1>Disadvantages Of SQLite Archives</h1>
 
 <ol>