[SYCL] Fix contribution guide instructions

CONTRIBUTING.md

@@ -24,24 +24,25 @@ for more information.
   - For the DPC++ Compiler project, use **sycl** branch as baseline for your
     changes. See [Get Started Guide](sycl/doc/GetStartedGuide.md).
 - Prepare your patch
-    - follow [LLVM coding standards](https://llvm.org/docs/CodingStandards.html)
-    - [clang-format](https://clang.llvm.org/docs/ClangFormat.html) and
-      [clang-tidy](https://clang.llvm.org/extra/clang-tidy/) tools can be
-      integrated into your workflow to ensure formatting and stylistic
-      compliance of your changes.
-    - use
-      ```
-      ./clang/tools/clang-format/git-clang-format `git merge-base origin/sycl HEAD`
-      ```
-      to check the format of your current changes against the `origin/sycl`
-      branch.
-        - `-f` to also correct unstaged changes
-        - `--diff` to only print the diff without applying
-- Build the project and run all tests.
-    - complete test suite: `python buildbot/check.py`
-    - sycl test suite `python buildbot/check.py -t test-sycl`
-    - run only "mytest" test `python buildbot/check.py -t test-sycl-mytest`
-    - if necessary, use `-o $LLVM_BUILD_DIR` to specify the llvm build directory
+  - follow [LLVM coding standards](https://llvm.org/docs/CodingStandards.html)
+  - [clang-format](https://clang.llvm.org/docs/ClangFormat.html) and
+    [clang-tidy](https://clang.llvm.org/extra/clang-tidy/) tools can be
+    integrated into your workflow to ensure formatting and stylistic
+    compliance of your changes.
+  - use
+
+    ```bash
+    ./clang/tools/clang-format/git-clang-format `git merge-base origin/sycl HEAD`
+    ```
+
+    to check the format of your current changes against the `origin/sycl`
+    branch.
+    - `-f` to also correct unstaged changes
+    - `--diff` to only print the diff without applying
+- Build the project following
+[Get Started Guide instructions](sycl/doc/GetStartedGuide.md#build-dpc-toolchain).
+- Run regression tests -
+[instructions](sycl/doc/GetStartedGuide.md#test-dpc-toolchain).
 
 ### Commit message
 
@@ -67,6 +68,7 @@ ready for merge.
 ### Merge
 
 Project maintainers merge pull requests using one of the following options:
+
 - [Rebase and merge] The preferable choice for PRs containing a single commit
 - [Squash and merge] Used when there are multiple commits in the PR
   - Squashing is done to make sure that the project is buildable on any commit