From 79e2a261788f863993c012055524acbf66b7829c Mon Sep 17 00:00:00 2001 From: Markus Lanser Date: Mon, 17 Dec 2018 20:28:31 +0000 Subject: [PATCH] fixing spelling mistake (#25923) --- guide/english/agile/acceptance-testing/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/agile/acceptance-testing/index.md b/guide/english/agile/acceptance-testing/index.md index 0a1b8f8f9d..cdb9ef95db 100644 --- a/guide/english/agile/acceptance-testing/index.md +++ b/guide/english/agile/acceptance-testing/index.md @@ -6,7 +6,7 @@ title: Acceptance Testing Acceptance testing, is a testing technique performed to determine whether the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it has met the required criteria for delivery to end users. -In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience.In engineering and its various subdisciplines acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. +In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience. In engineering and its various subdisciplines acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. There are various forms of acceptance testing: