chore(merge): pull request for patch/v3.0.1

[Falcion]

PRs: chore(merge): pull request for patch/v3.0.1

Before writing anything about your changes in this PR, checklist this items:

• Agreed with current version of code of conduct.
• Read and followed current version of “issue policy”.
• Read and followed current version of “commit convention”.

By agreeding and following this project's documentation, you are reminded that your's commit and styling of changes must follow this project's documentation, in case of “de-followization”, there are two ways before you make sure to publishing your PR:

1. In case of “de-followization” of commit's styling convention, you can amend them (change their message and description signatures):

git commit --amend -m "MESSAGE" -m "DESCRIPTION"

For amending old commit, see the stackoverflow question¹, more about changing commits in official docs for github:
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message/

2. In case of “de-followization” of coding, documentation and etc. files, you can just refactor everything you need by following styling guidelines of project.

Changes with that PR

Please, write below every changes you made:

READ THE CHANGELOG AND THE RULESETS (DATA/RELEASES).

Process of testing for that PR

• Was testing process initiated via this PR?
  answer (y/n): (y);
• If testing was done, type below the procedures you make:
  default testing (simulating user experience).

Additional context for that PR

...

Footnotes

1. https://stackoverflow.com/questions/17338792/amending-old-commit/ ↩