diff --git a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md
index 62912567893..294a4dc55b4 100644
--- a/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md
+++ b/website/docs/docs/dbt-versions/release-notes/02-Dec-2022/private-packages-clone-git-token.md
@@ -7,7 +7,7 @@ tags: [Dec-23-2022]
 
 The supported method for cloning private GitHub packages is the [git token method](/docs/build/packages#git-token-method), where an appropriate access token is passed into the package repository URL with an environment variable. 
 
-There is a small number of people that has been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. 
+A small number of people have been able to clone private packages using dbt's native GitHub application without explicitly providing an access token. This functionality is being deprecated as it’s limited in flexibility. 
 
 If you have been using a package hosted in a private repository on GitHub, you must start passing an access token into the URL.