diff --git a/doc/release/branch.tex b/doc/release/branch.tex
index 237cbe1f5dc7eb915b89130563888efe0928f4b4..072abe5104db3cbd6d188aea587e54a9bb9655a6 100644
--- a/doc/release/branch.tex
+++ b/doc/release/branch.tex
@@ -16,7 +16,7 @@ When the ``freeze'' period arrives (usually a few weeks before the beta
 release), the release manager may decide to prevent direct merges to the
 \texttt{master} branch, until the \texttt{stable} branch is created. If so, then
 the branch should be protected such that Developers can no longer push and merge
-to it, without asking for a Master to do it. In Gitlab, this is done via:
+to it, without asking for a Maintainer to do it. In Gitlab, this is done via:
 Frama-C project $\rightarrow$ Settings $\rightarrow$ Repository $\rightarrow$
 Protected Branches.\\
 
diff --git a/doc/release/deploy.tex b/doc/release/deploy.tex
index f6baebc205fb89b2c0dbe7962f1e3cf4a0cc5c56..6f510a2bc1bdb9af4494b43cbd80d64bda460f7e 100644
--- a/doc/release/deploy.tex
+++ b/doc/release/deploy.tex
@@ -101,7 +101,7 @@ For a final release \textbf{ONLY}, the following files must appear as \textbf{mo
   \item \texttt{e-acsl/e-acsl-implementation.pdf}
   \item \texttt{e-acsl/e-acsl-manual.pdf}
   \item \texttt{frama-c-aorai-example.tar.gz}
-  \item \texttt{hello.tar.gz}
+  \item \texttt{frama-c-hello.tar.gz}
 \end{itemize}
 
 If everything is fine, merge the website and ask a website maintainer to put it
diff --git a/doc/release/validation.tex b/doc/release/validation.tex
index 0ebbd63c50f3cdff939503b604c6901356feb5fd..a8a746c7905b469ac16e856637d811a6c1a5d7bf 100644
--- a/doc/release/validation.tex
+++ b/doc/release/validation.tex
@@ -113,7 +113,7 @@ Commit any change that you have done during these checks \textbf{and push}.
 In the last continuous integration pipeline of the release branch, force the
 run of the following targets:
 \begin{itemize}
-  \item manuals
+  \item manuals-artifacts
   \item opam-pin
   \item opam-pin-minimal
 \end{itemize}