diff --git a/Database-migrations.md b/Database-migrations.md
index a4d456f..3d66dbd 100644
--- a/Database-migrations.md
+++ b/Database-migrations.md
@@ -7,4 +7,4 @@ https://blog.makandra.com/2010/03/how-to-use-models-in-your-migrations-without-k
 
 ### Always provide a rollback method
 
-Simple migrations have a `change` method that can perform the migration and can be used to reverse it as well. But not everything can be reversed that easily. In that case you can declare the `up` and `down` methods, one for migrating and the other for rolling back. If the `up` method is destructive, you can't reverse it. For example, if you delete a whole column, the data is lost and can't be restored ... unless you keep a backup. No matter how simple the change is, we have some pretty complex production data and the simplest change can have nasty side effects. Therefore we should always write a backup file for the data we are destroying and provide a `down` method that can reverse the migration. The [first example](https://github.com/openfoodfoundation/openfoodnetwork/pull/3126/commits/f4d5727fb455618822f4bbd8415dea35d686434e) can give you an idea of how that works. Let's make it a bit more beautiful and re-usable next time we need a reversible destructive migration.
\ No newline at end of file
+Simple migrations have a `change` method that can perform the migration and can be used to reverse it as well. But not everything can be reversed that easily. In that case you can declare the `up` and `down` methods, one for migrating and the other for rolling back. If the `up` method is destructive, you can't reverse it. For example, if you delete a whole column, the data is lost and can't be restored ... unless you keep a backup. No matter how simple the change is, we have some pretty complex production data and the simplest change can have nasty side effects. Therefore we should always write a backup file for the data we are destroying and provide a `down` method that can reverse the migration. The [first example](https://github.com/openfoodfoundation/openfoodnetwork/blob/master/db/migrate/20181123012635_associate_customers_to_users.rb) can give you an idea of how that works. Let's make it a bit more beautiful and re-usable next time we need a reversible destructive migration.
\ No newline at end of file