From ed8bdb6b90eeb37dc738dd13bc0fff803f943290 Mon Sep 17 00:00:00 2001 From: Glenn Goossens Date: Sat, 19 Feb 2022 23:33:33 +0100 Subject: [PATCH] paragraph rewrite --- website/docs/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/get-started.mdx b/website/docs/get-started.mdx index 3dfdbd9653..23c8b0fca5 100644 --- a/website/docs/get-started.mdx +++ b/website/docs/get-started.mdx @@ -77,7 +77,7 @@ const mySchema = application.schema Now that you have `Module`, `Application` and you got your `GraphQLSchema`, you need to make it available to consumption. -GraphQL-Modules allow you to do much more, like managing the lifecycle of your execution, encapsulate your HTTP request and more. To do that in the most optimal and flexible way, we need to wrap the GraphQL execution flow. Some GraphQL servers implementation allow this kind of flexibility, and some doesn't. +GraphQL-Modules allow you to do much more, like managing the lifecycle of your execution and encapsulating HTTP requests. The most optimal and flexible way to achieve this is by wrapping the GraphQL execution flow; which only some GraphQL server implementations allow. _But we got you covered, and provided solution for all popular GraphQL server implementations._