From 458cc190897c608df1e6f648cc28b793e88757ec Mon Sep 17 00:00:00 2001
From: soaringeagle <32617597+311289189@users.noreply.github.com>
Date: Sat, 10 Feb 2018 13:10:06 +0100
Subject: [PATCH] Update Learn-Queries.md

change to once, you would need to repeat at least once
---
 site/learn/Learn-Queries.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/learn/Learn-Queries.md b/site/learn/Learn-Queries.md
index 15ac8422f8..72bc263bb2 100644
--- a/site/learn/Learn-Queries.md
+++ b/site/learn/Learn-Queries.md
@@ -98,7 +98,7 @@ In the above example, the two `hero` fields would have conflicted, but since we
 
 ## Fragments
 
-Let's say we had a relatively complicated page in our app, which let us look at two heroes side by side, along with their friends. You can imagine that such a query could quickly get complicated, because we would need to repeat the fields at least twice - one for each side of the comparison.
+Let's say we had a relatively complicated page in our app, which let us look at two heroes side by side, along with their friends. You can imagine that such a query could quickly get complicated, because we would need to repeat the fields at least once - one for each side of the comparison.
 
 That's why GraphQL includes reusable units called _fragments_. Fragments let you construct sets of fields, and then include them in queries where you need to. Here's an example of how you could solve the above situation using fragments: