chore(): add disclaimer for boostrapping feature flags behavior post-init

contents/docs/feature-flags/bootstrapping.mdx

@@ -128,6 +128,25 @@ export function MyApp() {
 
 </MultiLanguage>
 
+
+## Overriding feature flags 
+
+Bootstrapped feature flag values are temporary and are disregarded after PostHog fetches flag values. If you are trying to override feature flag values in a persistent manner, some PostHog SDKs support overriding flags:
+
+
+<MultiLanguage selector="tabs">
+
+```node
+posthog.overrideFeatureFlag('my-feature-flag', true)
+```
+
+```js-web
+posthog.feature_flags.override({'my-feature-flag': 'variant-1', 'other-feature': true})
+```
+
+</MultiLanguage>
+
+
 ## Examples
 
 - [How to bootstrap feature flags in React and Express](/tutorials/bootstrap-feature-flags-react)

contents/docs/feature-flags/snippets/bootstrapping-intro.mdx

@@ -1,3 +1,3 @@
 Since there is a delay between initializing PostHog and fetching feature flags, feature flags are not always available immediately. This makes them unusable if you want to do something like redirecting a user to a different page based on a feature flag.
 
-To have your feature flags available immediately, you can initialize PostHog with precomputed values until it has had a chance to fetch them. This is called bootstrapping.
+To have your feature flags available immediately, you can initialize PostHog with precomputed values until it has had a chance to fetch them. This is called bootstrapping. After the SDK fetches feature flags from PostHog, it will use those flag values instead of bootstrapped ones.