From d907ceb50fd1817ca0a717616495e71db446101b Mon Sep 17 00:00:00 2001
From: Makhnev Petr <51853996+i582@users.noreply.github.com>
Date: Mon, 13 Feb 2023 14:49:13 +0400
Subject: [PATCH] docs: format with IDEA formatter other .md files (#17293)

---
 CONTRIBUTING.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e142adfdd4..2a44bfa17a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -87,15 +87,16 @@ accordingly in the steps below.)
 3. `cd nv`
 4. `git remote add pullrequest https://github.com/YOUR_GITHUB_USERNAME/v`
 
-Note: The remote named `pullrequest` should point to YOUR own forked repo, not the
-main v repository! After this, your local cloned repository is prepared for
-making pullrequests, and you can just do normal git operations such as:
-`git pull` `git status` and so on.
+   Note: The remote named `pullrequest` should point to YOUR own forked repo, not the
+   main v repository! After this, your local cloned repository is prepared for
+   making pullrequests, and you can just do normal git operations such as:
+   `git pull` `git status` and so on.
 
 5. When finished with a feature/bugfix/change, you can:
 `git checkout -b fix_alabala`
    - Don't forget to keep formatting standards, run `v fmt -w YOUR_MODIFIED_FILES` before committing
 6. `git push pullrequest` Note: The `pullrequest` remote was setup on step 4
+
 7. On GitHub's web interface, go to: https://github.com/vlang/v/pulls
 
    Here the UI shows a dialog with a button to make a new pull request based on