Standardize on hanging indent in documentation

[Tim Graham]

Most of the documentation using 4 space hanging indent, but there are a few places where it needs to be cleaned up. I attached a patch to give some examples and get you started.

Rules to follow:

• The closing parenthesis goes on its own line, aligned with the line that contains the opening parenthesis.
• Include a trailing comma after the last kwarg or item in the dict or tuple so more items can be added later without modifying that line again.

Any questions, let me know.

[Chris Cogdon]

In utils.txt, (new) line 670, there's no trailing comma. It kinda makes sense that there isn't one, since the function has exactly three arguments, but checking to see if that was intended.

[Tim Graham]

It's not critical either way, but I find it easiest to always add the comma so you don't have to think about it. You never know if a function might gain new arguments too.

[Tim Graham <timograham@…>]

In e475e849:

Refs #26021 -- Used hanging indentation in some doc examples.

[Tim Graham <timograham@…>]

In dbd72b8:

[1.9.x] Refs #26021 -- Used hanging indentation in some doc examples.

Backport of e475e849703d937e158e75e7a6d9cb99090857f6 from master

[Tim Graham]

I'm sure there are other places to revise, but I committed my patch for now since no one has picked this up in a while and those weird indentations bother me when I see them.

[Tim Graham <timograham@…>]

In 4a4d7f98:

Fixed #26021 -- Applied hanging indentation to docs.

[Tim Graham <timograham@…>]

In 6d0c9f9:

[1.9.x] Fixed #26021 -- Applied hanging indentation to docs.

Backport of 4a4d7f980e2a66756e1e424f7648dcd28ff765b7 from master

[Tim Graham <timograham@…>]

In 521772ff:

[1.10.x] Fixed #26021 -- Applied hanging indentation to docs.

Backport of 4a4d7f980e2a66756e1e424f7648dcd28ff765b7 from master