Suggestion: Markdown Linting with Spelling and Grammar Reporting (Possible automated CI pipeline)

It is suggested to use [markdown-lint](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint) extension of VSCode or some other tool(s) to automate the linting of the markdown files. The linting rules may also be configured for the exceptions in `.markdownlint.json` file and this may be added to this project to enforce the recommended Markdown format setting.

This integration may somehow be automated to create a CI pipeline for the submitted PRs.

The [redis-doc](https://github.com/redis/redis-doc) is worth to look at. It uses [Aspell](http://aspell.net/) for spelling mistakes.

Other relevant tools and/or solutions may also be suggested to automate the CI which would definitely help all the future work adhere to the recommended practices resulting in to-the-point reviews i.e. **documentation** and not the style, spelling, and grammar issues.

Regards!

Comienza revisando la configuración propuesta de .markdownlint.json y las referencias a markdown-lint y Aspell en el issue. Compara el enfoque de redis-doc y, después, inspecciona los puntos de entrada de CI disponibles en el repositorio. La tarea estará terminada cuando el proyecto tenga un enfoque acordado para el linting y la comprobación ortográfica, con comprobaciones automatizadas para los PRs enviados.

Escrito por el modelo de indexación a partir del texto del issue.