From 86307559c17e897d9652c2a2e86ae2ac5b9b34e2 Mon Sep 17 00:00:00 2001 From: jonniebigodes Date: Sat, 20 Nov 2021 15:43:15 +0000 Subject: [PATCH] minor grammar fix --- docs/writing-tests/importing-stories-in-tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/writing-tests/importing-stories-in-tests.md b/docs/writing-tests/importing-stories-in-tests.md index 985cb07e19f..99da8acd420 100644 --- a/docs/writing-tests/importing-stories-in-tests.md +++ b/docs/writing-tests/importing-stories-in-tests.md @@ -6,7 +6,7 @@ Teams test a variety of UI characteristics using different tools. Each tool requ Storybook enables you to isolate a component and capture all of its use cases in a `*.stories.js` file. Stories are standard JavaScript modules so they’re cross compatible with the whole JavaScript ecosystem. No API lock-in. -Stories as a practical starting point for UI testing. Import stories into tools like [Jest](https://jestjs.io/), [Testing Library](https://testing-library.com/), [Puppeteer](https://pptr.dev/), [Cypress](https://www.cypress.io/), and [Playwright](https://playwright.dev/) to save time and maintenance work. +Stories are a practical starting point for UI testing. Import stories into tools like [Jest](https://jestjs.io/), [Testing Library](https://testing-library.com/), [Puppeteer](https://pptr.dev/), [Cypress](https://www.cypress.io/), and [Playwright](https://playwright.dev/) to save time and maintenance work. ## Setup the testing addon for your framework