From 2a0dec825362dc70948a628729a01263b9e2a8da Mon Sep 17 00:00:00 2001
From: orig <48911144+origranot@users.noreply.github.com>
Date: Wed, 31 Jan 2024 19:20:18 +0200
Subject: [PATCH] docs(misc): fixed a typo on nx-release recipe (#21453)

---
 docs/shared/recipes/nx-release/publish-in-ci-cd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/shared/recipes/nx-release/publish-in-ci-cd.md b/docs/shared/recipes/nx-release/publish-in-ci-cd.md
index 401922b2df..9658569ba1 100644
--- a/docs/shared/recipes/nx-release/publish-in-ci-cd.md
+++ b/docs/shared/recipes/nx-release/publish-in-ci-cd.md
@@ -154,7 +154,7 @@ jobs:
 
 This workflow will install node, install npm dependencies, then run `nx release publish` to publish the packages. It will run on every push to the repository that creates a tag that matches the pattern `v*.*.*`. A release process using this workflow is as follows:
 
-1. Run `nx release --skip-publish` locally. This will create a commit with the version and changelog updates, then create a tag for the new version version.
+1. Run `nx release --skip-publish` locally. This will create a commit with the version and changelog updates, then create a tag for the new version.
 2. Push the changes (including the new tag) to the remote repository with `git push && git push --tags`.
 3. The publish workflow will automatically trigger and publish the packages to the npm registry.