fix(CONTRIBUTING): improved reading experiences and fixed some typos

Author: caarloshenriq

CONTRIBUTING.md

@@ -27,7 +27,7 @@ We welcome:
 - **Topic summaries** (background, trade-offs, relevant work)
 - **Resource lists** (papers, PRs, BIPs, mailing-list threads)
 - **Corrections/improvements** (typos, clarifications, structure)
-- **New templates** that improve contributor experience
+- **New templates** that improve the contributor experience
 
 We avoid:
 
@@ -38,7 +38,7 @@ We avoid:
 
 ## Contribution workflow
 
-1. **Open an Issue** (optional but recommended for bigger changes) and describe what you'fll add or fix.
+1. **Open an Issue** (optional but recommended for bigger changes) and describe what you'll add or fix.
 2. **Fork** the repo and create a feature branch:
 
        git checkout -b docs/2025-10-seminar-notes
@@ -78,15 +78,6 @@ If you create the branch from the GitHub UI, try to avoid generic names like `pa
 
 ## Commit message conventions
 
-We follow a lightweight style similar to what is already used in `saopaulobitdevs.org`, for example:
-
-- `feat: november meetup`
-- `feat(header): add X (@saopaulobitdevs) link to navigation`
-- `feat(_posts): arkade announcement`
-- `fix(_posts): use xcancel. fuck X`
-- `fix broken link and remove two topics`
-- `2025-09 (#68)`
-
 General rules:
 
 - Write commit messages in **English**.
@@ -110,12 +101,12 @@ Common types:
 Examples for this repository:
 
 - `feat(topics): add socratic seminar 040`
-- `feat(posts): add november 2025 meetup`
+- `feat(posts): add nov 2025 meetup`
 - `fix(links): update delvingbitcoin URLs for september`
 - `docs: add contribution guidelines`
 - `chore(posts): reorder sections by topic`
 
-If you are working on a seminar topic file and that's the only change in the PR, a short and focused subject like below is fine:
+If you are working on a seminar topic file and that's the only change in the PR, a short and focused subject like the one below is fine:
 
 - `2025-09: add socratic seminar topics`