diff --git a/paper_hashtag_federation.pdf b/paper_hashtag_federation.pdf
index e1b3d7b..c3c4c6e 100644
--- a/paper_hashtag_federation.pdf
+++ b/paper_hashtag_federation.pdf
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7b8c709790dfd17dffc24e96870fce4403f145ee5f475c3c1144317aecb76143
-size 2920622
+oid sha256:d6a357547f76bf1d6a6b7bf1485a064ee97826364404da7f1708844a3697db50
+size 2920699
diff --git a/paper_hashtag_federation.tex b/paper_hashtag_federation.tex
index e724650..9ab28c9 100644
--- a/paper_hashtag_federation.tex
+++ b/paper_hashtag_federation.tex
@@ -219,7 +219,7 @@ While the view onto the post history of a hashtag shall be consistent no matter
 \item \textbf{size of posts}:\label{ass:post_size}
 As posts are text-only objects of the content, often having a size limit of 500--1000 characters, and some additional metadata, we assume the size of each post to be \(\leq 10\) KiB.
 \item \textbf{size of post URIs}:\label{ass:url_size}
-Each post is identifiable by dereferenceable \ac{URI} and can be retrieved from there.  Given the \acp{URI} in existing network server implementations, we assume them to have a size \(\leq 1\) KiB.
+Each post is identified by dereferenceable \ac{URI} and can be retrieved from there.  Given the \acp{URI} in existing network server implementations, we assume them to have a size \(\leq 1\) KiB.
 \end{itemize}
 
 \subsection{Security}