(docs) discourage setting language defaults

Author: dummdidumm

docs/preprocessors/in-general.md

@@ -38,19 +38,7 @@ It's also necessary to add a `type="text/language-name"` or `lang="language-name
 
 #### Using language defaults
 
-If you use `svelte-preprocess` and define the defaults inside `svelte.config.js`, you can in some cases omit the `type`/`lang` attributes. While these defaults get picked up by the language server, this may break your syntax highlighting and your code is no longer colored the right way, so use with caution - we recommend to always type the attributes. Reason: we have to tell VSCode which part of the Svelte file is written in which language through providing static regexes, which rely on the `type`/`lang` attribute.
-
-```js
-const sveltePreprocess = require('svelte-preprocess');
-
-module.exports = {
-    preprocess: sveltePreprocess({
-        defaults: {
-            script: 'typescript' // <-- now you can just write <script>let typingsAllowed: string;</script>
-        }
-    })
-};
-```
+If you use `svelte-preprocess` and [define the defaults](https://github.com/sveltejs/svelte-preprocess/blob/main/docs/preprocessing.md#auto-preprocessing-options) inside `svelte.config.js`, you can in some cases omit the `type`/`lang` attributes. While these defaults get picked up by the language server, this may break your syntax highlighting and your code is no longer colored the right way, so use with caution - reason: we have to tell VSCode which part of the Svelte file is written in which language through providing static regexes, which rely on the `type`/`lang` attribute. It will also likely not work for other tooling in the ecosystem, for example `eslint-plugin-svelte3` or `prettier-plugin-svelte`. **We therefore recommend to always type the attributes.**
 
 #### Deduplicating your configs