Skip to content

docs: fix 5 typos across README and guides#32

Open
guvennsade-tech wants to merge 1 commit into
mergeworthy:mainfrom
guvennsade-tech:fix-typo-contribution-1
Open

docs: fix 5 typos across README and guides#32
guvennsade-tech wants to merge 1 commit into
mergeworthy:mainfrom
guvennsade-tech:fix-typo-contribution-1

Conversation

@guvennsade-tech
Copy link
Copy Markdown

PR: Fix 5 documentation typos across README and guides

Summary

Batch-fixes five reported spelling errors across the repository's main README and guide files. Each fix is minimal, surgical, and touches only the typo itself.

Related Issues

Closes #1contibutioncontribution in README.md
Closes #2developpersdevelopers in README.md
Closes #3responsivnessresponsiveness in finding-good-first-issues.md
Closes #4unfimiliarunfamiliar in reading-a-codebase.md
Closes #5comittingcommitting in your-first-pr-checklist.md

Changes

File Before After
README.md contibution contribution
README.md developpers developers
guides/finding-good-first-issues.md responsivness responsiveness
guides/reading-a-codebase.md unfimiliar unfamiliar
guides/your-first-pr-checklist.md comitting committing

Checklist

  • Each typo verified in source before edit
  • No other content altered
  • Conventional commit format (docs:)
  • All referenced issues linked in commit body

Time invested

~8 minutes total (scan + fix + verify + commit + PR write-up)


Submitted via ROI-Agent autonomous workflow

- contibution → contribution (README.md) — Closes mergeworthy#1
- developpers → developers (README.md) — Closes mergeworthy#2
- responsivness → responsiveness (finding-good-first-issues.md) — Closes mergeworthy#3
- unfimiliar → unfamiliar (reading-a-codebase.md) — Closes mergeworthy#4
- comitting → committing (your-first-pr-checklist.md) — Closes mergeworthy#5
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! This looks like your first pull request to this repo — welcome. 🎉

A maintainer will take a look soon. While you wait:

  • Make sure CI is green (the markdown lint check is informational and won't block your merge).
  • Feel free to update the PR with more commits if you spot something — we won't squash until merge.
  • If we ask for changes, that's normal — every PR, including ones from senior engineers, gets feedback.

Thanks for contributing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant