From 12bae06313ebd43e4f3241a0a7a5d46025cb59a8 Mon Sep 17 00:00:00 2001 From: mattc41190 Date: Tue, 7 Apr 2020 02:27:54 -0500 Subject: [PATCH] Minor grammar fix (#2881) --- content/docs/testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/testing.md b/content/docs/testing.md index 5bccd1fc..b8e242d9 100644 --- a/content/docs/testing.md +++ b/content/docs/testing.md @@ -14,7 +14,7 @@ There are a few ways to test React components. Broadly, they divide into two cat * **Rendering component trees** in a simplified test environment and asserting on their output. * **Running a complete app** in a realistic browser environment (also known as “end-to-end” tests). -This documentation section focuses on testing strategies for the first case. While full end-to-end tests can be very useful to prevent regressions to important workflows, such tests are not concerned with React components in particular, and are out of scope of this section. +This documentation section focuses on testing strategies for the first case. While full end-to-end tests can be very useful to prevent regressions to important workflows, such tests are not concerned with React components in particular, and are out of the scope of this section. ### Tradeoffs {#tradeoffs}