diff options
| author | Pascal Borreli <pascal@borreli.com> | 2018-04-27 11:50:05 +0300 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2018-04-27 11:50:05 +0300 |
| commit | 12e3eff462077008143146181c81f77204d1a8a9 (patch) | |
| tree | 3a7c1cf7ae9004a27df9d1c3d942a138185a3ee2 /doc/development/background_migrations.md | |
| parent | 740f0bb126a4e7da94d9d0181d2023b14113c93e (diff) | |
Fixed typos
Diffstat (limited to 'doc/development/background_migrations.md')
| -rw-r--r-- | doc/development/background_migrations.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/background_migrations.md b/doc/development/background_migrations.md index ce69694ab6a..46c5baddb9c 100644 --- a/doc/development/background_migrations.md +++ b/doc/development/background_migrations.md @@ -24,7 +24,7 @@ Some examples where background migrations can be useful: * Migrating events from one table to multiple separate tables. * Populating one column based on JSON stored in another column. -* Migrating data that depends on the output of exernal services (e.g. an API). +* Migrating data that depends on the output of external services (e.g. an API). ## Isolation @@ -46,7 +46,7 @@ See [Sidekiq best practices guidelines](https://github.com/mperham/sidekiq/wiki/ for more details. Make sure that in case that your migration job is going to be retried data -integrity is guarateed. +integrity is guaranteed. ## How It Works |