From de3131592aa3049a72fc11005db460114b198e03 Mon Sep 17 00:00:00 2001
From: ozaki <29860391+OzakIOne@users.noreply.github.com>
Date: Thu, 4 Apr 2024 16:56:34 +0200
Subject: [PATCH] docs: remove old github action description (#9980)

---
 website/docs/deployment.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/deployment.mdx b/website/docs/deployment.mdx
index 9048c4a4d1ae..527208a69c10 100644
--- a/website/docs/deployment.mdx
+++ b/website/docs/deployment.mdx
@@ -355,7 +355,7 @@ Our goal is that:
 1. When a new pull request is made to `main`, there's an action that ensures the site builds successfully, without actually deploying. This job will be called `test-deploy`.
 2. When a pull request is merged to the `main` branch or someone pushes to the `main` branch directly, it will be built and deployed to GitHub Pages. This job will be called `deploy`.
 
-Here are two approaches to deploying your docs with GitHub Actions. Based on the location of your deployment branch (`gh-pages`), choose the relevant tab below:
+Here are two approaches to deploying your docs with GitHub Actions. Based on the location of your deployment repository, choose the relevant tab below:
 
 - Source repo and deployment repo are the **same** repository.
 - The deployment repo is a **remote** repository, different from the source. Instructions for this scenario assume [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is the `gh-pages` branch.