Refine dependency wording

Co-authored-by: Tuntii <121901995+Tuntii@users.noreply.github.com>

Author: Copilot

docs/PHILOSOPHY.md

@@ -105,9 +105,9 @@ validator = "0.16"
 2. We bump `rustapi-rs` to `0.2.0`
 3. **Your code stays exactly the same** — just update the version
 
-### External Dependency Reduction (Dış Bağımlılıkları Azaltma)
+### External Dependency Reduction (Harici Bağımlılıkları Azaltma)
 
-RustAPI already hides external crates behind internal adapters. To reduce dependency debt, we focus on components with a stable spec and a small surface area, while keeping the public API unchanged. The playbook is:
+RustAPI already hides external crates behind internal adapters. To reduce dependency debt, we focus on components, each with a stable spec and a small surface area, while keeping the public API unchanged. The playbook is:
 
 1. Wrap dependencies with internal traits/types so behavior is defined by RustAPI.
 2. Add contract tests to lock in behavior before replacing internals.

docs/README.md

@@ -30,7 +30,7 @@ RustAPI provides a stable, ergonomic public API. Internal dependencies (`hyper`,
 
 ### External Dependency Plan
 
-To reduce external dependency debt (dış borç), we prioritize replacing crates with stable specs and small surfaces while keeping the public API unchanged. Candidate areas for RustAPI-owned implementations are validation, routing, OpenAPI generation, and the TOON format. Foundational runtime and HTTP crates (`tokio`, `hyper`, `tower`) remain external for stability and security.
+To reduce external dependency debt (bağımlılık borcu), we prioritize replacing crates with stable specs and small surfaces, while keeping the public API unchanged. Candidate areas for RustAPI-owned implementations are validation, routing, OpenAPI generation, and the TOON format. Foundational runtime and HTTP crates (`tokio`, `hyper`, `tower`) remain external for stability and security.
 
 ## Getting Started