> For the complete documentation index, see [llms.txt](https://lesp.gitbook.io/lesp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lesp.gitbook.io/lesp/intro/introduction.md). # Introduction Have you ever struggled with developing a reliable spellcheck algorithm? Do you wish there was a simple and fast way to check and correct spelling mistakes? If so, you might be interested in LESP, a lightweight efficient spelling proofreader library written in Python. LESP is a project that aims to provide a decent spelling correction solution that is easy to use and lightweight. It does not require any additional libraries or dependencies, and it works on any platform that supports Python 3.6 or higher. LESP uses a wordlist-based approach to help you find spelling mistakes easily and quickly, without consuming a lot of resources. In this documentation, you will find everything you need to know about LESP, such as its features, installation, usage, examples, contributing, license, and more. Whether you are a beginner or an expert, you will find LESP useful and easy to integrate into your projects. So, what are you waiting for? Let’s get started! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://lesp.gitbook.io/lesp/intro/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.