diff --git a/website/docs/topics/feature-flags/feature-flag-best-practices.md b/website/docs/topics/feature-flags/feature-flag-best-practices.md
index 69ac20ee72..4648a3f7f3 100644
--- a/website/docs/topics/feature-flags/feature-flag-best-practices.md
+++ b/website/docs/topics/feature-flags/feature-flag-best-practices.md
@@ -1,6 +1,5 @@
 ---
-title: "Feature flags: Best practices for building and scaling"
-description: "Discover 11 essential principles for building robust, large-scale feature flag systems."
+title: "11 Principles for building and scaling feature flag systems"
 toc_max_heading_level: 2
 ---
 
@@ -194,4 +193,4 @@ To ensure a good developer experience, you should provide the following:
 - **Usage metrics**: Provide aggregated insights into feature flag usage, helping developers confirm that everything is working as expected.
 - **Documentation and training**: Offer clear, comprehensive documentation for the API, UI, and SDKs, with easy-to-follow examples. This simplifies onboarding for new developers and supports continuous training, ensuring the effective use of the feature flagging system.
 
-Thank you for reading. Our motivation for writing these principles is to share what we've learned building a large-scale feature flag solution with other architects and engineers solving similar challenges. Unleash is open-source, and so are these principles. Have something to contribute? [Open a PR](https://github.com/Unleash/unleash/pulls) or [discussion](https://github.com/orgs/Unleash/discussions) on our GitHub.
\ No newline at end of file
+Thank you for reading. Our motivation for writing these principles is to share what we've learned building a large-scale feature flag solution with other architects and engineers solving similar challenges. Unleash is open-source, and so are these principles. Have something to contribute? [Open a PR](https://github.com/Unleash/unleash/pulls) or [discussion](https://github.com/orgs/Unleash/discussions) on our GitHub.