From my regular expression foo, those are the only 9 case whereas there
are about ~2000 usage that do not have spaces.

While this is ok with docutils/sphinx, it does not seem to be
documented, and that means that other parsers will see that as comments,
leading to for example improper syntax highlighting.

This make it also a tiny bit harder to develop alternative rst parsers.

The math expression needs to be indented, Otherwise it is seen as being
outside the directive and not rendered.

ENH: Vectorizing umath module using AVX-512 (open sourced from Intel Short Vector Math Library, SVML)

Ok, I know legmul is important, I'm not sure I need it twice.

Joking aside, I belive that's a wrong copy-past, as other functions have
`legmulx, legmul`, but as this is the docs of legmulx, I guess the
author removed the `x` without realising legmul was already present.

DOC: fix docstring formatting of polynomial fit method return values.

Fixes #19897

The 2nd return value of the following methods/functions were badly
formatted and the list was all appearing in a single line. Changed them
to separate points which are rendered nicely.
 - numpy.polyfit
 - numpy.ma.polyfit
 - numpy.polynomial.polynomial.polyfit
 - numpy.polynomial.polynomial.Polynomial.fit
 - numpy.polynomial.chebyshev.chebfit
 - numpy.polynomial.chebyshev.Chebyshev.fit
 - numpy.polynomial.hermite.hermfit
 - numpy.polynomial.hermite.Hermite.fit
 - numpy.polynomial.hermite_e.hermefit
 - numpy.polynomial.hermite_e.HermiteE.fit
 - numpy.polynomial.laguerre.lagfit
 - numpy.polynomial.laguerre.Laguerre.fit
 - numpy.polynomial.legendre.legfit
 - numpy.polynomial.legendre.Legendre.fit

Also fixed erroneous links to `numpy.full` which were actually referring
to the `full` argument. Changed those to code strings (double backticks)
from single backticks.

Also fixed formatting issues in the 3rd return value of numpy.polyfit
(and hence also numpy.ma.polyfit).

SVML library is accurate upto 4ULP and hence reduces the accuracy
slightly