Two typo fixes in the learning content:
learn/javascript/Classes.md:32 — "Let's add a name propery to the class" → "property"learn/tutorials/Earthquakes.md:353 — "and runing methods" → "running"
Tutorial prose only. I deliberately left the many similar spellings under resources/content/archive/** alone — those files reproduce real contributors' issue and PR comments verbatim, so correcting them would alter quoted text.
Pull request overview
Fixes two spelling mistakes in the learning documentation to improve readability and reduce confusion in tutorial prose.
Changes:
- Corrected “runing” → “running” in the Earthquakes tutorial lab section.
- Corrected “propery” → “property” in the JavaScript Classes learning content.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File |
Description |
| learn/tutorials/Earthquakes.md |
Fixes a typo in the debugging lab description (“running”). |
| learn/javascript/Classes.md |
Fixes a typo in the class property introduction (“property”). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
@neo-opus-grace (APPROVED) reviewed on 2026-08-23T16:39:39Z
Class: micro — two single-word prose corrections in learning content; no code, no contract, no architectural concept.
Verdict: Approved
Welcome, and thank you — this is a genuinely good first contribution, for a reason that has nothing to do with its size.
Glance: Verified both fixes at head e6ece54c01 against the exact-head sources rather than the diff alone. learn/javascript/Classes.md:32 — "propery" → "property", and the sentence sits in prose describing a name config, not in a code block or an identifier; I checked that propery appears nowhere in src/** or apps/** as a real symbol, so nothing is being renamed out from under code. learn/tutorials/Earthquakes.md:353 — "runing" → "running", likewise prose, inside the debugging lab. The one thing I went looking for and did not find: any remaining whole-word instance of either typo under learn/**. There are none, so the sweep of the surface you targeted is complete rather than partial. All checks green.
Findings: None.
The part worth calling out is your PR body, not your diff.
"I deliberately left the many similar spellings under resources/content/archive/** alone — those files reproduce real contributors' issue and PR comments verbatim, so correcting them would alter quoted text."
That is exactly right, and it is a repository convention you inferred rather than one anybody told you. Those archived files are a record of what people actually wrote; silently improving someone's spelling inside a quotation makes the record less true, and a "harmless" tidy-up there would have been a real regression. Most first contributions here get larger to look more substantial. Yours got smaller on purpose, and explained why — that is the harder instinct and the more useful one.
One small precision, since you were precise with me: on those two specific words, a whole-word search of resources/content/archive/** returns nothing, so the restraint you describe applies to the broader class of similar spellings rather than to these exact two. That does not weaken the principle at all — I mention it only because your note was careful enough to deserve a careful answer.
On Earthquakes.md specifically: that tutorial was written by @maxrahder years ago, long before this repository had any AI tooling in it. It has outlived the era it was written in, and it is still being read closely enough by a newcomer for a single doubled-letter slip to get caught. That says something good about the guide, and something good about how you read it.
No required actions — eligible for human merge. I hope this is the first of several.
- Origin Session ID: eb671e6e-ca17-4a53-8069-64fd5885ce84
🖖 Grace (Claude Opus 5, Claude Code). Eligibility rules: pr-review-guide §6.4.
Two typo fixes in the learning content:
learn/javascript/Classes.md:32— "Let's add anamepropery to the class" → "property"learn/tutorials/Earthquakes.md:353— "and runing methods" → "running"Tutorial prose only. I deliberately left the many similar spellings under
resources/content/archive/**alone — those files reproduce real contributors' issue and PR comments verbatim, so correcting them would alter quoted text.Pull request overview
Fixes two spelling mistakes in the learning documentation to improve readability and reduce confusion in tutorial prose.
Changes:
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
💡 Add a
code-reviewagent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.@neo-opus-grace(APPROVED) reviewed on 2026-08-23T16:39:39ZClass: micro — two single-word prose corrections in learning content; no code, no contract, no architectural concept.
Verdict: Approved
Welcome, and thank you — this is a genuinely good first contribution, for a reason that has nothing to do with its size.
Glance: Verified both fixes at head
e6ece54c01against the exact-head sources rather than the diff alone.learn/javascript/Classes.md:32— "propery" → "property", and the sentence sits in prose describing anameconfig, not in a code block or an identifier; I checked thatproperyappears nowhere insrc/**orapps/**as a real symbol, so nothing is being renamed out from under code.learn/tutorials/Earthquakes.md:353— "runing" → "running", likewise prose, inside the debugging lab. The one thing I went looking for and did not find: any remaining whole-word instance of either typo underlearn/**. There are none, so the sweep of the surface you targeted is complete rather than partial. All checks green.Findings: None.
The part worth calling out is your PR body, not your diff.
That is exactly right, and it is a repository convention you inferred rather than one anybody told you. Those archived files are a record of what people actually wrote; silently improving someone's spelling inside a quotation makes the record less true, and a "harmless" tidy-up there would have been a real regression. Most first contributions here get larger to look more substantial. Yours got smaller on purpose, and explained why — that is the harder instinct and the more useful one.
One small precision, since you were precise with me: on those two specific words, a whole-word search of
resources/content/archive/**returns nothing, so the restraint you describe applies to the broader class of similar spellings rather than to these exact two. That does not weaken the principle at all — I mention it only because your note was careful enough to deserve a careful answer.On
Earthquakes.mdspecifically: that tutorial was written by @maxrahder years ago, long before this repository had any AI tooling in it. It has outlived the era it was written in, and it is still being read closely enough by a newcomer for a single doubled-letter slip to get caught. That says something good about the guide, and something good about how you read it.No required actions — eligible for human merge. I hope this is the first of several.
🖖 Grace (Claude Opus 5, Claude Code). Eligibility rules: pr-review-guide §6.4.