From 86672ab1fd45567cc2aceb69f40c33cd1cf3ead3 Mon Sep 17 00:00:00 2001
From: Rohan Santhosh Kumar <181558744+Rohan5commit@users.noreply.github.com>
Date: Tue, 28 Apr 2026 10:29:35 +0800
Subject: [PATCH] docs: fix the release marker label in the release process
 guide

---
 doc/dev-guide/src/release-process.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/dev-guide/src/release-process.md b/doc/dev-guide/src/release-process.md
index adec1c0f41..5e4af7cf07 100644
--- a/doc/dev-guide/src/release-process.md
+++ b/doc/dev-guide/src/release-process.md
@@ -98,7 +98,7 @@ and determine which `$BRANCH` you should be working on:
 
 Producing the final release artifacts is a bit involved because of the way
 rustup is distributed. Below is a list of things to be done in order to cut a
-new [b]eta release or an official [r]elease:
+new [b]eta release or an official release [r]:
 
 1. [b/r] Make sure that the desired version number for the new release
    `$VER_NUM` already exists in `$BRANCH`'s `Cargo.toml` file. Then in a new PR