Catchall PR for minor formatting/typo updates to docstrings

[mgjarrett]

What is the change?

Typographical and formatting updates to docstrings and implementation detail that is going into the SQA docs for ARMI.

Why is the change being made?

Edits are being made as part of a review of the SQA documentation for ARMI.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
• The documentation is still up-to-date in the doc folder.
• If any requirements were affected, mention it in the release notes.
• The dependencies are still up-to-date in pyproject.toml.

[john-science]

You know we have a ticket open for this, right?

#1624

[john-science]

@albeanth @mgjarrett This is certainly one of the main options in the ticket I linked. But I thought maybe we would discuss it first. I certainly think it doesn't belong in the API. But it could be somewhere else in the docs.

Thoughts?

[albeanth]

I think this is a fine band-aid solution but shouldn't be the long term solution.

Having a 109-page long table in the HTML is also not very useful. I think we should either 1) get rid of it, or 2) have a small table with ~10 nuclides as an example and reference the rest in a script that can be run.

[mgjarrett]

@opotowsky @john-science I don't see any other fixes coming in. Should we merge this now?