docs: streamline features section and remove redundant explanations in README

Author: CSenshi

packages/socket.io-adapter/README.md

@@ -18,12 +18,9 @@ Redis-powered Socket.IO adapter for NestJS
 
 ## Features
 
-- **Horizontal scaling**: Connect clients to any server instance
-- **Redis pub/sub**: Automatic event distribution across instances
-- **Lifecycle management**: Redis connections are managed automatically
-- **Works with existing connections**: Integrates seamlessly with `@nestjs-redis/client`
-- **Type-safe**: Full TypeScript support
-- **Production-ready**: Built on the official Socket.IO Redis adapter
+- Horizontal scaling with Redis pub/sub
+- Works with existing `@nestjs-redis/client` connections
+- Type-safe, production-ready
 
 ## Installation
 
@@ -41,8 +38,6 @@ npm install @nestjs-redis/socket.io-adapter redis
 
 ## Quick Start
 
-### Setup with existing Redis connection (Recommended)
-
 ```typescript
 // app.module.ts
 import { Module } from '@nestjs/common';
@@ -107,62 +102,6 @@ async function bootstrap() {
 }
 ```
 
-## The Problem
-
-When scaling your NestJS application horizontally with multiple instances, WebSocket connections become a challenge. By default, Socket.IO connections are tied to a single server instance, which means:
-
-- Events sent from one server instance won't reach clients connected to other instances
-- Real-time features break when users connect to different servers
-- Load balancing becomes complex as you need sticky sessions
-
-## The Solution
-
-This package provides a Redis-backed Socket.IO adapter that uses Redis pub/sub to synchronize events across all server instances. When a server emits an event, it's published to Redis and distributed to all other server instances, ensuring all clients receive the event regardless of which server they're connected to.
-
-## How It Works
-
-1. **Redis Pub/Sub**: The adapter creates two Redis connections - one for publishing and one for subscribing
-2. **Event Distribution**: When a server emits an event, it's published to a Redis channel
-3. **Cross-Instance Delivery**: All server instances subscribe to the same channels and forward events to their connected clients
-4. **Automatic Management**: Connection lifecycle is handled automatically by the adapter
-
-## API
-
-### `setupRedisAdapter(app, redisToken?)`
-
-Sets up the Redis adapter for the NestJS application.
-
-- `app`: NestJS application instance
-- `redisToken` (optional): Redis connection name (defaults to the default connection)
-
-### `RedisIoAdapter`
-
-The underlying Socket.IO adapter class that handles Redis connections.
-
-## Architecture
-
-```
-┌─────────────┐    ┌─────────────┐    ┌─────────────┐
-│   Server 1  │    │   Server 2  │    │   Server 3  │
-│  ┌───────┐  │    │  ┌───────┐  │    │  ┌───────┐  │
-│  │Client │  │    │  │Client │  │    │  │Client │  │
-│  └───────┘  │    │  └───────┘  │    │  └───────┘  │
-└──────┬──────┘    └──────┬──────┘    └──────┬──────┘
-       │                  │                  │
-       └──────────────────┼──────────────────┘
-                          │
-                    ┌─────▼─────┐
-                    │   Redis   │
-                    │  Pub/Sub  │
-                    └───────────┘
-```
-
-## Learn More
-
-- [NestJS WebSocket Adapter Documentation](https://docs.nestjs.com/websockets/adapter)
-- [Socket.IO Redis Adapter](https://socket.io/docs/v4/redis-adapter/)
-- [Redis Pub/Sub](https://redis.io/docs/manual/pubsub/)
-
 ## Links
 
 - Root repo: [CSenshi/nestjs-redis](https://github.com/CSenshi/nestjs-redis)