diff --git a/src/pages/agile/acceptance-testing/index.md b/src/pages/agile/acceptance-testing/index.md
index de0e558d4c8..27785380ebd 100644
--- a/src/pages/agile/acceptance-testing/index.md
+++ b/src/pages/agile/acceptance-testing/index.md
@@ -15,6 +15,7 @@ There are various forms of acceptance testing:
 ->Alpha Testing
 
 ->Beta Testing
+->Theta testing
 
 #Acceptance Criteria
 Acceptance criteria are defined on the basis of the following attributes
@@ -125,6 +126,6 @@ A good way of defining which acceptance tests should be written is to add accept
 In an Agile project it is important for the team to have acceptance criteria defined for all user stories. The Acceptance Testing work will use the defined criteria for evaluating the delivered functionality. When a story can pass all acceptance criteria it is complete. 
 
 Acceptance testing can also validate if a completed epic/story/task fulfills the defined acceptance criteria. In contrast to definition of done, this criteria can cover specific business cases that the team wants to solve. This provides a good measurement of work quality.
-
+# my changes
 #### More Information:
 - [International Software Testing Qualifications Board](http://www.istqb.org/)