diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b22955bfd..55dc55ba3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -35,7 +35,7 @@ Fork the repository and open a pull request to submit your work. Please consider
 
 As general guideline for pull requests, please:
 
-* Don't mix fixes and cleanups in same pull request. They just increase the likelhood of merge conflicts. Cleanups are welcome, but just keep them separate.
+* Don't mix fixes and cleanups in same pull request. They just increase the likelihood of merge conflicts. Cleanups are welcome, but just keep them separate.
 * Prefer `git rebase main` over `git merge main` on your branches to keep git logs clean.
 
 ## Debugging query execution
@@ -69,6 +69,18 @@ If the bytecode is the same, but query results are different, then the bug is so
 The `testing/test.all` is a starting point for adding functional tests using a similar syntax to SQLite.
 The purpose of these tests is to verify behavior matches with SQLite and Limbo.
 
+### Prerequisites
+
+1. [Cargo-c](https://github.com/lu-zero/cargo-c) is needed for building C-ABI compatible library. You can get it via:
+```console
+cargo install cargo-c
+```
+2. [SQLite](https://www.sqlite.org/index.html) is needed for compatibility checking. You can install it using `brew`:
+```console
+brew install sqlite
+```
+
+### Running the tests
 To run the test suite with Limbo, simply run:
 
 ```
diff --git a/README.md b/README.md
index 83fba08c1..91d7cdad1 100644
--- a/README.md
+++ b/README.md
@@ -115,6 +115,15 @@ Test coverage report:
 cargo tarpaulin -o html
 ```
 
+> [!NOTE]
+> Generation of coverage report requires [tarpaulin](https://github.com/xd009642/tarpaulin) binary to be installed.
+> You can install it with `cargo install cargo-tarpaulin`
+
+[//]: # (TODO remove the below tip when the bug is solved)
+
+> [!TIP]
+> If coverage fails with "Test failed during run" error and all of the tests passed it might be the result of tarpaulin [bug](https://github.com/xd009642/tarpaulin/issues/1642). You can temporarily set [dynamic libraries linking manually](https://doc.rust-lang.org/cargo/reference/environment-variables.html#dynamic-library-paths) as a workaround, e.g. for linux  `LD_LIBRARY_PATH="$(rustc --print=target-libdir)" cargo tarpaulin -o html`.
+
 Run benchmarks:
 
 ```console