fix(rdb): review hugo2

Author: ldecarvalho-doc

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

@@ -75,7 +75,7 @@ We recommend you remove the identified instances before continuing.
 
     <Message type="tip">
       Before performing an engine upgrade migration, we recommend testing the process in a "dry-run". This allows you to estimate the migration time and verify its success without affecting your source instance. To do so:
-        - Run the migration without checking the "migration endpoint" flag. This will simulate the migration process. 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.
+        - 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>
 4. Click **Upgrade version**. A new Database Instance is created.