More docs refinement and polish

docs/writing-tests/accessibility-testing.md

@@ -1,5 +1,5 @@
 ---
-title: 'Accessibility testing with Storybook'
+title: 'Accessibility tests'
 ---
 
 Accessibility is the practice of making websites inclusive to all. That means supporting requirements such as: keyboard navigation, screen reader support, touch-friendly, usable color contrast, reduced motion, and zoom support.
@@ -10,7 +10,7 @@ Storybook’s official [a11y addon](https://storybook.js.org/addons/@storybook/a
 
 ![Accessibility testing](./accessibility-testing-storybook.gif)
 
-### Setup a11y addon
+## Setup a11y addon
 
 To enable accessibility testing with Storybook, you'll need to install the [`@storybook/addon-a11y`](https://storybook.js.org/addons/@storybook/addon-a11y/) addon. Run the following command:
 

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

@@ -17,7 +17,7 @@ Storybook has test addons for core frameworks React, Vue (2,3), and Angular. Thi
 - [@storybook/testing-vue3](https://storybook.js.org/addons/@storybook/testing-vue3)
 - [@storybook/testing-angular](https://storybook.js.org/addons/@storybook/testing-angular)
 
-## Install the addon
+### Install the addon
 
 Run the following command to add Storybook's testing addon into your environment:
 

docs/writing-tests/interaction-testing.md

@@ -1,5 +1,5 @@
 ---
-title: 'Interaction testing with Storybook'
+title: 'Interaction tests'
 ---
 
 As you build more complex UIs like pages, components become responsible for more than just rendering the UI. They fetch data and manage state. Interaction tests allow you to verify these functional aspects of UI.
@@ -73,7 +73,7 @@ The example below showcases how a form component behaves when information is add
 
 When Storybook finishes rendering the story, it interacts with the component, fills in the form, simulates a button click, and verifies if the values returned match the provided ones.
 
-## Debugging
+### Debugging
 
 The [`@storybook/addon-interactions`](https://storybook.js.org/addons/@storybook/addon-interactions/) addon includes a set of UI controls to allow you control over the test execution flow. At any time, you can pause, resume, rewind, and step through each interaction. Also, providing you with an easy-to-use debugger for errors.
 
@@ -83,7 +83,7 @@ Open your `Interactions` panel and click on an individual step to jump to the ex
 
 ![Storybook addon interactions click steps](./addon-interactions-individual-states.gif)
 
-## Permalinks for reproductions
+### Permalinks for reproductions
 
 The `play` function is executed after the story is rendered. If there’s an error, it’ll be shown in the interaction addon panel to help with debugging.
 

docs/writing-tests/snapshot-testing.md

@@ -1,5 +1,5 @@
 ---
-title: 'Snapshot testing with Storybook'
+title: 'Snapshot tests'
 ---
 
 Snapshot tests compare the rendered markup of every story against known baselines. It’s a way to identify markup changes that trigger rendering errors and warnings.
@@ -8,7 +8,7 @@ Storybook is a helpful tool for snapshot testing because every story is essentia
 
 ![Example Snapshot test](./snapshot-test.png)
 
-## Setup
+## Setup Storyshots
 
 [Storyshots](https://storybook.js.org/addons/@storybook/addon-storyshots/) is the official Storybook addon that enables snapshot testing, powered by [Jest](https://jestjs.io/docs/getting-started).
 
@@ -98,7 +98,7 @@ By default, Storyshots detects your project's framework. If you run into a situa
 
 These are the frameworks currently supported by Storyshots: `angular`, `html`, `preact`, `rax`, `react`, `react-native`, `riot`, `svelte`, `vue`, `vue3`, and `web-components`.
 
-## Additional customization
+### Additional customization
 
 Storyshots is highly customizable and includes options for various advanced use cases. You can read more in the [addon’s documentation](https://github.com/storybookjs/storybook/tree/master/addons/storyshots/storyshots-core#options).
 

docs/writing-tests/visual-testing.md

@@ -1,5 +1,5 @@
 ---
-title: 'Visual testing with Storybook'
+title: 'Visual tests'
 ---
 
 Visual tests, also called visual regression tests, catch bugs in UI appearance. They work by taking screenshots of every story and comparing them commit-to-commit to identify changes.