Skip to content

Fix grammar: missing "its" in "not yet turn" - #72

Open
lunar-me wants to merge 2 commits into
KimGLee:mainfrom
lunar-me:fix-docs/grammar-minor-002
Open

Fix grammar: missing "its" in "not yet turn"#72
lunar-me wants to merge 2 commits into
KimGLee:mainfrom
lunar-me:fix-docs/grammar-minor-002

Conversation

@lunar-me

Copy link
Copy Markdown

Summary

This PR fixes a grammar issue in kernel/K13 Task Runtime and Execution Control/10 Batch Admission Transitions and Serial Integration.md (line 17).

Problem

Missing possessive pronoun "its" — "not yet turn" should be "not yet its turn".

The problematic text:

such a batch looks merely "not yet turn"

Fix

Replaced with:

such a batch looks merely "not yet its turn"

Type of Change

  • Documentation fix (grammar, spelling, logical error)
  • Code change
  • Breaking change

Checklist

  • Documentation files only
  • No code changes
  • Fix verified against original text

KimGLee commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Thank you for identifying and correcting the missing possessive pronoun. The change from not yet turn to not yet its turn is grammatically correct, preserves the intended meaning, and is made in the correct authoritative Kernel source.

Review outcome: Changes Requested — merge after the required governance write-back is completed.

Changing K13/10 changes the measured file size from 8,806 to 8,810 bytes and invalidates the source hashes of five dependent Cards. The current CI failure is therefore expected: the PR is missing the deterministic derived updates.

Please:

  1. update the K13/10 measurement in K00/16 from 8806 to 8810;
  2. regenerate/stamp R03, R06, R07, R10, and R11;
  3. synchronize the branch with the current main; and
  4. rerun the required checks.

After those write-back changes are included, this PR is suitable to merge. It is also the best integration PR for the related wording improvements in #71 and #73, because it already creates a legitimate K00/16 and R07 regeneration boundary.

For future contributions, please open an Issue first so that the problem, authority layer, and required derived artifacts can be agreed before implementation. Then open a linked PR using a reference such as Closes #<issue-number>. This keeps the governance trail and review scope clear.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants