fix(runpodctl): correct the windows install command

runpodctl/overview.mdx

@@ -1,12 +1,12 @@
 ---
 title: "Overview"
 sidebarTitle: "Overview"
 description: "Use Runpod CLI to manage Pods, Serverless endpoints, templates, and more from your local machine. Review commands and usage guidance for the Runpod CLI."
 ---
 
 import { PodsTooltip, PodTooltip } from "/snippets/tooltips.jsx";
 
 Runpod CLI is an [open source](https://github.com/runpod/runpodctl) command-line tool for managing your Runpod resources from your local machine. You can manage Pods, Serverless endpoints, templates, network volumes, and models, transfer files between your system and Runpod, diagnose issues, and view account information.
 
 ## Quick start
 
@@ -20,7 +20,7 @@
 runpodctl pod list                  # List your Pods
 ```
 
 ## Install Runpod CLI locally
 
 Every <PodTooltip /> you deploy comes preinstalled with `runpodctl` and a Pod-scoped API key. You can also install it on your local machine to manage resources remotely.
 
@@ -95,9 +95,34 @@
 </Tab>
 
 <Tab title="Windows">
-```bash
-wget https://github.com/runpod/runpodctl/releases/latest/download/runpodctl-windows-amd64.exe -O runpodctl.exe
-```
+
+In PowerShell, `wget` is an alias for `Invoke-WebRequest`, so use `Invoke-WebRequest` directly. This installs runpodctl to `%LOCALAPPDATA%\runpodctl` and adds it to your `PATH`, so you can run `runpodctl` from any terminal.
+
+**AMD64 (x86_64):**
+```powershell
+$dest = "$env:LOCALAPPDATA\runpodctl"
+Invoke-WebRequest -UseBasicParsing -Uri https://github.com/runpod/runpodctl/releases/latest/download/runpodctl-windows-amd64.zip -OutFile "$env:TEMP\runpodctl.zip"
+Expand-Archive -Force -Path "$env:TEMP\runpodctl.zip" -DestinationPath $dest
+$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
+$pathEntries = @($userPath -split ';' | Where-Object { $_ })
+if ($pathEntries -notcontains $dest) {
+  [Environment]::SetEnvironmentVariable('Path', (($pathEntries + $dest) -join ';'), 'User')
+}
+```
+
+**ARM64:**
+```powershell
+$dest = "$env:LOCALAPPDATA\runpodctl"
+Invoke-WebRequest -UseBasicParsing -Uri https://github.com/runpod/runpodctl/releases/latest/download/runpodctl-windows-arm64.zip -OutFile "$env:TEMP\runpodctl.zip"
+Expand-Archive -Force -Path "$env:TEMP\runpodctl.zip" -DestinationPath $dest
+$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
+$pathEntries = @($userPath -split ';' | Where-Object { $_ })
+if ($pathEntries -notcontains $dest) {
+  [Environment]::SetEnvironmentVariable('Path', (($pathEntries + $dest) -join ';'), 'User')
+}
+```
+
+Open a new terminal so the `PATH` change takes effect, then verify with `runpodctl version`.
 
 </Tab>
 
@@ -145,7 +170,7 @@
 runpodctl doctor
 ```
 
 This command guides you through first-time setup, including API key configuration and SSH key setup.
 
 Alternatively, you can manually configure your API key:
 
@@ -158,7 +183,7 @@
 saved apiKey into config file: /Users/runpod/.runpod/config.toml
 ```
 
 ### Step 3: Verify installation
 
 To verify that `runpodctl` installed successfully, run this command:
 
@@ -166,7 +191,7 @@
 runpodctl version
 ```
 
 You should see which version is installed:
 
 ```bash
 runpodctl v2.0
@@ -174,11 +199,11 @@
 
 ## Command groups
 
 Runpod CLI organizes commands into groups based on the resource type:
 
 | Command | Alias | Description |
 |---------|-------|-------------|
 | `runpodctl pod` | | Manage Pods (create, list, start, stop, delete) |
 | `runpodctl serverless` | `sls` | Manage Serverless endpoints |
 | `runpodctl template` | `tpl` | List, search, and manage templates |
 | `runpodctl hub` | | Browse and deploy from the Runpod Hub |
@@ -192,7 +217,7 @@
 
 ## Help and reference
 
 Learn how to use Runpod CLI commands by browsing the CLI reference using the sidebar to the left, or by running the `help` command:
 
 ```bash
 runpodctl help
@@ -211,6 +236,6 @@
 runpodctl completion
 ```
 
 This command auto-detects your shell and adds the appropriate source command to your shell configuration file (`~/.bashrc` or `~/.zshrc`). The command is idempotent—running it again skips installation if completion is already configured.
 
 Restart your shell or source the configuration file for changes to take effect.