diff --git a/Writing-high-quality-testing-instructions.md b/Writing-high-quality-testing-instructions.md
index 1fe239f..2856db5 100644
--- a/Writing-high-quality-testing-instructions.md
+++ b/Writing-high-quality-testing-instructions.md
@@ -20,6 +20,12 @@ Specifying what are the preconditions, action and validation can be quite benefi
 
 In this context, we will refer to testing instructions as the tests we need to execute in order to validate that the changes delivered in a Pull Request or Release work as expected. This means the testing instructions could refer to a test or more, involving the happy path and potential edge cases.
 
+## What to cover with the testing instructions
+As stated in the previous section, a test (in our context, a testing instruction) is a method to check that a new change or set of changes meets certain criteria.
+
+Therefore, a PR could have testing instructions for multiple scenarios, in fact, it is recommended to include testing instructions for as many scenarios as needed to cover the changes introduced in the PR. In other words, please **add as many testing instructions as needed to cover the acceptance criteria**, understanding acceptance criteria as _the conditions that a software product must satisfy to be accepted by a user, customer or other stakeholders_ or, in the context of a PR, the conditions that this PR must satisfy to be accepted by users, developers and the WooCommerce community as per requirements.
+
+
 ## Flow to write good testing instructions
 1. **Outline the user flows** you want to cover.
 2. **Define the environment** where the testing instructions should be executed (server, PHP version, WP version, required plugins, etc), and start writing the testing instructions as if you were starting from a fresh install.