Maryam

@dichotommy, are we still using this?

To be done: 1. We currently have **28 warnings and 36 suggestions** - 4 warnings for using `indexation` instead of `indexing` - 2 suggestions for the Oxford comma - The...

Closing this for https://github.com/meilisearch/documentation/issues/1939

I like [Mailchimp's](https://mailchimp.com/developer/marketing/docs/errors/) error page. We currently have most of this information but it's on different pages ([FAQ](https://docs.meilisearch.com/faq.html#what-do-the-different-error-types-mean), [API README](https://docs.meilisearch.com/reference/api/#errors-status-code)). It would be nice if we could move all of...

Can we make Errors a separate heading instead of having it [under API references](https://github.com/meilisearch/documentation/pull/1378)? We could have two pages here, one with just a general introduction and a [table with...

> Attempt to enforce a consistent format for each error, e.g. "Error message", "Why does this error happen", "How to resolve it", "Example" I think we can cover this part...

This is briefly mentioned in #1280 with the help of a gif

Rename [Asynchronous operations](https://docs.meilisearch.com/learn/advanced/asynchronous_operations.html) to include the word “tasks”, e.g. “Tasks and asynchronous processes”.

@dichotommy, is this something we still plan on doing?

Hi @vaish567, Use one format for writing data types. We currently write it with backticks (`string`) and without backticks (string)