docs edits

Author: paigecalvert

docs/vendor/environment-setup.mdx

@@ -97,7 +97,7 @@ sudo mv linux-amd64/helm /usr/local/bin/helm
 
 The Replicated CLI is the primary interface for the Replicated Platform. With the Replicated CLI, you can create and manage applications, releases, channels, customers, and more. You also use the Replicated CLI to create clusters with the Compatibility Matrix.
 
-After installing, authorize the Replicated CLI using the Replicated credentials to begin working with your applications. See [Authenticate](#auth) in _Install the Replicated CLI_.
+After installing, authorize the Replicated CLI using your Replicated credentials. See [Authenticate](#auth) in _Install the Replicated CLI_.
 
 For more information about installing and authorizing the Replicated CLI, see [Install the Replicated CLI](/reference/replicated-cli-installing).
 

docs/vendor/replicated-api-tokens.md

@@ -4,16 +4,14 @@ import TeamTokenNote from "../partials/vendor-api/_team-token-note.mdx"
 
 This topic describes the available types of API tokens and how to generate them for use with the Replicated CLI and Replicated Vendor API v3.
 
+The Replicated CLI also supports creating multiple authentication profiles for managing tokens across different accounts or environments. For more information, see [Authenticate](/reference/replicated-cli-installing#auth) in _Installing the Replicated CLI_.
+
 ## About API Tokens
 
 The Vendor API v3 is the API that manages applications in the Replicated Vendor Portal. The Replicated CLI is an implementation of the Vendor API v3.
 
 Using the Replicated CLI and Vendor API V3 requires an API token for authorization. Tokens are primarily used for automated customer, channel, and release management. You create tokens in the Vendor Portal.
 
-:::tip
-The Replicated CLI supports multiple authentication profiles for managing tokens across different accounts or environments. See [CLI Authentication Profiles](/reference/cli-profiles).
-:::
-
 The following types of tokens are available:
 
 - [Service Accounts](#service-accounts)
@@ -68,13 +66,11 @@ To generate a service account:
 
 1. Copy the service account token and save it in a secure location. The token will not be available to view again.
 
-   :::tip
-   You can store this token in a CLI authentication profile for easy management. See [CLI Authentication Profiles](/reference/cli-profiles).
-   :::
+1. (Recommended) Add the token to a Replicated authentication profile. See [Authenticate](/reference/replicated-cli-installing#auth) in _Installing the Replicated CLI_.
 
-   :::note
-   To remove a service account, select **Remove** for the service account that you want to delete.
-   :::
+:::note
+To remove a service account, select **Remove** for the service account that you want to delete.
+:::
 
 ### Generate a User API Token
 
@@ -101,10 +97,8 @@ To generate a user API token:
 
 1. Copy the user API token that displays and save it in a secure location. The token will not be available to view again.
 
-   :::tip
-   You can store this token in a CLI authentication profile for easy management. See [CLI Authentication Profiles](/reference/cli-profiles).
-   :::
+1. (Recommended) Add the token to a Replicated authentication profile. See [Authenticate](/reference/replicated-cli-installing#auth) in _Installing the Replicated CLI_.
 
-   :::note
-   To revoke a token, select **Revoke token** for the token that you want to delete.
-   :::
+:::note
+To revoke a token, select **Revoke token** for the token that you want to delete.
+:::