Drop the pronunciation guidance from the naming note - #28
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes "PAR-ti-keps" from all four places the naming note carried it:
README.md,docs/participant-guide.md, and both locales ofweb/src/lib/participant/copy.ts. The etymology stays — it is what the note is for — and each sentence was rewritten rather than truncated.web/tests/participant-copy.spec.tspinned the pronunciation as its proof that the note exists at all. That anchor moves toLatin/拉丁文, which is stable and still fails if the note is dropped. The assertions on the limits half are untouched: those are the ones that stop a later edit leaving a claim of participant control the app does not provide.pnpm run check,pnpm run test(204), andpnpm run buildpass.