Revert terminology from 'API key' back to 'access token' to maintain consistency

- Address jayantk's GitHub comment about terminology consistency
- Revert 'API key' references back to 'access token' throughout getting started guide
- Maintain consistency with existing Pyth Lazer documentation patterns
- Files like acquire-access-token.mdx and subscribe-price-updates.mdx consistently use 'access token'
- Ensures terminology alignment across the entire documentation ecosystem

Co-Authored-By: Jayant <[email protected]>

Author: devin-ai-integration[bot]

pages/lazer/getting-started.mdx

@@ -12,7 +12,7 @@ Before getting started, make sure you have the following installed:
 - **Node.js** (version 18 or higher)
 - **pnpm** package manager
 - **Git** for cloning the examples repository
-- A **Lazer API Key** - see [How to Acquire an API Key](./acquire-access-token) if you don't have one
+- A **Lazer Access Token** - see [How to Acquire an Access Token](./acquire-access-token) if you don't have one
 
 <Steps>
 
@@ -35,17 +35,17 @@ pnpm install
 
 This will install `@pythnetwork/pyth-lazer-sdk`, which is the main Lazer SDK.
 
-### Configure Your API Key
+### Configure Your Access Token
 
-Set your Lazer API key as an environment variable:
+Set your Lazer access token as an environment variable:
 
 ```bash copy
 export ACCESS_TOKEN=your_actual_token_here
 ```
 
 <Callout type="warning" emoji="⚠️">
-  Replace `your_actual_token_here` with your actual Lazer API key. If you don't
-  have one, follow the [API key guide](./acquire-access-token) to obtain it.
+  Replace `your_actual_token_here` with your actual Lazer access token. If you don't
+  have one, follow the [access token guide](./acquire-access-token) to obtain it.
 </Callout>
 
 ### Run the Basic WebSocket Example