fix(l10n): align the stores dialog with the setup trust hint (Sie-form, plain language)
Some checks failed
Security / Security check (push) Failing after 1s
Some checks failed
Security / Security check (push) Failing after 1s
The regulated setup path sends the operator to the stores dialog to pin a publisher key — but the field was labelled 'Angepinnter Public-Key — PEM (optional)' with du-form developer prose (PEM, vendor key) at exactly the trust-critical moment. Field now reads 'Signatur-Schlüssel anheften (PEM, optional)' with a plain-language Sie-form explanation of what pinning does; the dialog intro and the onboarding checklist follow (MCP jargon explained in the sentence, developer-only follow-up cards labelled as such). Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
parent
ddac84ce8e
commit
7888b71f63
5 changed files with 18 additions and 19 deletions
|
|
@ -925,12 +925,11 @@ class AppLocalizationsEn extends AppLocalizations {
|
|||
String get storesManagerAddShort => 'Add';
|
||||
|
||||
@override
|
||||
String get storesManagerPinnedKeyLabel =>
|
||||
'Pinned public key — PEM (optional)';
|
||||
String get storesManagerPinnedKeyLabel => 'Pin a signing key (PEM, optional)';
|
||||
|
||||
@override
|
||||
String get storesManagerPinnedKeyHint =>
|
||||
'Signed modules from this store verify against this key instead of the built-in vendor key. Paste a PEM public key.';
|
||||
'Only modules signed with this key are accepted from this source. Paste the publisher\'s public key (PEM) — used instead of the built-in vendor key.';
|
||||
|
||||
@override
|
||||
String get storesManagerNotAvailable => 'Not available yet';
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue