Skip to content

Commit fac381f

Browse files
authored
Update migrate-continuous-backup.md
1 parent 2a1f8b3 commit fac381f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/migrate-continuous-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following are the key reasons to migrate into continuous mode:
3333
>
3434
> You can migrate an account to continuous backup mode only if the following conditions are true. Also checkout the [point in time restore limitations](continuous-backup-restore-introduction.md#current-limitations) before migrating your account:
3535
>
36-
> * If the account is of type API for NoSQL, API for Table or Gremlin or MongoDB.
36+
> * If the account is of type API for NoSQL,API for Table or Gremlin or MongoDB.
3737
> * If the account has a single write region.
3838
> * If the account isn't enabled with analytical store.
3939
>
@@ -226,7 +226,7 @@ Yes.
226226

227227
### Which accounts can be targeted for backup migration?
228228

229-
Currently, API for NoSQL, API for Table , Gremlin API and API for MongoDB accounts with single write region that have shared, provisioned, or autoscale provisioned throughput support migration.
229+
Currently, API for NoSQL, API for Table, Gremlin API and API for MongoDB accounts with single write region that have shared, provisioned, or autoscale provisioned throughput support migration.
230230

231231
Accounts enabled with analytical storage and multiple-write regions aren't supported for migration.
232232

0 commit comments

Comments
 (0)