diff --git a/postgres/managing/upgrades.html.markerb b/postgres/managing/upgrades.html.markerb
index d3fe8ca70e..e4b5dafa8c 100644
--- a/postgres/managing/upgrades.html.markerb
+++ b/postgres/managing/upgrades.html.markerb
@@ -20,7 +20,7 @@ And upgrade with:
 fly image update -a <postgres-app-name>
 ```
 
-The update only works if the major Postgres version in your existing Postgres app matches that in the newest Postgres app release, for example `postgres-flex:15.2` to `postgres-flex:15.3`.
+By default, `fly image update` does not change your image tag. It resolves the same repository and tag your Machines already use (for example `flyio/postgres-flex:15.2`) and updates them to the latest image Fly publishes for that ref—usually a newer digest or build on that tag. To use a different tag (for example moving from `:15.2` to `:15.3`), set the image explicitly with [`fly image update --image`](/docs/flyctl/image-update/).
 
 Upgrading Postgres across major versions is more complicated, and right now the way to do this is to provision a new cluster and restore a backup of your database data into it.