English
Now you can make whatever changes it is that you want. Fire up your favorite text editor and edit away. When you're done, it's time to commit the changes.
`git add ''file(s) that you edited''`
`git commit`
Edit the commit message and quit the editor. If your system uses vim as the default editor (which it probably does, unless you changed it), type `i` to enter editing mode. When you're done writing your commit message, hit the Escape key, type `:wq`, and hit enter.
Good commit messages are helpful when someone (including future you) looks at the commit history to see what was done. A good commit message says what the commit does and why.
Try to keep your commits related to a single logical change. This makes it easier to undo it if needed. A "single logical change" may require editing multiple files, which should all be in one commit, but if you're adding unrelated content, do it separately.
Finally, it's time to push your changes from your local machine to the remote server and create the pull request.
`git push origin ''branch_name''`
In your web browser, go to your forked repo (for example \https://pagure.io/fork/bcotton/fedora-docs/quick-docs)
Follow the git forge's instructions for creating a pull request (docs for https://docs.pagure.org/pagure/usage/pull_requests.html[Pagure] and https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork[GitHub])