Bug 2035348

Summary: Fix two grammar issues in kubevirt-plugin.json strings
Product: OpenShift Container Platform Reporter: ralpert
Component: Console Kubevirt PluginAssignee: Guohua Ouyang <gouyang>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.10CC: aos-bugs, gouyang
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-12 04:40:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description ralpert 2021-12-23 17:15:15 UTC
Description of problem:
We got some new translations back. We look through them for obvious bugs and noticed a couple of grammar issues in the original OpenShift strings. Would you be able to fix them?

"You do not have permissions to create Virtual Machine. Contact your system administrator for more information." - Should it be "You do not have permissions to create Virtual Machines." or "You do not have permissions to create the Virtual Machine."?

"Are you sure you want to cancel importing {{vmImportElem}}? It will also delete the newly created {{vmElem}} in the {{nsElem}} namespace?" - the last question mark (?) should probably be a period.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Look at kubevirt-plugin.json or search the kubevirt plugin for the above strings

Actual results:
There are some grammar issues.

Expected results:
Grammar is ok.

Additional info:

Comment 5 errata-xmlrpc 2022-03-12 04:40:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.