Skip to content

Commit 913a6d1

Browse files
Merge pull request #208828 from hariramt/task/208244Review
Corrected minor typo from PR:208244
2 parents 7980a0f + 7a14af4 commit 913a6d1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/postgresql/migrate/how-to-migrate-single-to-flexible-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ You can use the refresh button to refresh the status of the migrations.
167167

168168
You can also select the migration name in the grid to see the details of that migration.
169169

170-
:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png" alt-text="Screenshot of the the migration grid containing all migrations." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png":::
170+
:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png" alt-text="Screenshot of the migration grid containing all migrations." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png":::
171171

172172
As soon as the migration is created, the migration moves to the **InProgress** state and **PerformingPreRequisiteSteps** substate. It takes up to 10 minutes for the migration workflow to move out of this substate. The reason is that it takes time to create and deploy Database Migration Service, add the IP address on the firewall list of source and target servers, and perform maintenance tasks.
173173

0 commit comments

Comments
 (0)