docs: remove duplicate How It Works section

Author: beran-t

docs/use-cases/ci-cd.mdx

@@ -6,17 +6,6 @@ icon: "gears"
 
 CI/CD pipelines can use AI agents to review pull requests, generate tests, and validate code changes automatically. E2B sandboxes provide the secure, isolated execution environment where these agents can safely clone repositories, run untrusted code, and report results — all triggered by [GitHub Actions](https://docs.github.com/en/actions) on every pull request. Since each run gets a fresh sandbox, malicious or buggy PR code never touches your CI runner.
 
-## How It Works
-
-The AI-powered CI/CD workflow follows this pattern:
-
-1. **A pull request is opened or updated** — GitHub Actions triggers a workflow
-2. **The workflow creates an E2B sandbox** — a fresh Linux environment isolated from the CI runner
-3. **The repository is cloned into the sandbox** — the PR branch is checked out using E2B's [git integration](/docs/sandbox/git-integration)
-4. **An LLM analyzes the changes** — the diff is sent to a language model (e.g., OpenAI ChatGPT 5.2 Mini, Anthropic Claude) for review or test generation
-5. **Tests run inside the sandbox** — the project's test suite executes in isolation, with output streamed back to the workflow
-6. **Results are reported** — the workflow posts findings as PR comments via the GitHub API
-
 ## GitHub Actions Workflow
 
 The workflow triggers on pull request events and runs a review script. `E2B_API_KEY` and the LLM API key are stored as [GitHub Actions secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions), while the built-in `GITHUB_TOKEN` is available automatically. The `permissions` block grants write access so the script can post PR comments.