fix tables, fix links, fix blocks (#1077)

* fix tables in index config

* fix notion links

* fix caution, tip block

* fix caution blocks

Author: PSeitz

docs/reference/index-config.md

@@ -85,13 +85,11 @@ Today, only the s3 storage is available when running several searcher nodes.
 
 The doc mapping defines how a document and the fields it contains are stored and indexed for a given index. A document is a collection of named fields, each having its own data type (text, binary, date, i64, u64, f64).
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `field_mappings` | Collection of field mapping, each having its own data type (text, binary, date, i64, u64, f64).   | [] |
 | `tag_fields` | Collection of fields already defined in `field_mappings` whose values will be stored in a dedicated `tags` (1) | [] |
 | `store_source` | Whether or not the original JSON document is stored or not in the index.   | false |
-```
 
 (1) [Learn more on the tags usage](../design/querying.md).
 
@@ -119,33 +117,27 @@ record: position
 
 **Parameters for text field**
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `stored`    | Whether value is stored in the document store | `true` |
 | `tokenizer` | Name of the `Tokenizer`, choices between `raw`, `default` and `stem_en` | `default` |
 | `record`    | Describes the amount of information indexed, choices between `basic`, `freq` and `position` | `basic` |
-```
 
 **Description of available tokenizers**
 
-```markdown
 | Tokenizer     | Description   |
 | ------------- | ------------- |
 | `raw`         | Does not process nor tokenize text  |
 | `default`     | Chops the text on according to whitespace and punctuation, removes tokens that are too long, and lowercases tokens |
 | `stem_en`     |  Like `default`, but also applies stemming on the resulting tokens  |
-```
 
 **Description of record options**
 
-```markdown
 | Record option | Description   |
 | ------------- | ------------- |
 | `basic`       |  Records only the `DocId`s |
 | `freq`        |  Records the document ids as well as the term frequency  |
 | `position`    |  Records the document id, the term frequency and the positions of occurences.  |
-```
 
 Indexing with position is required to run phrase queries.
 
@@ -167,13 +159,11 @@ fast: true
 
 **Parameters for i64, u64 and f64 field**
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `stored`    | Whether value is stored in the document store | `true` |
 | `indexed`   | Whether value is indexed | `true` |
 | `fast`      | Whether value is stored in a fast field | `false` |
-```
 
 #### `date` type
 
@@ -191,13 +181,11 @@ fast: true
 
 **Parameters for date field**
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `stored`    | Whether value is stored in the document store | `true` |
 | `indexed`   | Whether value is indexed | `true` |
 | `fast`      | Whether value is stored in a fast field | `false` |
-```
 
 #### `bytes` type
 The `bytes` type accepts a binary value as a `Base64` encoded string.
@@ -214,13 +202,11 @@ fast: true
 
 **Parameters for bytes field**
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `stored`    | Whether value is stored in the document store | `true` |
 | `indexed`   | Whether value is indexed | `true` |
 | `fast`     | Whether value is stored in a fast field | `false` |
-```
 
 ### Composite types
 
@@ -261,7 +247,6 @@ Fields with `null` or missing fields in your JSON document will be silently igno
 
 This section describes indexing settings for a given index.
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `timestamp_field`      | Timestamp field used for sharding documents in splits (1).   | None |
@@ -271,7 +256,6 @@ This section describes indexing settings for a given index.
 | `merge_policy.max_merge_factor`      | Maximum number of splits to merge.   | 12 |
 | `resources.num_threads`      | Number of threads per source.   | 1 |
 | `resources.heap_size`      | Indexer heap size per source per index.   | 2_000_000_000 |
-```
 
 (1) [Learn more on time sharding]( ../design/architecture.md)
 
@@ -285,11 +269,9 @@ Indexer works with a default heap of 2 GiB of memory. This does not directly ref
 
 This section describes search settings for a given index.
 
-```markdown
 | Variable      | Description   | Default value |
 | ------------- | ------------- | ------------- |
 | `search_default_fields`      | Default list of fields that will be used for search.   | None |
-```
 
 ## Sources
 

docs/reference/metastore-config.md

@@ -12,7 +12,7 @@ For instance:
 - The different sources checkpoints.
 - Some extra information such as the index creation time.
 
-The metastore is entirely defined by a single URI. One can set it by editing the `metastore_uri` parameter of the [Quickwit configuration file](https://www.notion.so/Quickwit-configuration-MERGED-3fab5a181a9a43cba83db2fb25b46729) (often named `quickwit.yaml`).
+The metastore is entirely defined by a single URI. One can set it by editing the `metastore_uri` parameter of the [Quickwit configuration file](./quickwit-config.md) (often named `quickwit.yaml`).
 
 Currently, Quickwit offers two implementations:
 
@@ -48,7 +48,7 @@ Likewise, if you upgrade Quickwit to a version that includes some changes in the
 
 For convenience, Quickwit also makes it possible to store its metadata in files using a file-backed metastore. In that case, Quickwit will write one file per index.
 
-The metastore is then configured by passing a [Storage URI](https://www.notion.so/Storage-URI-APPROVED-176d8befb8d144fb820bcd0df077a728) that will serve as the root of the metastore storage.
+The metastore is then configured by passing a [Storage URI](./storage-uri.md) that will serve as the root of the metastore storage.
 
 The metadata file associated with a given index will then be stored under 
 
@@ -57,7 +57,7 @@ The metadata file associated with a given index will then be stored under
 For the moment, Quickwit supports two types of storage types:
 
 - a local file system URI (e.g., `file:///opt/toto`). It is also valid to pass a file path directly (without file://). `/var/quickwit`. Relative paths will be resolved with respect to the current working directory.
-- S3-compatible storage URI (e.g. `s3://my-bucket/some-path`] ). See the [Storage URI](https://www.notion.so/Storage-URI-APPROVED-176d8befb8d144fb820bcd0df077a728) documentation to configure S3 or S3-compatible storage.
+- S3-compatible storage URI (e.g. `s3://my-bucket/some-path`] ). See the [Storage URI](./storage-uri.md) documentation to configure S3 or S3-compatible storage.
 
 ### Polling configuration
 
@@ -67,10 +67,10 @@ You can also configure it to poll the File-Backed Metastore periodically to keep
 
 To configure the polling interval (in seconds only), add a URI fragment to the storage URI like this: `s3://quickwit/my-indexes#polling_interval=30s`
 
-<aside>
-👌 Amazon S3 charges $0.0004 per 1000 GET requests. Polling a metastore every 30 seconds will induce a cost of $0.04 per month and per index.
+:::tip
+Amazon S3 charges $0.0004 per 1000 GET requests. Polling a metastore every 30 seconds will induce a cost of $0.04 per month and per index.
 
-</aside>
+:::
 
 ### Examples
 
@@ -86,9 +86,9 @@ file:///local/indices#polling_interval=30s
 ./quickwit-metastores
 ```
 
-<aside>
-⛔ The file-backed metastore does not allow concurrent writes. For this reason, it should not be used in distributed settings. 
+:::caution
+The file-backed metastore does not allow concurrent writes. For this reason, it should not be used in distributed settings. 
 Running several indexer services on the same file-backed metastore can lead to the corruption of the metastore.
 Running several search services, on the other hand, is perfectly safe.
 
-</aside>
+:::

docs/reference/storage-uri.md

@@ -30,12 +30,12 @@ The following are valid local file system URIs
 - ./quickwit
 ```
 
-<aside>
-⚠️ When using the `file://` protocol, a third `/` is necessary to express an absolute path.
+:::caution
+When using the `file://` protocol, a third `/` is necessary to express an absolute path.
 
 For instance, the following URI `file://home/quickwit/` is interpreted as `./home/quickwit`
 
-</aside>
+:::
 
 ## Amazon S3
 
@@ -70,7 +70,7 @@ The region will be detected using the first successful method in this list (orde
 - `AWS_REGION` environment variable
 - Amazon’s instance metadata API [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html)
 
-<aside>
-⚠️ Custom endpoints are not supported yet.
+:::caution
+Custom endpoints are not supported yet.
 
-</aside>
+:::