Two lines the register pass could not have seen

[MongLong0214]

#753 converged README.ko.md on 한다체 with six exceptions following one rule: address the reader and it stays polite, describe the product and it does not.

Two lines break it, and neither was in that branch's diff. #751 wrote them — replacing the protocol section with a pointer — and the two branches never saw each other.

- record는 … 대개는 작은 것으로 충분합니다:
+ record는 … 대개는 작은 것으로 충분하다:

- … 방법은 docs/protocol.md에 있습니다. 규범적 정의는 SPEC §3입니다.
+ … 방법은 docs/protocol.md에 있다. 규범적 정의는 SPEC §3이다.

Both describe where a document is. Nobody is addressed, so both take the plain form the surrounding paragraphs use.

My own count was wrong, and the reason is worth recording

The review counted fourteen polite lines. I counted twenty-five.

아니다 contains 니다. A pattern matching that syllable alone reports every plain-form negation as polite — and this document has many, because refusing an overclaim is what it does:

:182  … 모든 commit에 record가 생긴다는 뜻이 아니다.
:303  이것은 전달을 잰 것이지 효과를 잰 것이 아니다.
:377  또 하나의 메모리 데이터베이스가 아니다.

The precise pattern gives fourteen, and all fourteen are documented exceptions:

17-30    the hero paragraph — addressed to the reader
46-47    contents links — anchor text for the two headings below
105      the CTA
192      "설치하기 전에 읽어보세요"
277,290  headings — anchor targets, and ja/zh parity

Limit

Nothing checks this. The rule lives in the PR that established it and in a comment. The next section written in the wrong register will land the same way these did — from a branch that never touched the file the rule was recorded on.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/main..ca4f99b44c77718a99cbd700264a3eaa2d1f6553
Active constraints: not read — commitlore: the index is incomplete: the build stopped after its time budget with 779 commit(s) or note(s) unread — records in them are missing from this answer. fix: commitlore init (or commitlore index) to finish the index (1 changed path)

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}