From 1a7330e1e0841072d445fa9de02d1b321dd133a0 Mon Sep 17 00:00:00 2001 From: Faraz Samapoor Date: Mon, 9 Jan 2023 13:21:57 +0330 Subject: [PATCH] Updates the "Migrations" section's phrasing. To make it more readable and to remove redundant words. Signed-off-by: Faraz Samapoor --- developer_manual/basics/storage/migrations.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer_manual/basics/storage/migrations.rst b/developer_manual/basics/storage/migrations.rst index b17f2323b..88fabe418 100644 --- a/developer_manual/basics/storage/migrations.rst +++ b/developer_manual/basics/storage/migrations.rst @@ -43,7 +43,7 @@ For example, you can rename a column while copying all the content with 3 steps packed in 2 migrations. After creating migrations for your current database and installation routine, -you need to in order to make use of migrations, is to delete the old `appinfo/database.xml` +in order to make use of migrations, you need to delete the old `appinfo/database.xml` file. The Nextcloud updater logic only allows to use one or the other. But as soon as the `database.xml` file is gone, it will look for your migration files in the apps `lib/Migration` folder.