From b8ae600d0d139fa76f8350f13f058b2cb795b692 Mon Sep 17 00:00:00 2001
From: "Douglas B. Rumbaugh" <doug@douglasrumbaugh.com>
Date: Sun, 1 Jun 2025 15:09:25 -0400
Subject: more updates

---
 chapters/sigmod23/background.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'chapters/sigmod23/background.tex')

diff --git a/chapters/sigmod23/background.tex b/chapters/sigmod23/background.tex
index d600c27..88f2585 100644
--- a/chapters/sigmod23/background.tex
+++ b/chapters/sigmod23/background.tex
@@ -114,7 +114,7 @@ of problems that will be directly addressed within this chapter.
 \subsection{Algorithmic Solutions}
 
 Relational database systems often have native support for IQS using
-SQL's \texttt{TABLESAMPLE} operator~\cite{postgress-doc}. However, the
+SQL's \texttt{TABLESAMPLE} operator~\cite{postgres-doc}. However, the
 algorithms used to implement this operator have significant limitations
 and do not allow users to maintain statistical independence of the results
 without also running the query to be sampled from in full. Thus, users must
@@ -137,7 +137,7 @@ in full anyway before returning only some of the results.\footnote{
 For performance, the statistical guarantees can be discarded and
 systematic or block sampling used instead. Systematic sampling considers
 only a fraction of the rows in the table being sampled from, following
-some particular pattern~\cite{postgress-doc}, and block sampling samples
+some particular pattern~\cite{postgres-doc}, and block sampling samples
 entire database pages~\cite{db2-doc}. These allow for query performance
 to be decoupled from data size, but tie a given record's inclusion in the
 sample set directly to its physical storage location, which can introduce
-- 
cgit v1.2.3

