diff --git a/doc/project/release_process.rst b/doc/project/release_process.rst
index efc5012ad3f..5ffb189dbf1 100644
--- a/doc/project/release_process.rst
+++ b/doc/project/release_process.rst
@@ -409,26 +409,3 @@ steps:
 
         #. Send an email to the mailing lists (``announce`` and ``devel``) with a link
            to the release
-
-Listing all closed GitHub issues
-=================================
-
-The release notes for a final release contain the list of GitHub issues that
-have been closed during the development process of that release.
-
-In order to obtain the list of issues closed during the release development
-cycle you can do the following:
-
-#. Look for the last release before the current one and find the day it was
-   tagged::
-
-    $ git show -s --format=%ci v1.10.0
-    tag v1.10.0
-    Tagger: Kumar Gala <kumar.gala@linaro.org>
-
-    Zephyr 1.10.0
-    2017-12-08 13:32:22 -0600
-
-
-#. Use available release tools to list all the issues that have been closed
-   between that date and the day of the release.
diff --git a/doc/releases/release-notes-3.5.rst b/doc/releases/release-notes-3.5.rst
index fbfbdbc11eb..a6bb1beaec3 100644
--- a/doc/releases/release-notes-3.5.rst
+++ b/doc/releases/release-notes-3.5.rst
@@ -313,11 +313,5 @@ Documentation
 Tests and Samples
 *****************
 
-Issue Related Items
-*******************
-
 Known Issues
-============
-
-Addressed issues
-================
+************