From 417f14f952c5e10f82f17d5f62c3794caef0fbd0 Mon Sep 17 00:00:00 2001 From: Sharif Mamun Date: Fri, 20 Dec 2024 13:45:18 -0800 Subject: [PATCH] Fix typo in serving-over-http.mdx --- src/pages/learn/serving-over-http.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/learn/serving-over-http.mdx b/src/pages/learn/serving-over-http.mdx index 22021696cf..5ed1ff6d33 100644 --- a/src/pages/learn/serving-over-http.mdx +++ b/src/pages/learn/serving-over-http.mdx @@ -4,7 +4,7 @@ import { Callout } from "nextra/components"

Respond to GraphQL requests using an HTTP server

-The GraphQL specification doesn't require paricular client-server protocols when sending API requests and responses, but HTTP is the most common choice because of its ubiquity. On this page, we'll review some key guidelines to follow when setting up a GraphQL server to operate over HTTP. +The GraphQL specification doesn't require particular client-server protocols when sending API requests and responses, but HTTP is the most common choice because of its ubiquity. On this page, we'll review some key guidelines to follow when setting up a GraphQL server to operate over HTTP. Note that the guidelines that follow only apply to stateless query and mutation operations. Visit the [Subscriptions page](/learn/subscriptions) for more information on transport protocols that commonly support these requests.