Skip to content

Commit 6484a58

Browse files
authored
fix: grammar in security-tokens doc (#1390)
1 parent bc9ae96 commit 6484a58

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/hub/security-tokens.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,6 @@ We recommend you create one access token per app or usage. For instance, you cou
7474

7575
This way, you can invalidate one token without impacting your other usages.
7676

77-
We also recommend only using fine-grained tokens for production usage. The impact, if leaked, will be reduced, and they can be shared among your organization without impacting your account.
77+
We also recommend using only fine-grained tokens for production usage. The impact, if leaked, will be reduced, and they can be shared among your organization without impacting your account.
7878

7979
For example, if your production application needs read access to a gated model, a member of your organization can request access to the model and then create a fine-grained token with read access to that model. This token can then be used in your production application without giving it access to all your private models.

0 commit comments

Comments
 (0)