From 793b9c29a11a6682a5e311ad98a4cac61b4072e4 Mon Sep 17 00:00:00 2001
From: grounzero <16921017+grounzero@users.noreply.github.com>
Date: Thu, 9 Nov 2023 19:32:37 +0000
Subject: [PATCH] Fixed Typos in Strawberry Shake Network Documentation.
 (#6685)

---
 website/src/docs/strawberryshake/v13/networking/index.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/src/docs/strawberryshake/v13/networking/index.md b/website/src/docs/strawberryshake/v13/networking/index.md
index bb0f1c342e0..16a6292af55 100644
--- a/website/src/docs/strawberryshake/v13/networking/index.md
+++ b/website/src/docs/strawberryshake/v13/networking/index.md
@@ -17,11 +17,11 @@ Strawberry Shake supports multiple network protocols to communicate with your Gr
 
 # Transport Profiles
 
-In order to have a small client size and generate the optimized client for your use-case Strawberry Shake uses transport profiles. By default Strawberry Shake will generate a client that uses `GraphQL over HTTP` for queries and mutations and `subscriptions-transport-ws` for subscriptions. Meaning if you are only using queries and mutations you need to add the package `StrawberryShake.Transport.Http`.
+In order to have a small client size and generate the optimized client for your use-case Strawberry Shake uses transport profiles. By default Strawberry Shake will generate a client that uses `GraphQL over HTTP` for queries and mutations and `graphql-transport-ws` for subscriptions. Meaning if you are only using queries and mutations you need to add the package `StrawberryShake.Transport.Http`.
 
-There are cases in which we want to define specialize transport profiles where we for instance define for each request type a specific transport. You can define those transport profiles in your `.graphqlrc.json`.
+There are cases in which we want to define specialized transport profiles where we define for each request type a specific transport. You can define those transport profiles in your `.graphqlrc.json`.
 
-The following `.graphqlrc.json` can be copied into our getting started example and will create two transport profiles. The first is called `Default` and matches the internal default. It will use `GraphQL over HTTP` by default and use `subscriptions-transport-ws` for subscriptions. The second profile is called `WebSocket` and will also use `GraphQL over HTTP` by default but for mutations and subscriptions it will use `subscriptions-transport-ws`.
+The following `.graphqlrc.json` can be copied into our getting started example and will create two transport profiles. The first is called `Default` and matches the internal default. It will use `GraphQL over HTTP` by default and use `graphql-transport-ws` for subscriptions. The second profile is called `WebSocket` and will also use `GraphQL over HTTP` by default but for mutations and subscriptions it will use `graphql-transport-ws`.
 
 ```json
 {