Refine language for clarity in blog post (#7038)

Author: n1ru4l

packages/web/docs/src/app/blog/(posts)/public-graphql-schema-federation-contracts/page.mdx

@@ -12,7 +12,7 @@ Many teams start with a **single GraphQL monolith** powering their applications.
 arises to expose parts of that schema publicly - whether for partners, customers, or other external
 integrations.
 
-But here’s the problem:
+But then you might realize the following:
 
 Your internal schema wasn’t designed for public consumption. It likely contains inconsistent naming,
 experimental fields, and sensitive operations you don’t want outsiders touching.
@@ -223,6 +223,4 @@ one, while only exposing the parts you want today, and leaving the door open for
 This approach provides a clean, incremental path to offering a public GraphQL API without
 compromising the flexibility of your internal schema.
 
-[Learn more on schema contracts with Hive
-Console]([Learn more in the Hive Console documentation](https://the-guild.dev/graphql/hive/docs/schema-registry/contracts).
-).
+[Learn more on schema contracts with Hive Console](https://the-guild.dev/graphql/hive/docs/schema-registry/contracts).