docs: improve stats/base/dists/lognormal README Examples

[meddhiaka]

Resolves # .

Description

What is the purpose of this pull request?
I updated improved the documentation of the README examples of stats/base/dists/lognormal namespace, with providing examples of using the functions inside that directory, also the expected return of every possible function

This pull request:

• a
• b
• c

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves #
• fixes [RFC]: improve README examples of stats/base/dists/lognormal namespace #1636

Questions

Any questions for reviewers of this pull request?

I'm waiting for reviewers comment ASAP, I'm interested in contributing to this repository so bad, so any advices or comments would be appreciated!

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as this pull request does not follow project conventions.

We place a high value on consistency throughout the stdlib codebase, and this pull request was found to significantly deviate from stdlib conventions. We encourage you to closely examine other packages in stdlib and attempt to emulate the practices and conventions found therein.

• If you are attempting to contribute a new package, sometimes the best approach is to simply copy the contents of an existing package and then modify the minimum amount necessary to implement the feature (e.g., changing descriptions, parameter names, and implementation).
• If you are contributing tests, find a package implementing a similar feature and emulate the tests of that package.
• If you are updating documentation, examine several similar packages and emulate the content, style, and prose of those packages.

In short, the more effort you put in to ensure that your contribution looks and feels like stdlib—including variables names, bracket spacing, line breaks, etc—the more likely that your contribution will be reviewed and ultimately accepted. We encourage you to closely study the codebase before continuing to work on this pull request.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.