docs: fix english grammar

Author: S1M0N38

docs/contributing.md

@@ -36,7 +36,7 @@ Before contributing, ensure you have:
     uv sync --all-extras
     ```
 
-3. **Stars Balatro with Mods**
+3. **Start Balatro with Mods**
 
     ```bash
     ./balatro.sh -p 12346
@@ -93,7 +93,7 @@ Before contributing, ensure you have:
     - **Important**: Enable "Allow edits from maintainers" when creating your PR
     - Link to related issues
     - Provide clear description of changes
-    - Include test for new functionality
+    - Include tests for new functionality
 
 ### Commit Messages
 
@@ -247,9 +247,9 @@ pytest -n 4 --port 12346 --port 12347 --port 12348 --port 12349 tests/lua/
 **Troubleshooting Test Failures**:
 
 - **Connection timeouts**: Ensure TCP port 12346 is available
-- **Game state errors**: Verify game is responsive and hasn't crashed
-- **Invalid responses**: Check mod loaded correctly in `balatro.log`
-- **Balatro crashes**: Stop testing immediately, investigate crash logs, restart game before retrying
+- **Game state errors**: Verify the game is responsive and hasn't crashed
+- **Invalid responses**: Check the mod loaded correctly in `balatro.log`
+- **Balatro crashes**: Stop testing immediately, investigate crash logs, restart the game before retrying
 
 ### Documentation
 
@@ -275,18 +275,8 @@ mkdocs build
 
 - **Focus Area**: Primary development is on `src/lua/api.lua`
 - **Communication**: TCP protocol on port 12346
-- **Protocol**: Bot sends "HELLO" → Game responds with JSON state → Bot sends actions
 - **Debugging**: Use DebugPlus mod for enhanced debugging capabilities
 
-### Architecture Context
-
-The project consists of:
-
-- **Lua API** (`src/lua/api.lua`): Game-side mod handling socket communication
-- **Python Framework** (`src/balatrobot/`): Bot development framework (being refactored)
-- **TCP Communication**: Real-time bidirectional communication
-- **Testing Suite**: Comprehensive API and integration tests
-
 ### Configuration System
 
 The BalatroBot mod includes a sophisticated configuration system that optimizes Balatro for bot automation:

docs/developing-bots.md

@@ -1,11 +1,11 @@
 # Developing Bots
 
-BalatroBot allows you to create automated players (bots) that can play Balatro by implementing decision-making logic in Python. Your bot communicates with the game through a TCP socket connection actions to perform and receiving back the game state.
+BalatroBot allows you to create automated players (bots) that can play Balatro by implementing decision-making logic in Python. Your bot communicates with the game through a TCP socket connection, sending actions to perform and receiving back the game state.
 
 ## Bot Architecture
 
 A bot is a finite state machine that implements a sequence of actions to play the game.
-The bot can be in one state at a time and have access to a set of functions that can move the bot to other states.
+The bot can be in one state at a time and has access to a set of functions that can move the bot to other states.
 
 | **State**        | **Description**                              | **Functions**                            |
 | ---------------- | -------------------------------------------- | ---------------------------------------- |
@@ -16,7 +16,7 @@ The bot can be in one state at a time and have access to a set of functions that
 | `SHOP`           | Buy items and move to the next round         | `shop`                                   |
 | `GAME_OVER`      | Game has ended                               | –                                        |
 
-Developing a bot boils down to provide the action name and its parameters for each of the
+Developing a bot boils down to providing the action name and its parameters for each state.
 
 ### State Diagram
 
@@ -25,9 +25,9 @@ The following diagram illustrates the possible states of the game and how the fu
 - Start (◉) and End (⦾) states
 - States are written in uppercase (e.g., `MENU`, `BLIND_SELECT`, ...)
 - Functions are written in lowercase (e.g., `start_run`, `skip_or_select_blind`, ...)
-- Functions parameters are written in italics (e.g., `action = play_hand`). Not all parameters are reported in the diagram.
+- Function parameters are written in italics (e.g., `action = play_hand`). Not all parameters are reported in the diagram.
 - Comments are reported in parentheses (e.g., `(win round)`, `(lose round)`).
-- Abstract groups are written with Capital letters (e.g., `Run`, `Round`, ...)
+- Abstract groups are written with capital letters (e.g., `Run`, `Round`, ...)
 
 <div style="text-align: center">
 

docs/index.md

@@ -17,34 +17,31 @@ BalatroBot is a Python framework designed to help developers create automated bo
 
     ---
 
-    Complete setup guide covering prerequisites, Steamodded mod installation,
-    Python environment setup.
+    Setup guide covering prerequisites, Steamodded mod installation, and Python environment setup.
 
     [:octicons-arrow-right-24: Installation](installation.md)
 
 - :material-robot:{ .lg .middle } __Developing Bots__
 
     ---
 
-    Learn to develop bots, complete code examples,
-    class structure, game state handling.
+    Learn to develop bots with complete code examples, class structure, and game state handling.
 
     [:octicons-arrow-right-24: Developing Bots](developing-bots.md)
 
 - :material-api:{ .lg .middle } __Protocol API__
 
     ---
 
-    Technical reference for TCP socket communication, message formats,
-    game states, action types.
+    Technical reference for TCP socket communication, message formats, game states, and action types.
 
     [:octicons-arrow-right-24: Protocol API](protocol-api.md)
 
 - :octicons-sparkle-fill-16:{ .lg .middle } __Documentation for LLM__
 
     ---
 
-    Documentation in [llms.txt](https://llmstxt.org/) formats. Just paste the following link (or it's content) into the LLM chat.
+    Documentation in [llms.txt](https://llmstxt.org/) format. Just paste the following link (or its content) into the LLM chat.
 
     [:octicons-arrow-right-24: llms-full.txt](llms-full.txt)
 

docs/installation.md

@@ -8,9 +8,9 @@ Before installing BalatroBot, ensure you have:
 
 - **[balatro](https://store.steampowered.com/app/2379780/Balatro/)**: Steam version (>= 1.0.1)
 - **[git](https://git-scm.com/downloads)**: for cloning the repository
-- **[uv](https://docs.astral.sh/uv/)**: for managing Python installations, environments and dependencies
+- **[uv](https://docs.astral.sh/uv/)**: for managing Python installations, environments, and dependencies
 - **[lovely](https://github.com/ethangreen-dev/lovely-injector)**: for injecting Lua code into Balatro (>= 0.8.0)
-- **[steamodded](https://github.com/Steamodded/smods)**: for loading and injecting mods (>=1.0.0)
+- **[steamodded](https://github.com/Steamodded/smods)**: for loading and injecting mods (>= 1.0.0)
 
 ## Step 1: Install BalatroBot
 
@@ -134,10 +134,10 @@ BalatroBot is installed like any other Steamodded mod.
         rm -rf balatrobot
         ```
 
-## Step 2: Setup Python Environment
+## Step 2: Set Up Python Environment
 
-Uv takes care of managing Python installations, virtual environments creation and dependencies installation.
-To setup the Python environment for running BalatroBot bots simply run:
+Uv takes care of managing Python installations, virtual environment creation, and dependency installation.
+To set up the Python environment for running BalatroBot bots, simply run:
 
 === "Windows"
 
@@ -247,8 +247,8 @@ The bot is working correctly if:
 
 1. Game starts automatically
 2. Cards are played/discarded automatically
-3. Win the first round
-4. Game progresses through rounds
+3. Win the first blind
+4. Game progresses through blinds
 
 ## Troubleshooting
 

docs/logging-systems.md

@@ -4,7 +4,7 @@ BalatroBot implements three distinct logging systems to support different aspect
 
 1. [**JSONL Run Logging**](#jsonl-run-logging) - Records complete game runs for replay and analysis
 2. [**Python SDK Logging**](#python-sdk-logging) - Future logging capabilities for the Python framework
-3. [**Mod Logging**](#mod-logging) - Traditional streamodded logging for mod development and debugging
+3. [**Mod Logging**](#mod-logging) - Traditional Steamodded logging for mod development and debugging
 
 ## JSONL Run Logging