Suggestions for federation links (#4436)

Author: Urigo

website/pages/docs/scaling-graphql.mdx

@@ -101,11 +101,10 @@ GraphQL.js, you'll need to:
 - Output a schema that conforms to a federation-compliant format
 
 Most federation tooling today is based on 
-[Apollo Federation](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/federation). 
+[Apollo Federation](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/federation) and [here you can find a list of Apollo Federation compatible gateways](https://the-guild.dev/graphql/hive/federation-gateway-audit).
+
 However, other approaches exist:
 
-- [GraphQL Mesh](https://the-guild.dev/graphql/mesh) allows federation-like composition across 
-services using plugins.
 - Custom gateways and tooling can be implemented using GraphQL.js or other frameworks.
 - The [GraphQL Composite Schemas WG](https://github.com/graphql/composite-schemas-wg/) (formed of Apollo, ChilliCream, The Guild, Netflix, Graphile and many more) are working on an open specification for the next generation of GraphQL Federation
 
@@ -158,4 +157,4 @@ Make sure your team has the operational maturity to support the tooling and patt
 - Define ownership boundaries. Federation is most useful when teams need clear control over parts of
 the schema. Without strong ownership models, a federated graph can become harder to manage.
 - Consider alternatives. Not all use cases need stitching or federation. Sometimes, versioning, modular
-schema design, or schema delegation patterns within a monolith are sufficient.
+schema design, or schema delegation patterns within a monolith are sufficient.