Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.8] Bug 1975559: Fix typo in olm message #9334

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -43,8 +43,8 @@
"Plugin available": "Plugin available",
"None": "None",
"No Operators found": "No Operators found",
"No Operators are availalble for project {{project}}.": "No Operators are availalble for project {{project}}.",
"No Operators are availalble.": "No Operators are availalble.",
"No Operators are available for project {{project}}.": "No Operators are available for project {{project}}.",
"No Operators are available.": "No Operators are available.",
"Discover and install Operators from the <1>OperatorHub</1>.": "Discover and install Operators from the <1>OperatorHub</1>.",
"Name": "Name",
"Namespace": "Namespace",
Expand Down
Expand Up @@ -557,10 +557,10 @@ const CSVListNoDataEmptyMsg = () => {
const { t } = useTranslation();
const project = useActiveNamespace();
const noOperatorsInSingleNamespaceMessage = t(
'olm~No Operators are availalble for project {{project}}.',
'olm~No Operators are available for project {{project}}.',
{ project },
);
const noOperatorsInAllNamespacesMessage = t('olm~No Operators are availalble.');
const noOperatorsInAllNamespacesMessage = t('olm~No Operators are available.');
const detail = (
<>
<div>
Expand Down