Update docs/architecture/self-hosted/authentication/databricks-oauth.md

Co-authored-by: kathweinschenkprophecy <[email protected]>
SimpleDataLabsInc · Dec 13, 2024 · c5070ff · c5070ff
1 parent 549a7f2
commit c5070ff
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/architecture/self-hosted/authentication/databricks-oauth.md b/docs/architecture/self-hosted/authentication/databricks-oauth.md
@@ -29,7 +29,7 @@ The authentication flow then uses Prophecy-hosted callback URL to capture and pr
 
 ### Token storage
 
-Prophecy stores the refresh token, which are used to renew the refresh token itself, and also get a new access token to maintain authenticated connectivity to Databricks.
+Prophecy stores the refresh token, which is used to renew the refresh token itself, and also gets a new access token to maintain authenticated connectivity to Databricks.
 
 The tokens are stored securely, with access limited to authorized Prophecy processes. This includes encrypting tokens before storing them in our database, in the same way that we encrypt other credentials that Prophecy stores.