From 496c3328e0c61b439abc6e4758c36501612c74fa Mon Sep 17 00:00:00 2001 From: melindafekete Date: Tue, 15 Jul 2025 18:33:13 +0200 Subject: [PATCH] Fix typo --- .../use-cases/manage-feature-flags-in-code.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/feature-flag-tutorials/use-cases/manage-feature-flags-in-code.mdx b/website/docs/feature-flag-tutorials/use-cases/manage-feature-flags-in-code.mdx index 1d9d30878e..c32b80ceff 100644 --- a/website/docs/feature-flag-tutorials/use-cases/manage-feature-flags-in-code.mdx +++ b/website/docs/feature-flag-tutorials/use-cases/manage-feature-flags-in-code.mdx @@ -100,7 +100,7 @@ How and where you check a flag's state is one of the most important architectura Directly calling the Unleash SDK's `unleash.isEnabled()` throughout your codebase tightly couples your application to the specific SDK implementation. -Instead, we recommend implementing an abstraction layer, often called a "wrapper," to encapsulate all interactions with the Unleash SDK. This service becomes the single entry point for all feature flag checks in your application. +Instead, we recommend implementing an abstraction layer, often called a "wrapper", to encapsulate all interactions with the Unleash SDK. This service becomes the single entry point for all feature flag checks in your application. ```typescript // src/services/feature-service.ts