wip(docs): minor enhancements

Author: FranckFreiburger

README.md

@@ -1,6 +1,6 @@
 # vue3-sfc-loader
 
-###### [API](docs/api/README.md#loadmodule) | see [FAQ](docs/faq.md) | [Examples](docs/examples.md) | [dist](#dist) | [Roadmap](../../issues/1)
+###### [API](docs/api/README.md#loadmodule) | [FAQ](docs/faq.md) | [Examples](docs/examples.md) | [dist](#dist) | [Roadmap](../../issues/1)
 
 Vue3/Vue2 Single File Component loader.  
 Load .vue files dynamically at runtime from your html/js. No node.js environment, no (webpack) build step needed.  

docs/faq.md

@@ -2,7 +2,7 @@
 
 ## How to use 3rd party plugins or components
 
-#### from a `<script>` tag
+#### From a `<script>` tag
 If the plugin is loaded through a `<script>` tag, you have to store the plugin's module in `options.moduleCache`.
 Note that this is what is currently done with vue :
 ```
@@ -16,10 +16,11 @@ const options = {
 ```
 then, subsequent `import Vue from 'vue'` will return the Vue module (`options.moduleCache.vue`).
 
-#### same origin
+#### From the same origin
 If your plugin is reachable from the current URL (same origin, relative or absolute) just use `import from`, `import()` or `require()`.
 `vue3-sfc-loader` is able to load esm and cjs modules). Just take care to specify the plugin entry point.
 
+
 eg.
 ```
 import Vue from 'vue'
@@ -28,7 +29,7 @@ vue.use(myPlugin);
 ...
 ```
 
-#### from a different origin (remote component)
+#### From a different origin (remote component)
 If your plugin is hosted elsewhere (on a different origin), you have to define your own `option.pathResolve`.
 See https://github.com/FranckFreiburger/vue3-sfc-loader/blob/main/docs/examples.md#use-remote-components