Skip to content

Commit 599db42

Browse files
authored
Improve clarity in README.md Statement of Need
Reorder sentences for clarity in the Statement of Need section.
1 parent e006d48 commit 599db42

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,9 @@
4343

4444
## Statement of Need
4545

46-
Researchers frequently accumulate reference lists in ad-hoc formats — DOIs copied from browser tabs, arXiv IDs from paper PDFs, titles typed by hand, and BibTeX fragments from various sources. Cleaning these into a consistent, complete `.bib` file is tedious and error-prone. However, in the era of Generative AI, compiling a bibliography is no longer just about formatting—it is about **verification**. **OneCite acts as the firewall between AI outputs and your manuscript.** By serving as a deterministic truth-detector at the API-lookup layer, OneCite takes raw, unverified text and cross-checks every single entry against canonical academic databases (CrossRef, PubMed, arXiv, Semantic Scholar, etc.).
46+
Researchers frequently accumulate reference lists in ad-hoc formats—DOIs copied from browser tabs, arXiv IDs from paper PDFs, titles typed by hand, and BibTeX fragments from various sources. Cleaning these into a consistent, complete `.bib` file is tedious and error-prone. However, in the era of Generative AI, compiling a bibliography is no longer just about formatting—it is about **verification**. OneCite takes raw, unverified text and cross-checks every single entry against canonical academic databases (CrossRef, PubMed, arXiv, Semantic Scholar, etc.). By serving as a deterministic truth-detector at the API-lookup layer, **OneCite acts as the firewall between AI outputs and your manuscript.**
47+
48+
4749

4850
**When to use OneCite vs. alternatives:**
4951

0 commit comments

Comments
 (0)