aboutsummaryrefslogtreecommitdiffstats
path: root/proposals/2021-01-29_citation_api.md
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2021-11-24 15:48:01 -0800
committerBryan Newbold <bnewbold@robocracy.org>2021-11-24 15:48:01 -0800
commitd6b1d3de6224b590a82b175f78b761df1a6df4a2 (patch)
treecdc5904d0136432fbfa0500fe136897eea650c34 /proposals/2021-01-29_citation_api.md
parentcc0393de91301a29bd469e38519125a530b4472d (diff)
downloadfatcat-d6b1d3de6224b590a82b175f78b761df1a6df4a2.tar.gz
fatcat-d6b1d3de6224b590a82b175f78b761df1a6df4a2.zip
codespell fixes to proposals
Diffstat (limited to 'proposals/2021-01-29_citation_api.md')
-rw-r--r--proposals/2021-01-29_citation_api.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/2021-01-29_citation_api.md b/proposals/2021-01-29_citation_api.md
index 3805dcac..6379da09 100644
--- a/proposals/2021-01-29_citation_api.md
+++ b/proposals/2021-01-29_citation_api.md
@@ -212,7 +212,7 @@ would make "outbound" queries a trivial key lookup, instead of a query by
rows would be returned, with unwanted metadata.
Another alternative design would be storing more metadata about source and
-target in each row. This would remove the ned to do separate
+target in each row. This would remove the need to do separate
"hydration"/"enrich" fetches. This would probably blow up in the index size
though, and would require more aggressive re-indexing (in a live-updated
scenario). Eg, when a new fulltext file is updated (access option), would need