Document how to run the wrap valídator. [skip ci]
diff --git a/docs/markdown/Adding-new-projects-to-wrapdb.md b/docs/markdown/Adding-new-projects-to-wrapdb.md
index 661ad6c..1ce9f3e 100644
--- a/docs/markdown/Adding-new-projects-to-wrapdb.md
+++ b/docs/markdown/Adding-new-projects-to-wrapdb.md
@@ -252,10 +252,17 @@
may also host your own Git repo with the changes if you wish. The Wrap
system has native support for Git subprojects.
-## Reviewing wraps
+## Passing automatic validation
-See [Wrap review guidelines](Wrap-review-guidelines.md), especially
-the part about tooling that you can use to check for the most common
-problems yourself. Fixing all issues reported by the tool is a
-mandatory requirement for getting your MR accepted, so doing this
-proactively makes the review process smoother.
+Every submitted wrap goes through an automated correctness review and
+passing it is a requirement for merging. Therefore it is highly
+recommended that you run the validation checks yourself so you can fix
+any issues faster.
+
+Instructions on how to install and run the review tool can be found on
+the [Wrap review guidelines page](Wrap-review-guidelines.md).
+proactively makes the review process smoother. If your submission is
+merge request number 5 for a repository called `mylib`, then you'd run
+the following command:
+
+ mesonwrap review --pull-request 5 mylib
