Apply Benjie's feedback

Author: kamilkisiela

src/pages/learn/federation.mdx

@@ -4,21 +4,21 @@ sidebarTitle: Federation
 
 import { Tabs } from 'nextra/components'
 
-# GraphQL Federation
+# GraphQL federation
 
 As applications grow more complex, traditional monolithic approaches often fall short. At scale,
 monolithic architectures can become cumbersome, brittle, and increasingly hard to test and validate.
 This has led to a rise in the adoption of new patterns like distributed systems and microservices.
-In some ways, GraphQL Federation is like microservices for GraphQL – an architectural pattern that
+In some ways, GraphQL federation is like microservices for GraphQL - an architectural pattern that
 has found particular resonance in the GraphQL ecosystem.
 
-GraphQL Federation gained widespread adoption after
+GraphQL federation gained widespread adoption after
 [Apollo GraphQL introduced Apollo Federation in 2019](https://www.apollographql.com/blog/apollo-federation-f260cf525d21).
 Their implementation has become a reference point for the GraphQL community, helping establish
 federation as a standard architectural pattern for building a distributed graph in the GraphQL
 ecosystem.
 
-With more companies and developers seeing the benefits of building a distributed graph with
+With more companies and developers seeing the benefits of building a distributed GraphQL schema with
 federation, the GraphQL ecosystem is now moving towards standardization of federation patterns. The
 GraphQL Foundation's
 [Composite Schema Working Group](https://github.com/graphql/composite-schemas-wg), which includes
@@ -50,14 +50,14 @@ Think of the "Login with Google" or "Login with Facebook" buttons you see on web
 federation in action: you can use your Google or Facebook account to log into many different
 websites, even though each company manages their own login system separately.
 
-## What Is Federated GraphQL?
+## What is federated GraphQL?
 
-GraphQL Federation applies those principles to GraphQL APIs. It enables organizations to build a
+GraphQL federation applies those principles to GraphQL APIs. It enables organizations to build a
 unified GraphQL schema from multiple independent services (most often called subgraphs), each
 responsible for its portion of the application's data graph.
 
 Consider an e-commerce platform: You might have separate teams managing products, user accounts, and
-order processing. With GraphQL Federation, each team can:
+order processing. With GraphQL federation, each team can:
 
 - Define their own GraphQL schema
 - Deploy and scale their service independently
@@ -67,7 +67,7 @@ order processing. With GraphQL Federation, each team can:
 The magic happens through a federated gateway that acts as the central coordinator, composing these
 separate schemas into a unified schema that clients can query.
 
-## How Federation Works in GraphQL
+## How federation works in GraphQL
 
 The federation process involves several key components:
 
@@ -122,7 +122,7 @@ type Order {
 
 </Tabs.Tab> </Tabs>
 
-### Schema Composition
+### Schema composition
 
 Let's break down schema composition in GraphQL federation with more detail and examples. Schema
 composition is the process where multiple subgraph schemas are combined into one unified schema.
@@ -205,58 +205,58 @@ query {
 The gateway will route parts of the query to the appropriate subgraphs, collect the results, and
 assemble them into a single response that the client can consume.
 
-## Benefits of GraphQL Federation
+## Benefits of GraphQL federation
 
-### Domain-Driven Development
+### Domain-driven development
 
 Teams can work independently on their services while contributing to a cohesive API. This autonomy
 accelerates development and reduces coordination overhead.
 
-### Service Integrity Protection
+### Service integrity protection
 
 The schema composition step verifies integration between services by ensuring that changes in
 individual subgraphs do not conflict with other subgraphs.
 
-### Scalability and Performance
+### Scalability and performance
 
 Subgraphs and services can be scaled independently based on their specific requirements. The product
 catalog might need different scaling characteristics than the order processing system.
 
-### Single, Unified API
+### Single, unified API
 
 Thanks to GraphQL, clients get a single endpoint with unified schema spanning multiple subgraphs.
 The complexity of distributed systems is hidden. The gateway ensures every query reaches its
 destination and returns with the right data.
 
-## Is GraphQL Federation Right for You?
+## Is GraphQL federation right for you?
 
-GraphQL Federation aligns naturally with Domain Driven Design (DDD) principles by allowing teams to
+GraphQL federation aligns naturally with Domain Driven Design (DDD) principles by allowing teams to
 maintain clear boundaries around their domains, while maintaining explicit integration points
 through the GraphQL schema. It is particularly valuable for organizations where multiple teams need
 to work independently on different parts of the GraphQL API, with the flexibility to use different
 technologies and programming languages.
 
-However, implementing Federation requires substantial infrastructure support, including a dedicated
+However, implementing federation requires substantial infrastructure support, including a dedicated
 team to manage the gateway, schema registry, to help connect subgraphs to the federated API and guide
 teams on best practices.
 
-Before adopting Federation, it's crucial to consider whether your organization truly needs this
+Before adopting federation, it's crucial to consider whether your organization truly needs this
 level of complexity.
 
 Meta (formerly Facebook), [where GraphQL was created](/blog/2015-09-14-graphql/), has continued to
 use a monolithic GraphQL API since 2012. However, companies like
 [Netflix](https://netflixtechblog.com/how-netflix-scales-its-api-with-graphql-federation-part-1-ae3557c187e2),
 [Expedia Group](https://youtu.be/kpeVT7J6Bsw?si=srGWsoxf3kTmneTu&t=79),
 [Volvo](https://www.apollographql.com/blog/volvo-cars-drives-into-the-future-of-online-car-shopping-with-the-supergraph),
-and [Booking](https://youtu.be/2KsP_x50tGk?si=mu-MOG-xZQSDNDjh&t=478) have adopted Federation to
+and [Booking](https://youtu.be/2KsP_x50tGk?si=mu-MOG-xZQSDNDjh&t=478) have adopted federation to
 better align with their organizational structures and microservices architecture.
 
-As you see, many industry leaders successfully federated their GraphQL APIs, proving that it works
-reliably for large-scale production applications.
+As you see, some of the world's largest industry leaders have successfully federated their GraphQL APIs, 
+proving that it works reliably for production applications at an extraordinary scale.
 
-## Getting Started with GraphQL Federation
+## Getting started with GraphQL federation
 
-If you're considering adopting GraphQL Federation, here are some steps to get started:
+If you're considering adopting GraphQL federation, here are some steps to get started:
 
 1. **Identify Service Boundaries**: Define clear boundaries between different domains in your
    application
@@ -269,6 +269,6 @@ If you're considering adopting GraphQL Federation, here are some steps to get st
 5. [**Use a Schema Registry**](/community/tools-and-libraries/?tags=schema-registry 'Discover a list of GraphQL schema registries in our Tools and Libraries page'):
    Manage schema composition and validation to ensure integrity across subgraphs
 
-When migrating from a monolithic GraphQL API to Federation, the simplest starting point is to treat
+When migrating from a monolithic to federated GraphQL API, the simplest starting point is to treat
 your existing schema as your first subgraph. From there, you can follow the steps above to gradually
 decompose your schema into smaller pieces.