Add more clarifications.

Author: rkistner

self-hosting/lifecycle-maintenance.mdx

@@ -86,7 +86,9 @@ server {
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 
-        # Disable proxy buffering - important for HTTP streaming connections (configured in the PowerSync client SDK)
+        # Disable proxy response buffering.
+        # This is not relevant for websocket connections, but is important when using
+        # HTTP streaming connections (configured in the PowerSync client SDK).
         proxy_buffering off;
     }
 }
@@ -104,9 +106,11 @@ If the load balancer supports health checks, it may be configured to poll the AP
 
 ### Migrations
 
+Occasionally, new versions of the PowerSync service image may require migrations on the underlying storage database. This is also specifically required the first time the service starts up on a new storage database.
+
 By default, migrations are run as part of the replication and API containers. In some cases, a migration may add signifant delay to the container startup.
 
-To avoid this, the migrations may be run as a separate job on each update, before replacing the rest of the containers. To run the migrations, run the docker command `migrate up`, for example `docker run powersync migrate up`.
+To avoid this startup delay, the migrations may be run as a separate job on each update, before replacing the rest of the containers. To run the migrations, run the docker command `migrate up`, for example `docker run powersync migrate up`.
 
 In this case, disable automatic migrations in the config:
 
@@ -119,6 +123,9 @@ migrations:
     disable_auto_migration: true
 ```
 
+Note that if you disable automatic migrations, and do not run the migration job manually,
+the service may run with an outdated storage schema version. This may lead to unexpected and potentially difficult-to-debug errors in the service.
+
 ## Backups
 
 We recommend using Git to backup your configuration files.