@EmilEnchev : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Can someone explain to me, when I make changes - to do or not to do pull requests?! I'm totally new here and I don't understand yet the Github's mechanic. If I only propose file changes is this enough?
Another thing that I don't understand is why when I make pull request it forked from MicrosoftDocs/cpp-docs to my Repositories? Should I then delete this fork after you've approve or disapprove the changes?
Best regards,
Emil Enchev

There are two ways to make a PR to the public repo: If you use the GitHub web interface to edit a file, it creates a fork of the repo for you if you don't have one already. The change is put in a branch with a name like "patch-2". Then this branch is used for the PR. Whether to delete the fork or not is up to you.
You can also work in your own fork of the repo. If you do, then you can include more than one file at a time in a PR. This is more advanced. If you have a complicated change, you should create an issue first for discussion, then make the PR.
The whole process is described in our Microsoft Docs contributor guide overview.

Thanks @corob-msft I will read Microsoft Docs contributor guide now.