Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@web/src/i18n/locales/uk/common.json`:
- Line 145: The Ukrainian text in the subtitle property at line 145 contains an
incorrect word form. The phrase "невідомі краї" is grammatically incomplete or
incorrect in Ukrainian. Correct this phrase to use the proper noun form that
accurately conveys "unknown lands" or "unknown areas" in Ukrainian, ensuring the
text reads naturally and is grammatically correct for the 404 error page
context.

In `@web/src/i18n/locales/uk/crossseed.json`:
- Line 15: The Ukrainian adjective in the "description" field has incorrect
gender agreement with the noun. Change "Автоматичний опитування" to "Автоматичне
опитування" to properly match the neuter gender of the noun "опитування"
(survey/polling).

In `@web/src/i18n/locales/uk/settings.json`:
- Around line 626-627: The validation error messages in the Ukrainian locale
file contain corrupted mixed-language artifacts where "requiчервоний" and
"requiчервоні" appear in the strings for apiKeyRequired and
baseUrlAndApiKeyRequired. These should be replaced with the correct Ukrainian
translations to provide clear validation feedback to users. Fix the corrupted
text in both the apiKeyRequired message (line 626) and baseUrlAndApiKeyRequired
message (line 627) by replacing the garbled "requiчервоний"/"requiчервоні"
portions with the proper Ukrainian word for "required" (обов'язковий). Apply the
same fix to any other instances of this corruption pattern in the file (such as
at line 782 mentioned in the comment).
- Around line 262-267: The translation file contains translated protocol scheme
examples and technical literals that must remain in their canonical English
form. In the examples object at lines 262-267, the "discord" key should not be
translated from "discord" to "розбрат", and the protocol scheme formats must
stay exactly as canonical literals (e.g., "discord://token@id" and
"notifiarr://apikey"). Keep only the descriptive text portions translated while
preserving all protocol schemes, command names, and technical examples in their
original form. The same issue also applies at lines 521-529, so update all
affected example literals throughout the file to use the canonical English forms
for protocols and scheme names while maintaining Ukrainian translations for the
surrounding description text.

In `@web/src/i18n/locales/uk/torrents.json`:
- Line 644: The remove key in the torrents.json Ukrainian locale file contains a
mixed-language string where Categor{{plural}} is partially English with an
untranslated fragment. Replace the incomplete English word Categor with the
proper Ukrainian translation for "Category" while preserving both the {{count}}
and {{plural}} placeholders exactly as they are, ensuring the complete
translated string reads naturally in Ukrainian and matches the intended
pluralization behavior.
- Line 19: The translation for the resume key in
web/src/i18n/locales/uk/torrents.json is incorrect. The current value "Резюме"
means "summary" but should convey the action of resuming or continuing a
torrent. Replace "Резюме" with the appropriate Ukrainian action verb meaning
"resume/continue" at line 19 (anchor location). Apply the same corrected
translation at line 47 (sibling location) where this same mistranslation also
appears.