fix(rdb): review jess

Co-authored-by: Jessica <[email protected]>

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx

@@ -79,7 +79,7 @@ We recommend you remove the identified instances before continuing.
         - Run the migration without checking the "migration endpoint" flag. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime.
         - Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints.
     </Message>
-5. Click **Upgrade version**. A new Database Instance is created.
+6. Click **Upgrade version**. A new Database Instance is created.
 
     <Message type="important">
       - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions on each database they are installed once the upgrade is complete.