diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md
index ebccbe3..af72042 100644
--- a/docs/maintainers/handbook.md
+++ b/docs/maintainers/handbook.md
@@ -41,7 +41,7 @@ For a simple example check the [entrypoint.sh for `croc`](https://git.coopcloud.
 
 If you write your own entrypoint, it needs to be specified in the `config` section of compose.yml. See [this handbook entry](/maintainers/handbook/#how-do-i-set-a-custom-entrypoint) for more.
 
-### `releases/` directory
+### `release/` directory
 
 This directory contains text files whose names correspond to the recipe versions which have been released and contain useful tips for operators who are doing upgrade work. See [this handbook entry](/maintainers/handbook/#how-do-i-write-version-release-notes) for more.
 
@@ -396,11 +396,11 @@ mkdir -p release
 
 And then create a text file which corresponds to the version release, e.g. `1.1.0+5.9.0` and write some notes. `abra` will show these when another operator runs `abra app deploy` / `abra app upgrade`.
 
-You can also add release notes for the next release into a special file `releases/next`. This file will be used when running `abra recipe release`.
+You can also add release notes for the next release into a special file `release/next`. This file will be used when running `abra recipe release`.
 
 !!! warning "Not available previous versions of Abra"
 
-    Using `releases/next` is only available in > 0.9.x series of `abra`.
+    Using `release/next` is only available in > 0.9.x series of `abra`.
 
 ## How do I generate the recipe catalogue