update spelling across docs (#7752)

Author: jonathanawesome

packages/web/docs/src/app/blog/(posts)/add-reactivity-to-an-existing-source/page.mdx

@@ -168,7 +168,7 @@ That's it!
   [playground](https://space-x-land-with-sub.herokuapp.com)
 
 I'm now ready to work on the demo for
-[**Svelte Codegen**](https://github.com/ticruz38/graphql-codegen-svelte-apollo)! Stay tunned ;)
+[**Svelte Codegen**](https://github.com/ticruz38/graphql-codegen-svelte-apollo)! Stay tuned ;)
 
 [@jycouet](https://twitter.com/jycouet)
 

packages/web/docs/src/app/blog/(posts)/ci-ci-graphql-inspector/page.mdx

@@ -75,7 +75,7 @@ We want to make **Azure** and **Bitbucket** a first-class citizens in GraphQL In
 the same experience as you get right now with **GitHub**.
 
 **Monitoring** will enable you to analyze the traffic of your GraphQL APIs and provide details
-needed to improve performance. Collecting informations about the usage will let you safely remove
+needed to improve performance. Collecting information about the usage will let you safely remove
 deprecated pieces of GraphQL Schema.
 
 > If you're interested, please reach out to us!

packages/web/docs/src/app/blog/(posts)/graphql-code-generator-011/page.mdx

@@ -258,7 +258,7 @@ export interface UserDbObject {
 ```
 
 There is also the need to handle the difference between embedded types and linked types, so you can
-use `@entity(embbeded: true)` and `@embbeded` to declare link and embedded entities:
+use `@entity(embedded: true)` and `@embedded` to declare link and embedded entities:
 
 ```graphql
 type User @entity {

packages/web/docs/src/app/blog/(posts)/graphql-codegen-best-practices/page.mdx

@@ -578,7 +578,7 @@ autocomplete inside `.graphql` files.
 GraphQL Code Generator plugins for frontend frameworks integrations (such as
 `typescript-react-apollo` / `typescript-apollo-angular`) are automatically creates an executable
 copy (`DocumentNode`) of your GraphQL operations in the generated code file, and it will
-automatically include it withing your wrapper call.
+automatically include it within your wrapper call.
 
 It will add that to the output file with `Document` suffix, and `FragmentDoc` for fragments.
 

packages/web/docs/src/app/blog/(posts)/graphql-cursor-pagination-with-postgresql/page.mdx

@@ -293,7 +293,7 @@ LIMIT
 + | '8771195f-7a8a-4685-8e4e-ae45d017c11b' | 'Uri'    | '2023-01-11T10:32:07.853915+00:00' |
 ```
 
-The only solution here is to also introduce another, truely unique, column to our cursor. In this
+The only solution here is to also introduce another, truly unique, column to our cursor. In this
 case we can utilize the `"id"` column.
 
 So lets execute the SQL query, but now with both the `id` (`'628995bf-2907-49d1-a36f-978566a053c4'`)

packages/web/docs/src/app/blog/(posts)/graphql-deep-dive-1/page.mdx

@@ -168,7 +168,7 @@ request-response lifecycle strongly typed.
 For instance, there are some amazing projects from [**The Guild**](/) like
 [**GraphQL Codegen**](https://the-guild.dev/graphql/codegen) which we can use for generating types
 based on our local/remote schema with great Typescript integration, and you have a lot of
-plugins/recepies you can use along with it as well.
+plugins/recipes you can use along with it as well.
 
 Want to generate Typescript objects based on GQL documents? You can try out
 [**Typed Document Node**](https://github.com/dotansimha/graphql-typed-document-node)

packages/web/docs/src/app/blog/(posts)/graphql-deep-dive-2/page.mdx

@@ -75,7 +75,7 @@ If you are in the Kubernetes world, you also have a lot of ingress controllers l
 The first thing would be the entry point of all your GraphQL requests. Since GraphQL exposes a
 single endpoint e.g. `/graphql` this becomes the single entry point for all your operations.
 
-But, I highly wouldn't recommend directly exposing your service to client since it can be unsecure,
+But, I highly wouldn't recommend directly exposing your service to client since it can be insecure,
 difficult to manage things like rate-limiting, load balancing and so on.
 
 Rather, it is always recommended to expose it via an API Gateway of your choice. Be it Ambassador,
@@ -220,7 +220,7 @@ This applies not just to the GraphQL ecosystem, but anything you choose for that
 - Does it have a clear roadmap for the future? If so, what are the milestones?
 - What are the other alternatives? How does it compare to them?
 - How is the documentation? Does it have tests? Does it have examples which I can refer to?
-- Does it follow standards and is free of Vendor Lockin?
+- Does it follow standards and is free of Vendor Lock-in?
 - Are there any security concerns which this tool or library might create?
 
 While not all of these questions might have been addressed by the library or tool well, what I see

packages/web/docs/src/app/blog/(posts)/graphql-deep-dive-3/page.mdx

@@ -24,7 +24,7 @@ use case and building the development workflow which suits you best in this blog
 
 Technology changes and evolves constantly as we have already seen it happening all these days. So,
 rather than worrying too much about the technology you choose, it is better to choose a tool,
-library or platform which allows for incremental changes without lockin. Using the list in the
+library or platform which allows for incremental changes without lock-in. Using the list in the
 [**previous blog post**](/blog/graphql-deep-dive-2) might actually help in your decision-making
 process.
 

packages/web/docs/src/app/blog/(posts)/graphql-deep-dive-6/page.mdx

@@ -52,7 +52,7 @@ time.
 
 The best way to avoid this is to put together a boilerplate with all that you would typically want
 to use and this can become a starting point of all the services you may develop in the future. This
-would also involve things like setting up your GraphQL Gateway (incase you are using something like
+would also involve things like setting up your GraphQL Gateway (in case you are using something like
 [Federation](https://the-guild.dev/graphql/hive/federation) or Stitching) since the gateway becomes
 the single point of contact for all your requests from the clients.
 

packages/web/docs/src/app/blog/(posts)/graphql-over-internet/page.mdx

@@ -184,7 +184,7 @@ SSE is HTTP/1. HTTP/1 powered servers are limited to
 meaning you can only have 6 concurrently active subscriptions (compared to HTTP/2 powered servers
 that are by default limited to 100+ active connection per domain).
 
-The "singe connection mode" creates a single connection to the server which is used exclusively for
+The "single connection mode" creates a single connection to the server which is used exclusively for
 streaming events and messages. Then you issue separate HTTP requests to execute operations. This
 property makes it safe for HTTP/1 environments, but also for subscription heavy apps even in HTTP/2
 environments (simply because subscriptions are typically best when really granular and this can