diff --git a/site/learn/BestPractice-Pagination.md b/site/learn/BestPractice-Pagination.md
index cba0d0f2f5..eeb72dbba0 100644
--- a/site/learn/BestPractice-Pagination.md
+++ b/site/learn/BestPractice-Pagination.md
@@ -78,7 +78,7 @@ The concept of an edge also proves useful if there is information that is specif
 
 Now we have the ability to paginate through the connection using cursors, but how do we know when we reach the end of the connection? We have to keep querying until we get an empty list back, but we'd really like for the connection to tell us when we've reached the end so we don't need that additional request. Similarly, what if we want to know additional information about the connection itself; for example, how many total friends does R2-D2 have?
 
-To solve both of these problems, our `friends` field can return a connection object. The connection object will then have field for the edges, as well as other information (like total count and information about whether a next page exists). So our final query might look more like:
+To solve both of these problems, our `friends` field can return a connection object. The connection object will then have a field for the edges, as well as other information (like total count and information about whether a next page exists). So our final query might look more like:
 
 
 ```graphql