diff --git a/docs/404.html b/docs/404.html
index fd2dfac8..582bad3e 100644
--- a/docs/404.html
+++ b/docs/404.html
@@ -4,6 +4,7 @@ title: Page not found
 permalink: /404
 nav_exclude: true
 search_exclude: true
+sitemap: false
 exclude: true
 ---
 
diff --git a/docs/_includes/head.html b/docs/_includes/head.html
index e3d8dd80..7c96b731 100644
--- a/docs/_includes/head.html
+++ b/docs/_includes/head.html
@@ -11,8 +11,6 @@
     <meta name="Description" content="{{ page.description }}">
     {% endif %}
 
-    <link rel="shortcut icon" href="{{ "favicon.ico" | absolute_url }}" type="image/x-icon">
-
     <link rel="stylesheet" href="{{ "/assets/css/just-the-docs.css" | absolute_url }}">
 
     {% if site.search_enabled != nil %}
diff --git a/docs/docs/transactions.md b/docs/docs/transactions.md
index 25fb2324..37d50298 100644
--- a/docs/docs/transactions.md
+++ b/docs/docs/transactions.md
@@ -33,30 +33,15 @@ There are a couple of things that should be kept in mind when working with trans
 1. __Await all calls__: All queries inside the transaction must be `await`-ed. The transaction
   will complete when the inner method completes. Without `await`, some queries might be operating
   on the transaction after it has been closed!
-2. __Don't run calls on your database__: Inside a transaction function, all queries must
-  be on the transaction itself.
-  ```dart
-await transaction((t) async {
-  // BAD - this will run on the database itself!
-  await delete(categories).delete(category);
-});
-await transaction((t) async {
-  // GOOD!
-  await t.delete(categories).delete(category);
-});
-  ```
-  The reason behind this is that no calls can operate on the database while it's in a transaction,
-  they will run after the transaction has completed. When the completion of the transaction can only
-  happen after a call to the database completes, as in the fist example, the database will reach a
-  dead lock!
+2. __No select streams in transactions__: Inside a `transaction` callback, select statements can't
+be `.watch()`ed. The reasons behind this is that it's unclear how a stream should behave when a
+transaction completes. Should the stream complete as well? Update to data changes made outside of the
+transaction? Both seem inconsistent, so moor forbids this.
 
 ## Transactions and query streams
 Query streams that have been created outside a transaction work nicely together with
 updates made in a transaction: All changes to tables will only be reported after the
 transaction completes. Updates inside a transaction don't have an immediate effect on
-streams.
+streams, so your data will always be consistent.
 
-However, streams cannot be created inside transactions! The reason behind that decision
-is that it's unclear what should happen to the stream after the transaction completes.
-Should the stream complete as well? Begin to the updated data outside the transaction?
-To not make things confusing here, this is forbidden.
\ No newline at end of file
+However, as mentioned above, note that streams can't be created inside a `transaction` block.
\ No newline at end of file
diff --git a/docs/docs/web.md b/docs/docs/web.md
index c8bc45cf..28262bdd 100644
--- a/docs/docs/web.md
+++ b/docs/docs/web.md
@@ -38,6 +38,11 @@ Moor web is built on top of the [sql.js](https://github.com/kripken/sql.js/) lib
 You can grab the latest version of `sql-wasm.js` and `sql-wasm.wasm` [here](https://github.com/kripken/sql.js/tree/master/dist)
 and copy them into your `web` folder.
 
+## Gotchas
+The database implementation uses WebAssembly, which needs to be supported by your browser. 
+Also, make sure that your webserver serves the `.wasm` file as `application/wasm`, browsers
+won't accept it otherwise.
+
 ## Sharing code between native apps and web
 If you want to share your database code between native applications and webapps, just import the
 basic `moor` library and make the `QueryExecutor` configurable: