[mmporong]

Three docstrings in compas.geometry document parameters that the functions do not have:

• Shear.from_entries(shear_entries) documented the argument as shear_factors.
• Polyline.split_by_length(length, strict=True) documented a tol argument. The method has no tol; the entry looks copied from divide_by_length, which does take one.
• trimesh_gradient_numpy(M, rtype="array") documented separate V and F arguments, but it takes a single M and unpacks it as V, F = M (as trimesh_descent_numpy calls it, trimesh_gradient_numpy((V, F))). The entry now follows the wording of the other trimesh_* functions that take M.

I found these by comparing the documented parameter names with the function signatures. After the change, the comparison reports no mismatch for these three functions. The doctests in shear.py and the split_by_length examples still pass, and trimesh_gradient_numpy((V, F)) runs on a one-triangle mesh. Docstrings and changelog only.

What type of change is this?

• Bug fix in a backwards-compatible manner.
• New feature in a backwards-compatible manner.
• Breaking change: bug fix or new feature that involve incompatible API changes.
• Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• I ran all tests on my computer and it's all green (i.e. invoke test).
• I ran lint on my computer and there are no errors (i.e. invoke lint).
• I added new functions/classes and made them available on a second-level import, e.g. compas.datastructures.Mesh.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate)

[gonzalocasas]

Thanks!!