aboutsummaryrefslogtreecommitdiffstats
path: root/proposals/20201012_no_capture.md
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@archive.org>2021-11-24 16:01:47 -0800
committerBryan Newbold <bnewbold@archive.org>2021-11-24 16:01:51 -0800
commitd93d542adf9d26633b0f3cfa361277ca677c46f3 (patch)
treec133d3030746afe25300a2e12a7645407a89b623 /proposals/20201012_no_capture.md
parentb4ca684c83d77a9fc6e7844ea8c45dfcb72aacb4 (diff)
downloadsandcrawler-d93d542adf9d26633b0f3cfa361277ca677c46f3.tar.gz
sandcrawler-d93d542adf9d26633b0f3cfa361277ca677c46f3.zip
codespell fixes in proposals
Diffstat (limited to 'proposals/20201012_no_capture.md')
-rw-r--r--proposals/20201012_no_capture.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/20201012_no_capture.md b/proposals/20201012_no_capture.md
index bb47ea2..27c14d1 100644
--- a/proposals/20201012_no_capture.md
+++ b/proposals/20201012_no_capture.md
@@ -29,7 +29,7 @@ The current status quo is to store the missing URL as the last element in the
pipeline that would read from the Kafka feed and extract them, but this would
be messy. Eg, re-ingesting would not update the old kafka messages, so we could
need some accounting of consumer group offsets after which missing URLs are
-truely missing.
+truly missing.
We could add a new `missing_url` database column and field to the JSON schema,
for this specific use case. This seems like unnecessary extra work.