Description of problem:

The tooltip in Administration -> Configure -> Scheduling Policies -> Weights Modules seems a bit out of date. It appears to describe the WeightSelector Policy Unit instead of the newer (and default) Rank Selector policy unit.

clusterPolicyWeightFunctionInfo=Weights represent soft constraints for running a VM. Note\: in a weighting system, lower score is considered better. So a host with the lowest score (weight) is the one the scheduler will choose. Each weight module scores any given host based on an optimization logic the module implements. For example, if we want to optimize for CPU load, the module will score each host based on its known CPU load. Weight modules scores are being summed, so it is possible to have more than one weight module. The way to prioritize modules is by increasing / decreasing a factor.

Can this be improved to explain that the scores are ranked, and then the host with lowest accumulated rank wins? I think it would be more in line to what actually happens.

Version-Release number of selected component (if applicable):
Same text even on master branch

How reproducible:
Always

Steps to Reproduce:
1. Go to  Administration -> Configure -> Scheduling Policies -> Weights Modules and see tooltip