From c120d5f3abaf48cf5f165069029ea5fce0124aa7 Mon Sep 17 00:00:00 2001 From: Jeremy Evans Date: Wed, 2 Apr 2025 16:28:59 -0700 Subject: [PATCH] Use softer wording in the CLI documentation --- quick-start/cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quick-start/cli.mdx b/quick-start/cli.mdx index b9f3769..5c2ef6b 100644 --- a/quick-start/cli.mdx +++ b/quick-start/cli.mdx @@ -29,7 +29,7 @@ That will create a personal access token. Click on the clipboard icon under the ![View token screenshot](/quick-start/cli-2-screenshot.png) -You can choose how you want to store this access token. As mentioned above, `ubi` requires it be provided via the `UBI_TOKEN` environment variable. If you have a password manager or other secure secret storage vault, you can store the token in there. If security is not at all important to you, you could store the access token in your shell startup files, so it is available for all programs. +You can choose how you want to store this access token. As mentioned above, `ubi` requires it be provided via the `UBI_TOKEN` environment variable. If you have a password manager or other secure secret storage vault, you can store the token in there. If security is not your primary concern, you could store the access token in your shell startup files, so it is available for all programs. As there a myriad number of ways that users may want to store the token, `ubi` does not provide integrations for specific token storage. You can use any storage method you want as long as the `UBI_TOKEN` environment variable is present when you execute the `ubi` program.