chore(readme): rewrite readme to not be able the problem but about the actual module

Author: Trozz

README.md

@@ -1,40 +1,31 @@
 # pulumi-aws-ec2-capacity-fallback
 
-A Pulumi component that launches EC2 instances with automatic fallback across instance types and availability zones when AWS returns capacity errors.
+A Pulumi dynamic resource provider that launches EC2 instances with automatic capacity fallback. You provide an ordered list of instance types and subnets, and the component walks through each type/AZ combination until one launches successfully. If AWS returns `InsufficientInstanceCapacity` or similar errors, it moves on to the next option without failing the deployment.
 
-## The problem
+This is particularly useful for GPU instance types (g6, g5, p5, etc.) where capacity is limited and unevenly distributed across availability zones.
 
-When launching GPU instances (g6, g5, p5, etc.), AWS frequently returns `InsufficientInstanceCapacity` because GPU capacity is limited and unevenly distributed across AZs. This causes `pulumi up` to fail, requiring manual intervention to try a different instance type or AZ.
+Once an instance is running, the component locks the launched type and subnet. Changing your type preferences in config won't replace an existing instance -- use `pulumi up --replace <urn>` for that.
 
-## The solution
+The component pre-filters combinations using `describe_instance_type_offerings` before attempting any launches, supports AZ suffix filtering, optional least-used subnet selection, and in-place updates for tags and security groups.
 
-This component wraps EC2 instance creation with retry logic. You provide an ordered list of instance types, and the component:
-
-1. Checks `describe_instance_type_offerings` to skip types not offered in the target AZs
-2. Attempts to launch each remaining type/AZ combination via `run_instances`
-3. On `InsufficientInstanceCapacity`, `Unsupported`, or `InstanceLimitExceeded`, automatically tries the next combination
-4. Once launched, the instance type is locked -- subsequent `pulumi up` runs will not replace the instance even if a different type is now preferred
+## Installation
 
-## Features
+Install directly from GitHub:
 
-- Automatic fallback across multiple instance types in priority order
-- Automatic fallback across multiple availability zones
-- Pre-flight offerings check to skip types not available in target AZs
-- AZ filtering (e.g. restrict to AZ A and B only)
-- Least-used subnet selection for balanced distribution
-- In-place tag and security group updates without instance replacement
-- Instance type locked after creation (use `pulumi up --replace <urn>` to force change)
+```bash
+uv add git+ssh://git@github.com/GremlinLTD/pulumi-python-aws-ec2-capacity-fallback.git
+```
 
-## Installation
+Or with pip:
 
 ```bash
-uv add pulumi-aws-ec2-capacity-fallback
+pip install git+ssh://git@github.com/GremlinLTD/pulumi-python-aws-ec2-capacity-fallback.git
 ```
 
-Or with pip:
+To pin a specific version tag:
 
 ```bash
-pip install pulumi-aws-ec2-capacity-fallback
+uv add git+ssh://git@github.com/GremlinLTD/pulumi-python-aws-ec2-capacity-fallback.git@v0.1.0
 ```
 
 ## Usage
@@ -121,14 +112,16 @@ instance = ResilientInstanceRaw(
 
 ## How it handles re-runs
 
-The component is designed to be safe on subsequent `pulumi up` runs:
+Subsequent `pulumi up` runs are safe:
 
 - **Instance type changes in config**: ignored. The existing instance keeps its launched type.
 - **Subnet/AZ changes in config**: ignored. The existing instance stays in its launched subnet.
 - **Tag changes**: applied in-place (no instance replacement).
 - **Security group changes**: applied in-place.
 - **AMI changes**: triggers instance replacement (delete + create with fallback).
 - **Volume size changes**: triggers instance replacement.
+- **Key name changes**: triggers instance replacement.
+- **User data changes**: triggers instance replacement.
 - **Intentional type change**: use `pulumi up --replace <urn>` to force recreation.
 
 ## Retryable errors