diff --git a/conf/config.yaml b/conf/config.yaml
index c294539..4f40caa 100644
--- a/conf/config.yaml
+++ b/conf/config.yaml
@@ -2,7 +2,7 @@
 homeserver:
     # The address that this appservice can use to connect to the homeserver.
     address: https://__DOMAIN__
-    # The domain of the homeserver (for MXIDs, etc).
+    # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
     domain: __SERVER_NAME__
 
     # What software is the homeserver running?
@@ -29,11 +29,12 @@ appservice:
 
     # Database config.
     database:
-        # The database type. "sqlite3" and "postgres" are supported.
+        # The database type. "sqlite3-fk-wal" and "postgres" are supported.
         #type: sqlite3
         type: postgres
         # The database URI.
-        #   SQLite: File name is enough. https://github.com/mattn/go-sqlite3#connection-string
+        #   SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
+        #           https://github.com/mattn/go-sqlite3#connection-string
         #   Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
         #             To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
         uri: postgres://__APP__:__DB_PWD__@localhost:5432/__DB_NAME__
@@ -301,6 +302,8 @@ bridge:
     # Send captions in the same message as images. This will send data compatible with both MSC2530 and MSC3552.
     # This is currently not supported in most clients.
     caption_in_message: false
+    # Should polls be sent using MSC3381 event types?
+    extev_polls: false
     # Should Matrix edits be bridged to WhatsApp edits?
     # Official WhatsApp clients don't render edits yet, but once they do, the bridge should work with them right away.
     send_whatsapp_edits: false