Fix image location config

docs-site/content/.vuepress/config.js

@@ -1,5 +1,6 @@
 const { description } = require('../../package')
 const { typesenseVersions, typesenseLatestVersion } = require('../../../typsenseVersions')
+const path = require('path')
 
 let config = {
   // The base URL the site will be deployed at
@@ -696,7 +697,7 @@ let config = {
   configureWebpack: {
     resolve: {
       alias: {
-        '@images': '../../.vuepress/public/images'
+        '@images': path.resolve(__dirname, 'public/images/')
       }
     }
   }

docs-site/content/0.19.0/guide/features/faceting.md

@@ -335,4 +335,4 @@ Smaple response:
 }
 ```
 
-Note the additional `stats` field in the result that shows the avg, min, max and sum value for `ratings_count` field. You can limit the number of faceted results using `max_facet_value` parameter. More details on these arguments can be found [here](https://typesense.org/docs/0.19.0/api/documents.html#arguments).
+Note the additional `stats` field in the result that shows the avg, min, max and sum value for `ratings_count` field. You can limit the number of faceted results using `max_facet_value` parameter. More details on these arguments can be found [here](../../api/documents.html#arguments).

docs-site/content/0.19.0/guide/features/filtering.md

@@ -104,5 +104,5 @@ Here is a sample response:
 }
 ```
 
-You can also filter results by matching a field with more than one value. More details on the argument can be found [here](https://typesense.org/docs/0.19.0/api/documents.html#arguments).
+You can also filter results by matching a field with more than one value. More details on the argument can be found [here](../../api/documents.html#arguments).
 # Filtering

docs-site/content/0.19.0/guide/features/typo-tolerance.md

@@ -2,7 +2,7 @@
 
 Typo, short for typographical error, is a mistake made while typing something. A typo is generally an unintentional mistake that can happen due to typing faster or typing on a screen where the keypad is small. However, sometimes your users might not know the exact spelling of the word and they type what they think is an approximation of the exact term, in the hope that the system would understand and bring up the relevant results. 
 
-Typesense can handle typos out of the box. It can understand what users are looking for even if there is a mistake in the search query and provide relevant results.  Let's see it in action! To follow this example, first [create](https://typesense.org/docs/0.19.0/api/collections.html#create-a-collection) a collection named "companies" and [index](https://typesense.org/docs/0.19.0/api/documents.html#index-a-document) a sample document. Now, let's perform a search (notice the typo!): 
+Typesense can handle typos out of the box. It can understand what users are looking for even if there is a mistake in the search query and provide relevant results.  Let's see it in action! To follow this example, first [create](../../api/collections.html#create-a-collection) a collection named "companies" and [index](../../api/documents.html#index-a-document) a sample document. Now, let's perform a search (notice the typo!): 
 
 <Tabs :tabs="['JavaScript','PHP','Python','Ruby']">
   <template v-slot:JavaScript>
@@ -93,6 +93,6 @@ Here is the sample response:
 }
 ```
 
-Typesense can get you the relevant results even if there is a typo in the search query. You can control the extent of typo toleration using the `num_typos` argument. The default value is 2. You can also keep looking for results with more typos until a threshold is reached using the `typo_tokens_threshold` argument. More details on these arguments can be found [here](https://typesense.org/docs/0.19.0/api/documents.html#arguments).
+Typesense can get you the relevant results even if there is a typo in the search query. You can control the extent of typo toleration using the `num_typos` argument. The default value is 2. You can also keep looking for results with more typos until a threshold is reached using the `typo_tokens_threshold` argument. More details on these arguments can be found [here](../../api/documents.html#arguments).