Doc: errors tutorial improvements

[adorilson]

Improvements:

• Improvements in how try clause works section
  This suggestion is because the execution continues after except, not after try but before except. I guess this form more clear.

• Surrounding some keywords with *...*
  For uniformity the highlighted terms

• Adjust the number of chars per line to 80

Automerge-Triggered-By: GH:aeros

[aeros]

Thanks for the PR @adorilson.

Regarding the usage of asterisks, they are typically reserved for argument names, so I do not support the idea of using try clause or except clause. If anything, the emphasis should only surround "try" or "except". Additionally, it should be using either the Spinx keyword role or inline code blocks. The Sphinx roles provide a specific functional purpose of linking to the documentation, so they are more beneficial when appropriately used.

Sphinx role example:

:keyword:`try` clause

Code block example:

``try`` clause

Also, while we typically require that any PRs changing or adding documentation fit within the 80 character line width limit for reST, it is discouraged to change an existing section solely for the purpose of fixing the wrapping, as this can add unnecessary clutter to the commit logs.

[adorilson]

Hi, folks.

What exactly I need to do here?

[aeros]

Sorry for the delay, LGTM. (For clarification, I did not have commit privileges when I last left a review)