Fix relative document link in the HOWTO
Restructure the document list in the main readme file into developer and user documentation lists.
@@ -132,11 +132,11 @@ With this feature CodeChecker can recognize the same and new bugs in two differe
**In summary:**
* Store daily runs of a module every day in a new run post-fixed with date. You can query *new* and *resolved* bugs
- using the [`cmd diff`](docs/user_guide.md#show-differences-between-two-runs-diff) or the WEB GUI.
+ using the [`cmd diff`](user_guide.md#show-differences-between-two-runs-diff) or the WEB GUI.
* Create a single run for each module in each branch and keep it up to date with code changes (commits). The CI
loop then can compare pull requests (commit attempts) against this run and list *new* bugs in the changed code.
Programmers can also compare their local edits to this run to see if they would introduce any new issues.
-* Programmers should use [in-code-suppression](docs/user_guide.md#suppression-in-the-source-code)
+* Programmers should use [in-code-suppression](user_guide.md#suppression-in-the-source-code)
to tell the CI guard that a report is false positive and should be ignored. This way your suppressions remain
also resistant to eventual changes of the bug hash (generated by clang).
@@ -223,7 +223,7 @@ he can suppress the false positive by amending the following suppression commend
// codechecker_suppress [core.NullDereference] suppress all checker results
x = 1; // warn
```
-See [User guide](docs/user_guide.md#suppression-in-the-source-code) for more information.
+See [User guide](user_guide.md#suppression-in-the-source-code) for more information.
### Programmer checking new bugs in the code after local edit (and compare it to a central database)
