From 3acae8a43ff03abc042eab24737c7effa97ede85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABl=20Valais?= <mael@vls.dev>
Date: Fri, 15 Sep 2023 13:58:03 +0200
Subject: [PATCH] release-process: remove duplicate explanation about github
 token
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Maël Valais <mael@vls.dev>
---
 content/docs/contributing/release-process.md | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/content/docs/contributing/release-process.md b/content/docs/contributing/release-process.md
index 05d74eda5aa..cedd546f40f 100644
--- a/content/docs/contributing/release-process.md
+++ b/content/docs/contributing/release-process.md
@@ -494,15 +494,11 @@ page if a step is missing or if it is outdated.
          --output github-release-description.md
        ```
 
-       <div className="pageinfo pageinfo-info"><p>
-       The GitHub token **does not need any scope**. The token is required
-       only to avoid rate-limits imposed on anonymous API users.
-       </p></div>
-
         <div className="pageinfo pageinfo-info"><p>
         The GitHub token **does not need any scope**. The token is required
         only to avoid rate-limits imposed on anonymous API users.
         </p></div>
+
     3. Add a one-sentence summary at the top.
 
     4. **(final release only)** Write the "Community" section, following the example of past releases such as [v1.12.0](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.0). If there are any users who didn't make code contributions but helped in other ways (testing, PR discussion, etc), be sure to thank them here!