Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix a minor typo in README #480

Merged
merged 1 commit into from
Aug 28, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ Running the retrieval service separately (as opposed to in the app itself) can
help address a number of challenges
1. **Better recall** - LLMs perform better when given smaller, discrete tasks
they can use to accomplish larger goals. By mapping a specific action to a
specify, pre-determined query it significantly improves the LLMs ability to
specific, pre-determined query it significantly improves the LLMs ability to
leverage it successfully.
1. **Better scalability** - Running the retrieval as a separate service both
allows multiple different LLMs to leverage it, as well as allowing it to
Expand Down