From 69247bc14397e0a3878927e347f480849bd2af07 Mon Sep 17 00:00:00 2001 From: Trevor Scheer Date: Sun, 2 Sep 2018 18:52:16 -0400 Subject: [PATCH] Correct description on mocking --- docs/source/mocking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/mocking.md b/docs/source/mocking.md index 7e310fea45e..f7b4756bf7b 100644 --- a/docs/source/mocking.md +++ b/docs/source/mocking.md @@ -5,7 +5,7 @@ description: Mock your GraphQL data based on a schema. The strongly-typed nature of a GraphQL API lends itself extremely well to mocking. This is an important part of a GraphQL-First development process, because it enables frontend developers to build out UI components and features without having to wait for a backend implementation. -Even when the UI is already built, it can let you test your UI without waiting on slow database requests, or build out a component harness using a tool like React Storybook without needing to start a real GraphQL server. +Even with a backend that is already built, mocking allows you to test your UI without waiting on slow database requests or building out a component harness with a tool like React Storybook. ## Default mock example