From 94a164b59839b248119257ad7c550a617fb86515 Mon Sep 17 00:00:00 2001
From: Arpit Kushwaha <29251567+shark-h@users.noreply.github.com>
Date: Thu, 9 May 2019 16:05:48 +0530
Subject: [PATCH] Updated the Boilerplate link to point to
 community/boilerplates/remote-schemas/ and removed the line about "Interfaces
 are not supported"

---
 remote-schemas.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/remote-schemas.md b/remote-schemas.md
index d1195cc8963fa..f34278d9d558a 100644
--- a/remote-schemas.md
+++ b/remote-schemas.md
@@ -6,7 +6,7 @@ Merge remote GraphQL schemas with GraphQL Engine's Postgres-based schema to quer
 * Supporting features like payments, etc. and providing a consistent interface to access them i.e. behind the GraphQL Engine's API
 * Fetching disparate data from other sources (*e.g. from a weather API or another database*)
 
-To support custom business logic, you'll need to create a custom GraphQL server (see [boilerplates](community/boilerplates/graphql-servers)) and merge its schema with GraphQL Engine's.
+To support custom business logic, you'll need to create a custom GraphQL server (see [boilerplates](community/boilerplates/remote-schemas)) and merge its schema with GraphQL Engine's.
 
 ![remote schems architecture](assets/remote-schemas-arch.png)
 
@@ -69,7 +69,6 @@ Please note that boilerplates for more languages, frameworks, serverless platfor
 * Nomenclature: Type names and node names need to be unique across all merged schemas (case-sensitive match). In the next few iterations, support for merging types with the exact same name and structure will be available.
 * Nodes from different GraphQL servers cannot be used in the same query/mutation. All top-level nodes have to be from the same GraphQL server.
 * Subscriptions on remote GraphQL server are not supported.
-* Interfaces are not supported - if a remote schema has interfaces, an error will be thrown if you try to merge it.
 
 These limitations will be addressed in upcoming versions.