Update backup-and-restore.html.markerb

fix typo

postgres/managing/backup-and-restore.html.markerb

@@ -85,7 +85,8 @@ vs_OPQXXna6kA2Qnhz8 26 MiB 2 days ago
 The values under the `ID` columns are what will be used to restore a snapshot.
 
 ## Identifying your Postgres image version
-Depending on when you created your Postgres cluster, it may be running an older image than the default for newly clusters. Different Postgres major versions may not be fully compatible, so it's important to use the same version for your restored cluster.
+Depending on when you created your Postgres cluster, it may be running an older image than the default for newly created clusters. Different Postgres major versions may not be fully compatible, so it's important to use the same version for your restored cluster.
+
 To see your Postgres image and version, run `fly image show`. 
 
 ```cmd
@@ -95,7 +96,8 @@ fly image show -a <postgres-app-name>
 MACHINE ID      REGISTRY                REPOSITORY      TAG     VERSION DIGEST                        LABELS                                                                          
 e286004f696700  registry-1.docker.io    flyio/postgres  14.6    v0.0.41 sha256:3c25db96357a78e827ca7d fly.app_role=postgres_clusterfly.pg-version=14.6-1.pgdg110+1fly.version=v0.0.41
 ```
-Take note of the REPOSITORY and TAG fields. Legacy postgres images use the `flyio/postgres` repository, while new Postgres Flex images use the flyio/`postgres-flex` repository. In the above example, the machine is running a legacy `flyio/postgres:14.6` image.
+The values under the `REPOSITORY and `TAG columns are the image you'll use to restore the snapshot. 
+Legacy postgres images use the `flyio/postgres` repository, while new Postgres Flex images use the flyio/`postgres-flex` repository. In the above example, the machine is running a legacy `flyio/postgres:14.6` image.
 
 ## Restoring from a snapshot