### Summary

In https://docs.ansible.com/ansible/latest/collections/ansible/builtin/yum_module.html , skip_broken description says:

Skip packages with broken dependencies(devsolve) and are causing problems.

a) Missing space before the opening parenthesis.
b) The sentence seems weird - not fully sure what it tries to convey. Perhaps "Skip packages with broken dependencies (devsolve) and packages that are causing problems." ?

### Issue Type

Documentation Report

### Component Name

yum

### Ansible Version

```console
latest
```


### Configuration

```console
Not relevant
```


### OS / Environment

Not relevant

### Additional Information

Readable docs

### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
action:
        details: In the case of yum, it has 2 action plugins that use it under the hood, M(yum) and M(package).
        support: partial
    async:
        support: none
    bypass_host_loop:
        support: none
    check_mode:
        support: full
    diff_mode:
        support: full
    platform:
        platforms: rhel
notes:
  - When used with a `loop:` each package will be processed individually,
    it is much more efficient to pass the list directly to the `name` option.
  - In versions prior to 1.9.2 this module installed and removed each package
    given to the yum module separately. This caused problems when packages
    specified by filename or url had to be installed or removed together. In
    1.9.2 this was fixed so that packages are installed in one yum
    transaction. However, if one of the packages adds a new yum repository
    that the other packages come from (such as epel-release) then that package
    needs to be installed in a separate task. This mimics yum's command line
    behaviour.
  - 'Yum itself has two types of groups.  "Package groups" are specified in the
    rpm itself while "environment groups" are specified in a separate file
    (usually by the distribution).  Unfortunately, this division becomes
    apparent to ansible users because ansible needs to operate on the group
    of packages in a single transaction and yum requires groups to be specified
    in different ways when used in that way.  Package groups are specified as