Documentation updated

[nivida]

Description

The module constructors where not consistently described.

Fixes #2534 #2514 #2494 #2490 #2383

Type of change

• Documentation

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no warnings.
• I have updated or added types for all modules I've changed
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run test in the root folder with success and extended the tests if necessary.
• I ran npm run build in the root folder and tested it in the browser and with node.
• I ran npm run dtslint in the root folder and tested that all my types are correct
• I have tested my code on an ethereum test network.

[coveralls]

Coverage remained the same at 95.374% when pulling b13cc55 on docs/improvements into c9486cb on 1.0.

[coveralls]

Coverage increased (+0.002%) to 95.376% when pulling 4a3a685 on docs/improvements into 340d621 on 1.0.

[coveralls]

Coverage remained the same at 95.374% when pulling b13cc55 on docs/improvements into c9486cb on 1.0.

[OFRBG]

Good changes! Keep in mind that users reading the docs don't know how the library behaves for "else" cases. If you specify a condition such as "if the address isn't available locally, X happens", the opposite needs to be implicitly clear or specified. Example logic: "[for all cases, Y happens], [only] if the address isn't available locally, X happens."