Merge pull request #87010 from openshift-cherrypick-robot/cherry-pick-86982-to-enterprise-4.18

[enterprise-4.18] Use a consistent description for the "kebab" menu

applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 The *Developer* perspective in the web console provides you the following options from the *+Add* view to create applications and associated services and deploy them on {product-title}:
 
-* *Getting started resources*: Use these resources to help you get started with Developer Console. You can choose to hide the header using the *Options* menu {kebab}.
+* *Getting started resources*: Use these resources to help you get started with Developer Console. You can choose to hide the header using the Options menu {kebab}.
 ** *Creating applications using samples*: Use existing code samples to get started with creating applications on the {product-title}.
 ** *Build with guided documentation*: Follow the guided documentation to build applications and familiarize yourself with key concepts and terminologies.
 ** *Explore new developer features*: Explore the new features and resources within the *Developer* perspective.

contributing_to_docs/doc_guidelines.adoc

@@ -820,7 +820,7 @@ user-defined entity added to the `common-attributes.adoc` module:
 When using inline, include the image after the UI element name. For example:
 
 ----
-Click the *Options* menu {kebab}.
+Click the Options menu {kebab}.
 ----
 
 ==== Inserting images inline without reuse

modules/builds-basic-edit-buildconfig.adoc

@@ -16,7 +16,7 @@ You can switch between the *Form view* and *YAML view* without losing any data.
 
 .Procedure
 
-. In the *Builds* view of the *Developer* perspective, click the menu {kebab} to see the *Edit BuildConfig* option.
+. In the *Builds* view of the *Developer* perspective, click the Options menu {kebab} to see the *Edit BuildConfig* option.
 . Click *Edit BuildConfig* to see the *Form view* option.
 . In the *Git* section, enter the Git repository URL for the codebase you want to use to create an application. The URL is then validated.
 * Optional: Click *Show Advanced Git Options* to add details such as:

modules/deleting-machine-pools-ocm.adoc

@@ -32,7 +32,7 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 
 . On the selected cluster, select the *Machine pools* tab.
 
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to delete.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to delete.
 
 . Click *Delete*.
 +

modules/deleting-machine-pools.adoc

@@ -30,7 +30,7 @@ ifndef::openshift-rosa,openshift-rosa-hcp[]
 
 . On the selected cluster, select the *Machine pools* tab.
 
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to delete.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to delete.
 . Click *Delete*.
 
 The selected machine pool is deleted.

modules/deployments-ab-testing-lb.adoc

@@ -103,7 +103,7 @@ spec:
 
 . Navigate to the *Networking* -> *Routes* page.
 
-. Click the Actions menu {kebab} next to the route you want to edit and select *Edit Route*.
+. Click the Options menu {kebab} next to the route you want to edit and select *Edit Route*.
 
 . Edit the YAML file. Update the `weight` to be an integer between `0` and `256` that specifies the relative weight of the target against other target reference objects. The value `0` suppresses requests to this back end. The default is `100`. Run `oc explain routes.spec.alternateBackends` for more information about the options.
 

modules/disabling-insights-advisor-recommendations.adoc

@@ -26,7 +26,7 @@ Disabling a recommendation for all of your clusters also applies to any future c
 . Disable an alert by using one of the following methods:
 +
 * To disable an alert:
-.. Click the *Options* menu {kebab} for that alert, and then click *Disable recommendation*.
+.. Click the Options menu {kebab} for that alert, and then click *Disable recommendation*.
 .. Enter a justification note and click *Save*.
 +
 * To view the clusters affected by this alert before disabling the alert:

modules/enabling-insights-advisor-recommendations.adoc

@@ -22,4 +22,4 @@ When a recommendation is disabled for all clusters, you no longer see the recomm
 .. From the *Filter by status* drop-down menu, select *Disabled*.
 .. Optional: Clear the *Clusters impacted* filter.
 . Locate the recommendation to enable.
-. Click the *Options* menu {kebab}, and then click *Enable recommendation*.
+. Click the Options menu {kebab}, and then click *Enable recommendation*.

modules/insights-operator-enable-obfuscation.adoc

@@ -30,13 +30,13 @@ The following procedure enables obfuscation using the `support` secret in the `o
 . Navigate to *Workloads* -> *Secrets*.
 . Select the *openshift-config* project.
 . Search for the *support* secret using the *Search by name* field. If it does not exist, click *Create* -> *Key/value secret* to create it.
-. Click the *Options* menu {kebab}, and then click *Edit Secret*.
+. Click the Options menu {kebab}, and then click *Edit Secret*.
 . Click *Add Key/Value*.
 . Create a key named `enableGlobalObfuscation` with a value of `true`, and click *Save*.
 . Navigate to *Workloads* -> *Pods*
 . Select the `openshift-insights` project.
 . Find the `insights-operator` pod.
-. To restart the `insights-operator` pod, click the *Options* menu {kebab}, and then click *Delete Pod*.
+. To restart the `insights-operator` pod, click the Options menu {kebab}, and then click *Delete Pod*.
 
 .Verification
 

modules/manually-removing-cloud-creds.adoc

@@ -36,4 +36,4 @@ Prior to a non z-stream upgrade, you must reinstate the credential secret with t
 
 |===
 
-. Click the *Options* menu {kebab} in the same row as the secret and select *Delete Secret*.
+. Click the Options menu {kebab} in the same row as the secret and select *Delete Secret*.

modules/manually-rotating-cloud-creds.adoc

@@ -78,7 +78,7 @@ endif::mint[]
 
 |===
 
-. Click the *Options* menu {kebab} in the same row as the secret and select *Edit Secret*.
+. Click the Options menu {kebab} in the same row as the secret and select *Edit Secret*.
 
 . Record the contents of the *Value* field or fields. You can use this information to verify that the value is different after updating the credentials.
 

modules/network-observability-operator-uninstall.adoc

@@ -12,15 +12,15 @@ You can uninstall the Network Observability Operator using the {product-title} w
 
 . Remove the `FlowCollector` custom resource.
 .. Click *Flow Collector*, which is next to the *Network Observability Operator* in the *Provided APIs* column.
-.. Click the options menu {kebab} for the *cluster* and select *Delete FlowCollector*.
+.. Click the Options menu {kebab} for the *cluster* and select *Delete FlowCollector*.
 . Uninstall the Network Observability Operator.
 .. Navigate back to the *Operators* -> *Installed Operators* area.
-.. Click the options menu {kebab} next to the  *Network Observability Operator* and select *Uninstall Operator*.
+.. Click the Options menu {kebab} next to the  *Network Observability Operator* and select *Uninstall Operator*.
 .. *Home* -> *Projects* and select `openshift-netobserv-operator`
 .. Navigate to *Actions* and select *Delete Project*
 . Remove the `FlowCollector` custom resource definition (CRD).
 .. Navigate to *Administration* -> *CustomResourceDefinitions*.
-.. Look for *FlowCollector* and click the options menu {kebab}.
+.. Look for *FlowCollector* and click the Options menu {kebab}.
 .. Select *Delete CustomResourceDefinition*.
 +
 [IMPORTANT]

modules/nodes-cma-autoscaling-custom-uninstalling.adoc

@@ -35,7 +35,7 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 
 .. Click *Operators* -> *Installed Operators*.
 
-.. Find the *CustomMetricsAutoscaler*  Operator and click the *Options* menu {kebab} and select *Uninstall Operator*.
+.. Find the *CustomMetricsAutoscaler*  Operator and click the Options menu {kebab} and select *Uninstall Operator*.
 
 .. Click *Uninstall*.
 

modules/odc-monitoring-your-project-metrics.adoc

@@ -68,7 +68,7 @@ Use the following options to see further details:
 ** Use the *Notifications* toggle adjoining an alert rule to silence all the alerts for that rule, and then select the duration for which the alerts will be silenced from the *Silence for* list.
 You must have the permissions to edit alerts to see the *Notifications* toggle.
 
-** Use the *Options* menu {kebab} adjoining an alert rule to see the details of the alerting rule.
+** Use the Options menu {kebab} adjoining an alert rule to see the details of the alerting rule.
 
 . Optional: Use the *Events* tab to see the events for your project.
 +

modules/odc-rolling-back-helm-release.adoc

@@ -8,7 +8,7 @@ If a release fails, you can rollback the Helm release to a previous version.
 To rollback a release using the *Helm* view:
 
 . In the *Developer* perspective, navigate to the *Helm* view to see the *Helm Releases* in the namespace.
-. Click the *Options* menu {kebab} adjoining the listed release, and select *Rollback*.
+. Click the Options menu {kebab} adjoining the listed release, and select *Rollback*.
 . In the *Rollback Helm Release* page, select the *Revision* you want to rollback to and click *Rollback*.
 . In the *Helm Releases* page, click on the chart to see the details and resources for that release.
 . Go to the *Revision History* tab to see all the revisions for the chart.
@@ -16,4 +16,4 @@ To rollback a release using the *Helm* view:
 .Helm revision history
 image::odc_helm_revision_history.png[]
 +
-. If required, you can further use the *Options* menu {kebab} adjoining a particular revision and select the revision to rollback to.
+. If required, you can further use the Options menu {kebab} adjoining a particular revision and select the revision to rollback to.

modules/olm-removing-catalogs.adoc

@@ -21,4 +21,4 @@ As a cluster administrator, you can remove custom Operator catalogs that have be
 
 . Click the *Sources* tab.
 
-. Select the *Options* menu {kebab} for the catalog that you want to remove, and then click *Delete CatalogSource*.
+. Select the Options menu {kebab} for the catalog that you want to remove, and then click *Delete CatalogSource*.

modules/ossm-validate-smcp-kiali.adoc

@@ -38,7 +38,7 @@ image::ossm-kiali-overview.png[Kiali Overview page showing istio-system]
 +
 The tile for each namespace displays the number of labels, the *Istio Config* health, the number of and *Applications* health, and *Traffic* for the namespace. If you are validating the console installation and namespaces have not yet been added to the mesh, there might not be any data to display other than `istio-system`.
 
-. Kiali has four dashboards specifically for the namespace where the {SMProductShortName} control plane is installed.  To view these dashboards, click the *Options* menu {kebab} on the tile for the control plane namespace, for example, `istio-system`, and select one of the following options:
+. Kiali has four dashboards specifically for the namespace where the {SMProductShortName} control plane is installed.  To view these dashboards, click the Options menu {kebab} on the tile for the control plane namespace, for example, `istio-system`, and select one of the following options:
 
 ** *Istio Mesh Dashboard*
 ** *Istio Control Plane Dashboard*

modules/removing-cso-operator.adoc

@@ -12,7 +12,7 @@ To uninstall the Container Security Operator, you must uninstall the Operator an
 
 . On the {product-title} web console, click *Operators* -> *Installed Operators*.
 
-. Click the menu {kebab} of the Container Security Operator.
+. Click the Options menu {kebab} of the Container Security Operator.
 
 . Click *Uninstall Operator*. 
 

modules/rosa-adding-node-labels.adoc

@@ -181,7 +181,7 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 
 ifdef::openshift-dedicated[]
 . Navigate to {cluster-manager-url} and select your cluster.
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to add a label to.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to add a label to.
 . Select *Edit labels*.
 . If you have existing labels in the machine pool that you want to remove, select *x* next to the label to delete it.
 . Add a label using the format `<key>=<value>` and press enter. For example, add `app=db` and then press Enter. If the format is correct, the key value pair is then highlighted.

modules/rosa-adding-taints-ocm.adoc

@@ -24,7 +24,7 @@ endif::[]
 
 //ifdef::openshift-dedicated[]
 . Navigate to {cluster-manager-url} and select your cluster.
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to add a taint to.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to add a taint to.
 . Select *Edit taints*.
 . Add *Key* and *Value* entries for your taint.
 . Select an *Effect* for your taint from the drop-down menu. Available options include `NoSchedule`, `PreferNoSchedule`, and `NoExecute`.

modules/rosa-adding-taints.adoc

@@ -29,7 +29,7 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 ifdef::openshift-dedicated[]
 .Procedure
 . Navigate to {cluster-manager-url} and select your cluster.
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to add a taint to.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to add a taint to.
 . Select *Edit taints*.
 . Add *Key* and *Value* entries for your taint.
 . Select an *Effect* for your taint from the drop-down menu. Available options include `NoSchedule`, `PreferNoSchedule`, and `NoExecute`.

modules/rosa-delete-users.adoc

@@ -18,4 +18,4 @@ You can revoke the `dedicated-admin` or `cluster-admin` access of users through
 
 . On the *Cluster List* tab of {cluster-manager}, select the name of your cluster to view the cluster details.
 . Select *Access control* > *Cluster Roles and Access*.
-. For the user that you want to remove, click the *Options* menu {kebab} to the right of the user and group combination and click *Delete*.
+. For the user that you want to remove, click the Options menu {kebab} to the right of the user and group combination and click *Delete*.

modules/rosa-scaling-worker-nodes.adoc

@@ -82,7 +82,7 @@ endif::[]
 
 ifdef::openshift-dedicated[]
 . Navigate to {cluster-manager-url} and select your cluster.
-. Under the *Machine pools* tab, click the options menu {kebab} for the machine pool that you want to scale.
+. Under the *Machine pools* tab, click the Options menu {kebab} for the machine pool that you want to scale.
 . Select *Scale*.
 . Specify the node count:
 * If you deployed your cluster using a single availability zone, specify the *Node count* in the drop-down menu.

modules/sd-olm-removing-catalogs.adoc

@@ -21,4 +21,4 @@ As an administrator with the `dedicated-admin` role, you can remove custom Opera
 
 . Select *CatalogSource* from the *Resources* list.
 
-. Select the *Options* menu {kebab} for the catalog that you want to remove, and then click *Delete CatalogSource*.
+. Select the Options menu {kebab} for the catalog that you want to remove, and then click *Delete CatalogSource*.

modules/uninstall-cluster-logging-operator.adoc

@@ -19,22 +19,22 @@ You can stop aggregating logs by deleting the {clo} and the `ClusterLogging` cus
 
 . On the *Custom Resource Definition Details* page, click *Instances*.
 
-. Click the options menu {kebab} next to the instance, and click *Delete ClusterLogging*.
+. Click the Options menu {kebab} next to the instance, and click *Delete ClusterLogging*.
 
 . Go to the *Administration* -> *Custom Resource Definitions* page.
 
-. Click the options menu {kebab} next to *ClusterLogging*, and select *Delete Custom Resource Definition*.
+. Click the Options menu {kebab} next to *ClusterLogging*, and select *Delete Custom Resource Definition*.
 +
 [WARNING]
 ====
 Deleting the `ClusterLogging` CR does not remove the persistent volume claims (PVCs). To delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action. Releasing or deleting PVCs can delete PVs and cause data loss.
 ====
 
-. If you have created a `ClusterLogForwarder` CR, click the options menu {kebab} next to *ClusterLogForwarder*, and then click *Delete Custom Resource Definition*.
+. If you have created a `ClusterLogForwarder` CR, click the Options menu {kebab} next to *ClusterLogForwarder*, and then click *Delete Custom Resource Definition*.
 
 . Go to the *Operators* -> *Installed Operators* page.
 
-. Click the options menu {kebab} next to the {clo}, and then click *Uninstall Operator*.
+. Click the Options menu {kebab} next to the {clo}, and then click *Uninstall Operator*.
 
 . Optional: Delete the `openshift-logging` project.
 +
@@ -44,5 +44,5 @@ Deleting the `openshift-logging` project deletes everything in that namespace, i
 ====
 
 .. Go to the *Home* -> *Projects* page.
-.. Click the options menu {kebab} next to the *openshift-logging* project, and then click *Delete Project*.
+.. Click the Options menu {kebab} next to the *openshift-logging* project, and then click *Delete Project*.
 .. Confirm the deletion by typing `openshift-logging` in the dialog box, and then click *Delete*.

modules/uninstall-es-operator.adoc

@@ -18,17 +18,17 @@
 
 . On the *Custom Resource Definition Details* page, click *Instances*.
 
-. Click the options menu {kebab} next to the instance, and then click *Delete Elasticsearch*.
+. Click the Options menu {kebab} next to the instance, and then click *Delete Elasticsearch*.
 
 . Go to the *Administration* -> *Custom Resource Definitions* page.
 
-. Click the options menu {kebab} next to *Elasticsearch*, and select *Delete Custom Resource Definition*.
+. Click the Options menu {kebab} next to *Elasticsearch*, and select *Delete Custom Resource Definition*.
 
 . Delete the object storage secret.
 
 . Go to the *Operators* -> *Installed Operators* page.
 
-. Click the options menu {kebab} next to the {es-op}, and then click *Uninstall Operator*.
+. Click the Options menu {kebab} next to the {es-op}, and then click *Uninstall Operator*.
 
 . Optional: Delete the `openshift-operators-redhat` project.
 +
@@ -38,5 +38,5 @@ Do not delete the `openshift-operators-redhat` project if other global Operators
 ====
 
 .. Go to the *Home* -> *Projects* page.
-.. Click the options menu {kebab} next to the *openshift-operators-redhat* project, and then click *Delete Project*.
+.. Click the Options menu {kebab} next to the *openshift-operators-redhat* project, and then click *Delete Project*.
 .. Confirm the deletion by typing `openshift-operators-redhat` in the dialog box, and then click *Delete*.

modules/uninstall-logging-delete-pvcs.adoc

@@ -17,4 +17,4 @@ If you do not want to keep the PVCs, you can delete them. If you want to recover
 .Procedure
 
 . Go to the *Storage* -> *Persistent Volume Claims* page.
-. Click the options menu {kebab} next to each PVC, and select *Delete Persistent Volume Claim*.
+. Click the Options menu {kebab} next to each PVC, and select *Delete Persistent Volume Claim*.

modules/uninstall-loki-operator.adoc

@@ -18,17 +18,17 @@
 
 . On the *Custom Resource Definition Details* page, click *Instances*.
 
-. Click the options menu {kebab} next to the instance, and then click *Delete LokiStack*.
+. Click the Options menu {kebab} next to the instance, and then click *Delete LokiStack*.
 
 . Go to the *Administration* -> *Custom Resource Definitions* page.
 
-. Click the options menu {kebab} next to *LokiStack*, and select *Delete Custom Resource Definition*.
+. Click the Options menu {kebab} next to *LokiStack*, and select *Delete Custom Resource Definition*.
 
 . Delete the object storage secret.
 
 . Go to the *Operators* -> *Installed Operators* page.
 
-. Click the options menu {kebab} next to the {loki-op}, and then click *Uninstall Operator*.
+. Click the Options menu {kebab} next to the {loki-op}, and then click *Uninstall Operator*.
 
 . Optional: Delete the `openshift-operators-redhat` project.
 +
@@ -38,5 +38,5 @@ Do not delete the `openshift-operators-redhat` project if other global Operators
 ====
 
 .. Go to the *Home* -> *Projects* page.
-.. Click the options menu {kebab} next to the *openshift-operators-redhat* project, and then click *Delete Project*.
+.. Click the Options menu {kebab} next to the *openshift-operators-redhat* project, and then click *Delete Project*.
 .. Confirm the deletion by typing `openshift-operators-redhat` in the dialog box, and then click *Delete*.

modules/virt-creating-vm-from-snapshot-web.adoc

@@ -13,7 +13,7 @@ You can create a new VM by copying an existing snapshot.
 . Navigate to *Virtualization* -> *VirtualMachines* in the web console.
 . Select a VM to open the *VirtualMachine details* page.
 . Click the *Snapshots* tab.
-. Click the actions menu {kebab} for the snapshot you want to copy.
+. Click the Options menu {kebab} for the snapshot you want to copy.
 . Select *Create VirtualMachine*.
 . Enter the name of the virtual machine.
 . (Optional) Select the *Start this VirtualMachine after creation* checkbox to start the new virtual machine.

modules/virt-creating-windows-vm.adoc

@@ -43,6 +43,6 @@ The Windows image is uploaded to a PVC.
 .. Click *Create VirtualMachine*.
 .. On the *YAML* tab, replace `running:false` with `runStrategy: RerunOnFailure` and click *Save*.
 
-. Click the options menu {kebab} and select *Start*.
+. Click the Options menu {kebab} and select *Start*.
 +
 The VM boots from the `sysprep` disk containing the `autounattend.xml` answer file.

modules/virt-deleting-vm-snapshot-web.adoc

@@ -13,5 +13,5 @@ You can delete an existing virtual machine (VM) snapshot by using the web consol
 . Navigate to *Virtualization* -> *VirtualMachines* in the web console.
 . Select a VM to open the *VirtualMachine details* page.
 . Click the *Snapshots* tab to view a list of snapshots associated with the VM.
-. Click the options menu {kebab} beside a snapshot and select *Delete snapshot*.
+. Click the Options menu {kebab} beside a snapshot and select *Delete snapshot*.
 . Click *Delete*.

modules/virt-hot-plugging-disks-ui.adoc

@@ -27,9 +27,9 @@ You can make a hot plugged disk persistent so that it is permanently mounted on
 .. In the *Add disk (hot plugged)* window, select the disk from the *Source* list and click *Save*.
 
 . Optional: Unplug a hot plugged disk:
-.. Click the options menu {kebab} beside the disk and select *Detach*.
+.. Click the Options menu {kebab} beside the disk and select *Detach*.
 .. Click *Detach*.
 
 . Optional: Make a hot plugged disk persistent:
-.. Click the options menu {kebab} beside the disk and select *Make persistent*.
+.. Click the Options menu {kebab} beside the disk and select *Make persistent*.
 .. Reboot the VM to apply the change.

modules/virt-restoring-vm-from-snapshot-web.adoc

@@ -12,8 +12,8 @@ You can restore a virtual machine (VM) to a previous configuration represented b
 
 . Navigate to *Virtualization* -> *VirtualMachines* in the web console.
 . Select a VM to open the *VirtualMachine details* page.
-. If the VM is running, click the options menu {kebab} and select *Stop* to power it down.
+. If the VM is running, click the Options menu {kebab} and select *Stop* to power it down.
 . Click the *Snapshots* tab to view a list of snapshots associated with the VM.
 . Select a snapshot to open the *Snapshot Details* screen.
-. Click the options menu {kebab} and select *Restore VirtualMachine from snapshot*.
+. Click the Options menu {kebab} and select *Restore VirtualMachine from snapshot*.
 . Click *Restore*.