From abb2772696499340ba6aa0dee0ef0d1a0db053ae Mon Sep 17 00:00:00 2001
From: bagtoad <47394200+BagToad@users.noreply.github.com>
Date: Tue, 22 Oct 2024 10:56:39 -0600
Subject: [PATCH] Use new GitHub preview terms in working-with-us.md

Update the "working with us" docs to align with new GitHub previews terminology, replacing `beta` with `public preview`.

https://github.blog/changelog/2024-10-18-new-terminology-for-github-previews/
---
 docs/working-with-us.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/working-with-us.md b/docs/working-with-us.md
index 38326921e..fefacf103 100644
--- a/docs/working-with-us.md
+++ b/docs/working-with-us.md
@@ -25,13 +25,13 @@ Describe how your new command would be used. Include mock-up examples, including
 
 We take this step seriously because we believe in keeping `gh`'s interface consistent and intuitive.
 
-## Step 2: Beta
+## Step 2: Public Preview
 
-Once we've signed off on the proposed UX on the issue opened in step 1, develop your extension to at least beta quality. It's up to you if you actually want to go through a beta release phase with real users or not.
+Once we've signed off on the proposed UX on the issue opened in step 1, develop your extension to at least public preview quality. It's up to you if you actually want to go through a public preview release phase with real users or not.
 
 ## Step 3: Merge or no merge
 
-With a beta in hand it's time to decide whether or not to mainline your extension into the `trunk` of `gh`. Some questions to consider:
+With a public preview in hand it's time to decide whether or not to mainline your extension into the `trunk` of `gh`. Some questions to consider:
 
 - How complex is the support burden for your feature?