Trim trailing whitespace in .md files

Author: skirtles-code

.editorconfig

@@ -10,4 +10,4 @@ trim_trailing_whitespace = true
 
 [*.md]
 indent_size = 4
-trim_trailing_whitespace = false
+

packages/docs/src/dist-files.md

@@ -62,7 +62,7 @@ For libraries, there are two build processes to consider: building the library i
 
 Rather than a clear split between development and production, we instead have three stages: developing the library, developing the consuming application, and finally production. The first stage, developing the library itself, doesn't impact what we publish to npm, so we can ignore that here.
 
-The production stage is also relatively straightforward. 
+The production stage is also relatively straightforward.
 
 The stage that poses the most challenges is developing the consuming application. We need to build our library in such a way that it'll work well during that stage.
 
@@ -134,7 +134,7 @@ This build is suitable for use in the Vue Playground:
 
 - [Vue Playground example](https://play.vuejs.org/#eNqlU01v2zAM/SuEL9lHbHfYTplXdBsCbAXWDduOvmg24yiRJUGiUxdB/vsofy0LmrZADwIkvqfHR0rcRx+tTXYNRoso84WTlsAjNRaU0NWHPCKfR5e5lrU1jmAPy1bUVuFnwwGNmubw7e6H0KjgACtnaphd+a10pDDFnhqzeqzkn1mus7RPwYJ8IGRYEPIJIKuF1N2O96dJIB2RMRlJzsD2jk55BCtjCN0U7o+d/3AZ4AuKEh0IXY5Yr5oOsk/KMqldN55AwLoTfUTpMWeD1lNcTXduzJAbjHvgZpYOrc3So45Hc37awuiVrJKNN5rffx/YeVRw16VC992SNJqffwEdEjChlLm97mLkGpyP8WKNxfae+Ma3IcZlO/Todty+CSPhKqQeXv66wZb3E1ibsgnNfgD8id6oJnjsaZ8aXbLtI17n9mv3c6WufvtlS6j9WFQwGpiHjp9H/E3DhztX+j+7b5N33b1cH7iL/WTEtbAnfeyB/0XOzUZfwZrI+kWaNtpuq4TfIT3HT0vp6TSYoK+TEndJveGsRxY93Sn0SeE9u7saRrlx6sXsuRlZcvbyfZjm8Mf6OmvRxreypDV36uLCtgyzj4FxCa/gNa+B6SqpYzJ2AW8mZnT4C74KhmM=)
 
-If your library needs to differentiate between bundlers and direct browser usage during development then you may need to adjust the build to generate more files. 
+If your library needs to differentiate between bundlers and direct browser usage during development then you may need to adjust the build to generate more files.
 
 ### `<name>.esm-browser.prod.js`
 

packages/docs/src/next-steps.md

@@ -20,7 +20,7 @@ You should do this before running `pnpm install`, so that `simple-git-hooks` can
 pnpm install
 ```
 
-The project uses the `^` prefix for most dependencies. This is usually what you'd want, as it ensures you're getting the latest versions, but it does mean that the exact versions you install may differ slightly from those that have been tested with this tool. Occasionally, new releases of the dependencies introduce regressions that break a newly scaffolded project. 
+The project uses the `^` prefix for most dependencies. This is usually what you'd want, as it ensures you're getting the latest versions, but it does mean that the exact versions you install may differ slightly from those that have been tested with this tool. Occasionally, new releases of the dependencies introduce regressions that break a newly scaffolded project.
 
 Bugs in the tool itself are also very much a possibility, especially if you've picked an unusual combination of options.
 

packages/docs/src/upgrading.md

@@ -1,6 +1,6 @@
 # Upgrading
 
-As a new tool, there hasn't really been time to establish how `@skirtle/create-vue-lib` handles upgrades. But it's maybe still worth some brief notes on how it's intended to be used. 
+As a new tool, there hasn't really been time to establish how `@skirtle/create-vue-lib` handles upgrades. But it's maybe still worth some brief notes on how it's intended to be used.
 
 Much like [`create-vue`](https://github.com/vuejs/create-vue), there isn't any explicit support for upgrading projects. Both tools aim to create new projects, with any upgrades being managed manually. In most cases this just involves bumping dependencies regularly, so there's no need to involve the scaffolding tool.
 

packages/docs/src/why.md

@@ -22,7 +22,7 @@ Those projects use [rollup](https://rollupjs.org/) directly for their builds, ra
 - Using Vite keeps us closer to `create-vue`.
 - Vite has its own ecosystem of useful plugins.
 
-In particular, the libraries mentioned above don't use `.vue` files in their source code. Compiling `.vue` files with rollup is certainly possible, but it's more convenient to reuse the same toolchain used to build Vue applications. 
+In particular, the libraries mentioned above don't use `.vue` files in their source code. Compiling `.vue` files with rollup is certainly possible, but it's more convenient to reuse the same toolchain used to build Vue applications.
 
 <!--