diff --git a/pages/06.contribute/10.packaging_apps/14.advanced/03.packaging_v2/packaging_v2.md b/pages/06.contribute/10.packaging_apps/14.advanced/03.packaging_v2/packaging_v2.md
index 5503925a..011b9a93 100644
--- a/pages/06.contribute/10.packaging_apps/14.advanced/03.packaging_v2/packaging_v2.md
+++ b/pages/06.contribute/10.packaging_apps/14.advanced/03.packaging_v2/packaging_v2.md
@@ -63,6 +63,7 @@ This will edit the file in place and you should then carefully review and iterat
     - `doc/notifications/post_upgrade.md` : a note to be displayed after the app upgrade. For example in the context of Nextcloud, the fact that you may need to re-enable custom modules manually ?
  - **Replace some historical names with more sensible ones**, or homogenize some practices:
     - `final_path` is now `install_dir` (this migration should be automatically handled by the core and the `convert_app_to_packaging_v2.py` script)
+    - `datadir` is now `data_dir` to be consistent with `install_dir` (this migration should be automatically handled by the core and the `convert_app_to_packaging_v2.py` script)
     - `path` is now always loaded as `$path`, no funky `$path_url`-but-it-is-saved-as-`path` anymore (this migration should be automatically handled by the core and the `convert_app_to_packaging_v2.py` script)
     - `mysqldbpwd` and `psqlpwd` or whatever are now always saved as `db_pwd` (cf the `database` resource) (this migration should be automatically handled by the core and the `convert_app_to_packaging_v2.py` script)
     - ports settings are now always named either `$port` or `$port_foo_bar` instead of `$foo_bar_port` (cf the `port` resource) (this migration should be automatically handled by the core and the `convert_app_to_packaging_v2.py` script)