Skip to content

Conversation

@abuts
Copy link
Collaborator

@abuts abuts commented Sep 4, 2025

  • Please check if the PR fulfills these requirements
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce(Bug fix, feature, docs update, ...)?

Fixes Re #50

This PR introduces changes to documentation which I have noticed as a newbing.

The changes charify things that were unclear or need additional imagination. They may be trivial, but cause problem for the beginner and I believe, will be useful for another beginner. I am also hope, that more experienced users will easy accept them.

  • Does this PR introduce a breaking change (What changes might users need to make in their application due to this PR)?
    No

  • Other information:

As I am reading this documentation for sufficiently long time I am getting used to it, so probably should close this ticket.

Part of these changes have been inherited from the results of PR #51. They should be disappearing from here, but as I did PR squash (never did it before), they are still displayed here, so the changes to README.md are from the PR, which is already in main and should be disregaded (unless you want to add something there too.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants