diff --git a/guide/english/agile/acceptance-criteria/index.md b/guide/english/agile/acceptance-criteria/index.md
index 88ffcbb4bd..b1ec6f8dbd 100644
--- a/guide/english/agile/acceptance-criteria/index.md
+++ b/guide/english/agile/acceptance-criteria/index.md
@@ -8,7 +8,7 @@ the Product Owner and the Delivery Team reach an understanding on the desired ou
 
 The Acceptance Criteria tells the Delivery Team how the code should behave. Avoid writing the **"How"** of the User Story; keep to the **"What"**.
 If the team is following Test Driven Development (TDD), it may provide the framework for the automated tests.
-The Acceptance Criteria will be the beginnings of the test plan for the QA team.
+The Acceptance Criteria will be the beginnings of the test plan for the QA team. The Acceptance Criteria is what is required for the story to go live, the QA team may still apply exploratory testing to pick up potential defects.
 
 Most importantly, if the story does not meet each of the Acceptance Criteria, then the Product Owner should not be accepting the story at the end of the iteration.