diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx
index 237704c5c3036..502a940098737 100644
--- a/docs/platforms/python/configuration/options.mdx
+++ b/docs/platforms/python/configuration/options.mdx
@@ -119,6 +119,8 @@ When enabled, the SDK will capture a snapshot of local variables to send with th
 
 When capturing errors, Sentry stack traces typically only include frames that start the moment an error occurs. But if the `add_full_stack` option is enabled (set to `True`), all frames from the start of execution will be included in the stack trace sent to Sentry.
 
+Note: Grouping of issues in Sentry is based on stack traces. If you change this value in an existing Sentry setup new groups for already known errors will be created.
+
 </SdkOption>
 
 <SdkOption name="max_stack_frames" type='int' defaultValue='100'>
@@ -400,7 +402,7 @@ sentry_sdk.init(custom_repr=custom_repr)
 
 <SdkOption name="profile_lifecycle" type='str' defaultValue='manual'>
 
-Determines how the profiler will run, accepts two values: `manual` or `trace`. 
+Determines how the profiler will run, accepts two values: `manual` or `trace`.
 
 In `manual` mode, you control when the profiler collects data by explicitly calling `sentry_sdk.profiler.start_profiler` and `sentry_sdk.profiler.stop_profiler`. You are entirely in control of when the profiler runs.