fix(docs): Corrected typos in project documentation (#669)

Author: plan-do-break-fix

docs/api/README.md

@@ -176,7 +176,7 @@ set({
 setTimeout(() => remove(), 3000)
 ```
 
-There is no reactivity for custom apps. The integrator need to take care of that and call `set` and `remove` when appropiate. If you call `addApp.set` on the client before the app is mounted, the tags will be processed on the first refresh. If you call set when the app is mounted they tags are immediately processed.
+There is no reactivity for custom apps. The integrator need to take care of that and call `set` and `remove` when appropriate. If you call `addApp.set` on the client before the app is mounted, the tags will be processed on the first refresh. If you call set when the app is mounted they tags are immediately processed.
 
 The function is called addApp because the added metaInfo is treated exactly the same as when there are multiple apps on one page. Eg the tags that will be added will also list the `appId` you specifiy:
 ```html

docs/faq/performance.md

@@ -4,7 +4,7 @@ Short answer, no
 
 On the client, `vue-meta` batches DOM updates using [`requestAnimationFrame`](https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame). It needs to do this because it registers a Vue mixin that subscribes to the [`beforeMount`](https://vuejs.org/api/#beforeMount) lifecycle hook on all components in order to be notified that renders have occurred and data is ready. If `vue-meta` did not batch updates, the DOM metadata would be re-calculated and re-updated for every component on the page in quick-succession.
 
-Thanks to batch updating, the update will only occurr once - even if the correct metadata has already been compiled by the server. If you don't want this behaviour, see below.
+Thanks to batch updating, the update will only occur once - even if the correct metadata has already been compiled by the server. If you don't want this behaviour, see below.
 
 :::tip Improvements since v2.0
 Previous versions of vue-meta injected lifecycle hooks from the global mixin on all components on the page. Also when refreshing metadata it checked all components on the page