chore(readme): fix typos (#27)

This commit is contained in:
Arash Ari Sheyda
2025-04-16 12:03:52 -06:00
committed by GitHub
parent 704df1efa3
commit 26d551e303

View File

@@ -130,7 +130,7 @@ Both approaches are _transparent_ to everyday usage you still run `codex` fr
| Requirement | Details | | Requirement | Details |
| --------------------------- | --------------------------------------------------------------- | | --------------------------- | --------------------------------------------------------------- |
| Operating systems | macOS 12+, Ubuntu 20.04+/Debian 10+, or Windows 11 **via WSL2** | | Operating systems | macOS 12+, Ubuntu 20.04+/Debian 10+, or Windows 11 **via WSL2** |
| Node.js | **22 newer** (LTS recommended) | | Node.js | **22 or newer** (LTS recommended) |
| Git (optional, recommended) | 2.23+ for builtin PR helpers | | Git (optional, recommended) | 2.23+ for builtin PR helpers |
| ripgrep (optional) | `rg` accelerates largerepo search | | ripgrep (optional) | `rg` accelerates largerepo search |
| RAM | 4GB minimum (8GB recommended) | | RAM | 4GB minimum (8GB recommended) |
@@ -276,7 +276,7 @@ Any model available with [Responses API](https://platform.openai.com/docs/api-re
## Contributing ## Contributing
This project is under active development and the code will likely change pretty siginificantly. We'll update this message once that's complete! This project is under active development and the code will likely change pretty significantly. We'll update this message once that's complete!
More broadly We welcome contributions whether you are opening your very first pull request or youre a seasoned maintainer. At the same time we care about reliability and longterm maintainability, so the bar for merging code is intentionally **high**. The guidelines below spell out what “highquality” means in practice and should make the whole process transparent and friendly. More broadly We welcome contributions whether you are opening your very first pull request or youre a seasoned maintainer. At the same time we care about reliability and longterm maintainability, so the bar for merging code is intentionally **high**. The guidelines below spell out what “highquality” means in practice and should make the whole process transparent and friendly.