Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1772381

Description of problem:
A tooltip provides an incorrect example on how to use multiple attributes as a matcher key.

Version-Release number of selected component (if applicable):
Satellite 6.4 and later
Foreman 1.10 and later

How reproducible:
Always

Steps to Reproduce:
1. In the Satellite web UI, navigate to Configure > Puppet Classes.
2. Select a class.
3. Click Smart Class Parameter.
4. Select some parameter and select the Override check box.
5. Click Add Matcher.
6. Click on the tooltip next to "Order".
7. Find the following text:
The order in which matchers keys are processed, first match wins.
You may use multiple attributes as a matcher key, for example, an order of host group, environment would expect a matcher such as hostgroup = "web servers", environment = production

Actual results:
The tooltip is misleading.
1. The example says “host group, environment”, but host group should be hostgroup (spaces don’t work) and the comma needs to be removed. The correct example would be “hostgroup,environment”.

when a space is added after the comma in the ‘Order’-box as the tooltip suggests it is not working.

Expected results:
Something like this. Please correct me if I am wrong:
The order in which matchers keys are processed, first match wins.
You may use multiple attributes as a matcher key, for example, an order of `host group,environment` would expect a matcher such as `hostgroup-"web servers",environment-production

Additional info:
You can find the working setup in the attachment.