Proofread and crosslink examples with immunohistochemistry image.

[mkcor]

Description

These minor changes are part of the documentation effort, with a particular focus on the life sciences. Adding a link to another example helps users navigate the gallery.

Checklist

• Docstrings for all functions
• Gallery example in ./doc/examples (new features only)
• Benchmark in ./benchmarks, if your changes aren't covered by an
  existing benchmark
• Unit tests
• Clean style in the spirit of PEP8

For reviewers

• Check that the PR title is short, concise, and will make sense 1 year
  later.
• Check that new functions are imported in corresponding __init__.py.
• Check that new features, API changes, and deprecations are mentioned in
  doc/release/release_dev.rst.

[rfezzani]

Thank you @mkcor, I just left a small question and a minor request 😉

[rfezzani]

🎉 Thank you @mkcor 😉

[mkcor]

Can another @scikit-image/core dev please review/approve this PR? Once it's merged, I can post my bio-centric announcement on the forum in all peace of mind. Thank you!

[grlee77]

I left one small comment about possibly overriding cross-link text, but if that suggestion is not likely to work, feel free to merge as-is.

[grlee77]

I had to check the docs to see how this got rendered and notice "Separate" is capitalized, but I don't think it is a big issue if that is not easy to fix.

Does it work if you use the following form?:

:ref:`sphx_glr_auto_examples_color_exposure_plot_ihc_color_separation.py <separate colors in immunohistochemical staining>`.

That would also be robust to future changes to the title in the other file.

link to the rendered doc:
https://1426-2014929-gh.circle-artifacts.com/0/doc/build/html/auto_examples/segmentation/plot_mask_slic.html#sphx-glr-auto-examples-segmentation-plot-mask-slic-py

[mkcor]

Oh, yes. I expected this, for I used the same syntax before, in this example: https://scikit-image.org/docs/dev/auto_examples/applications/plot_3d_structure_tensor.html

I think it makes sense to display a proper title as opposed to a hyperlink within a sentence that should read smoothly... I admit I stayed between two stools in this case: I hesitated between "see tutorial: Title" and adapting the syntax to the example's title. Generally speaking, I'm in favour of using the imperative for example titles (just like commit messages), so there's a standard, plus it's engaging for the reader.

[grlee77]

Looks great, thanks @mkcor!