fix typo

Author: MaxGraey

CONTRIBUTING.md

@@ -58,7 +58,7 @@ Guidelines for **AI**-assisted Contributions
 
 * Stay accountable: only submit changes you understand and can justify; be ready to explain behavior, edge cases, and alignment with Kvrocks conventions. If an **AI** suggestion feels unclear, rewrite or drop it.
 * Keep humans in the loop: discuss non-trivial ideas early via [Issues](https://github.com/AssemblyScript/assemblyscript/issues) or [Discord](https://discord.gg/assemblyscript), especially when you are unsure about design or impact.
-* Use **AI** for acceleration, optimizarion and verification: treat **AI** output as a draft for code, tests, or docs; run linters/tests and review the logic **yourself**.
+* Use **AI** for acceleration, optimization and verification: treat **AI** output as a draft for code, tests, or docs; run linters/tests and review the logic **yourself**.
 * Be transparent in PRs: note briefly if **AI** was used and for what (e.g., initial draft, test scaffolding), and call out any parts where you want extra review.
 * Respect ASF policy: ensure generated content does not introduce incompatible licenses or undisclosed third-party code; review the ASF Generative Tooling Guidance and licensing rules when in doubt.
 * Prefer small patches over large dumps; if you cannot confidently explain an **AI**-produced change, open a well-described issue instead.