From ed2617e682b1a93bb17ac7f2f8235e334a9d485b Mon Sep 17 00:00:00 2001
From: David Dunn <26876072+doubledup@users.noreply.github.com>
Date: Tue, 20 Oct 2020 13:50:31 +0200
Subject: [PATCH] Fix fragment name

Conditional fragments aren't referenced anywhere else in the documentation,
going by results from the search bar. This is introduced as an inline fragment
in the "Queries and Mutations" section.
---
 site/learn/Learn-Schema.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/learn/Learn-Schema.md b/site/learn/Learn-Schema.md
index 40a5b7ced5..9f42f072db 100644
--- a/site/learn/Learn-Schema.md
+++ b/site/learn/Learn-Schema.md
@@ -305,7 +305,7 @@ union SearchResult = Human | Droid | Starship
 
 Wherever we return a `SearchResult` type in our schema, we might get a `Human`, a `Droid`, or a `Starship`. Note that members of a union type need to be concrete object types; you can't create a union type out of interfaces or other unions.
 
-In this case, if you query a field that returns the `SearchResult` union type, you need to use a conditional fragment to be able to query any fields at all:
+In this case, if you query a field that returns the `SearchResult` union type, you need to use an inline fragment to be able to query any fields at all:
 
 ```graphql
 # { "graphiql": true}