Repository navigation
docs: refine Polish and English frontend localization - #64
Merged
Merged
Conversation
Review all six documentation sections and shared frontend copy, add the required applications entry, and correct misleading technical wording. Preserve formulas, identifiers and interpolation slots; include the complete bilingual correction report and updated copy checks.
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
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.
Summary
Review and improve Polish and English frontend copy, with particular attention to all six /docs tabs. Add the supplied About paragraphs and all four Applications entries, including intended traffic-management benefits.
docs/engineering/history/2026-10-30-localization-review.md.Verification
Contract or safety impact
Editorial changes only. No routing, state-management, API, simulation, CSS or dependency changes. Intended future traffic benefits remain separate from the current simulation’s capabilities.
Follow-ups
None requiring a product decision. User approved publication after reviewing the implementation and report.