docs: update links to svelte-hmr readme (#415)

Author: dominikg

docs/config.md

@@ -173,10 +173,10 @@ A [picomatch pattern](https://github.com/micromatch/picomatch), or array of patt
 
 ### hot
 
-- **Type:** `boolean | SvelteHotOptions` - See [svelte-hmr](https://github.com/sveltejs/svelte-hmr#options)
+- **Type:** `boolean | SvelteHotOptions` - See [svelte-hmr](https://github.com/sveltejs/svelte-hmr/blob/master/packages/svelte-hmr#options)
 - **Default:** `true` for development, always `false` for production
 
-  Enable or disable Hot Module Replacement ([HMR](https://github.com/sveltejs/svelte-hmr#whats-hmr-by-the-way)).
+  Enable or disable Hot Module Replacement ([HMR](https://github.com/sveltejs/svelte-hmr/blob/master/packages/svelte-hmr#whats-hmr-by-the-way)).
 
   > Do not customize the options unless you know exactly what you are doing.
 

docs/faq.md

@@ -2,7 +2,7 @@
 
 ### Why is component state reset on HMR update?
 
-Preservation of local component state after JS updates is disabled to avoid unpredictable and error-prone behavior. You can read more about it [here](https://github.com/rixo/svelte-hmr#preservation-of-local-state).
+Preservation of local component state after JS updates is disabled to avoid unpredictable and error-prone behavior. You can read more about it [here](https://github.com/sveltejs/svelte-hmr/blob/master/packages/svelte-hmr#preservation-of-local-state).
 
 Please note that if you only edit the `<style>` node, a separate CSS update can be applied where component state is 100% preserved.