diff --git a/Test262-Technical-Rationale-Report,-October-2017.md b/Test262-Technical-Rationale-Report,-October-2017.md
index 17eba25..22e726d 100644
--- a/Test262-Technical-Rationale-Report,-October-2017.md
+++ b/Test262-Technical-Rationale-Report,-October-2017.md
@@ -71,7 +71,7 @@ The efforts put into Test262 over the last 3 years has allowed the project to pr
 
 ## Conclusion
 
-Test262’s task of providing a detailed specification conformance test suite is supported by efforts to improve and evolve on two equally important fronts: maintenance and consumption. Both of these aspects require thoughtful and well considered efforts to successfully serve their broader purpose: to allow for the testing and verification of all JavaScript engine, parser, and runtime implementations—which includes, but is not limited to, those used in browsers, servers, end embedded environments. 
+Test262’s task of providing a detailed specification conformance test suite is supported by efforts to improve and evolve on two equally important fronts: maintenance and consumption. Both of these aspects require thoughtful and well considered efforts to successfully serve their broader purpose: to allow for the testing and verification of all JavaScript engine, parser, and runtime implementations—which includes, but is not limited to, those used in browsers, servers, and embedded environments. 
 
 Although structural conventions and maintenance policies may look complex, the result is  consistent testing material which may be used across myriad JavaScript implementation targets. The minor additional efforts required of contributions does not exceed that which is considered reasonable for most large open source projects.