minor tweaks

docs/snippets/common/storybook-test-runner-error.js.mdx

@@ -1,3 +0,0 @@
-```shell
-Timeout - Async callback was not invoked within the 15000 ms timeout specified by jest.setTimeout
-```

docs/writing-tests/accessibility-testing.md

@@ -208,7 +208,7 @@ It starts checking for issues by traversing the DOM tree starting from the story
 
 #### What’s the difference between browser-based and linter-based accessibility tests?
 
-Browser-based accessibility tests, like found in Storybook, evaluate the rendered DOM because that gives you the highest accuracy. Auditing code that hasn't been compiled yet is one step removed from the real thing, so you won't catch everything the user might experience.
+Browser-based accessibility tests, like those found in Storybook, evaluate the rendered DOM because that gives you the highest accuracy. Auditing code that hasn't been compiled yet is one step removed from the real thing, so you won't catch everything the user might experience.
 
 #### Learn about other UI tests
 

docs/writing-tests/importing-stories-in-tests.md

@@ -69,7 +69,7 @@ Update your test script to include the configuration file:
 
 ## Example with Testing Library
 
-[Testing Library](https://testing-library.com/) is a suite of helper libraries for browser-based interaction tests. With [Component Story Format](../api/csf.md), your stories are reusable with Testing Library. Each named export (in other words, a story) is renderable within your testing setup.
+[Testing Library](https://testing-library.com/) is a suite of helper libraries for browser-based interaction tests. With [Component Story Format](../api/csf.md), your stories are reusable with Testing Library. Each named export (story) is renderable within your testing setup.
 
 <div class="aside">
 

docs/writing-tests/introduction.md

@@ -12,7 +12,7 @@ The simplest testing method is manual “spot checking”. You run Storybook loc
 
 To test a component in isolation, you often have to mock data, dependencies, or even network requests. Check out our guide on [mocking in Storybook](../writing-stories/build-pages-with-storybook.md#mocking-connected-components) for more info.
 
-Storybook also comes with tools, [test runners](./test-runner.md), and [handy integrations](./importing-stories-in-tests.md) with the larger JavaScript ecosystem to expand your UI test coverage. These docs detail how you can use Storybook for UI testing.
+Storybook also comes with tools, [a test runner](./test-runner.md), and [handy integrations](./importing-stories-in-tests.md) with the larger JavaScript ecosystem to expand your UI test coverage. These docs detail how you can use Storybook for UI testing.
 
 - [**Test runner**](./test-runner.md) to automatically test your entire Storybook and catch broken stories.
 - [**Visual tests**](./visual-testing.md) capture a screenshot of every story then compare it against baselines to detect appearance and integration issues

docs/writing-tests/test-runner.md

@@ -273,15 +273,9 @@ Stories.json mode requires a `stories.json` file. Open a browser window and navi
 
 If your tests time out with the following message:
 
-<!-- prettier-ignore-start -->
-
-<CodeSnippets
-  paths={[
-    'common/storybook-test-runner-error.js.mdx',
-  ]}
-/>
-
-<!-- prettier-ignore-end -->
+```shell
+Timeout - Async callback was not invoked within the 15000 ms timeout specified by jest.setTimeout
+```
 
 It might be that Playwright couldn't handle testing the number of stories you have in your project. Perhaps you have a large number of stories, or your CI environment has a really low RAM configuration. In such cases, you should limit the number of workers that run in parallel by adjusting your command as follows: