Removing the old API files from the latest/2.8 versions and updating the redirect to current URL, also updating some verbiage after review.

Signed-off-by: Sunil Singh <sunil.singh@suse.com>

versioned_docs/version-2.8/api/previous-rancher-api-versions/api-tokens.md

@@ -6,6 +6,8 @@ title: Using API Tokens in Past Rancher Versions
   <link rel="canonical" href="https://ranchermanager.docs.rancher.com/api/previous-rancher-api-versions/api-tokens"/>
 </head>
 
+Rancher `v2.8.0` introduced the [Rancher Kubernetes API](../api-reference.mdx) which can be used to manage Rancher resources through `kubectl`. In previous Rancher versions `v2.7.x` and below you can access token resources through the previously used [web interface](https://ranchermanager.docs.rancher.com/v2.7/reference-guides/about-the-api).
+
 By default, some cluster-level API tokens are generated with infinite time-to-live (`ttl=0`). In other words, API tokens with `ttl=0` never expire unless you invalidate them. Tokens are not invalidated by changing a password.
 
 You can deactivate API tokens by deleting them or by deactivating the user account.

versioned_docs/version-2.8/api/previous-rancher-api-versions/previous-rancher-api-versions.md

@@ -6,9 +6,9 @@ title: Previous API Guide
   <link rel="canonical" href="https://ranchermanager.docs.rancher.com/api/previous-rancher-api-versions"/>
 </head>
 
-## How to use the API
+## How to Use the API
 
-The previous Rancher API has its own user interface accessible from a web browser.  This is an easy way to see resources, perform actions, and see the equivalent cURL or HTTP request & response.  To access it:
+The past Rancher versions `v2.7.x` and below have their own API user interfaces accessible from a web browser. This is an easy way to see resources, perform actions, and see the equivalent cURL or HTTP request & response.  To access it:
 
 <Tabs>
 <TabItem value="Rancher v2.6.4+">