address feedback

Author: Zylphrex

docs/platforms/python/profiling/index.mdx

@@ -18,7 +18,7 @@ Continuous profiling is available starting in SDK version `2.24.1`.
 
 </Alert>
 
-Continuous rofiling supports two modes - `manual` and `trace`. The two modes are mutually exclusive, and cannot be used at the same time.
+Continuous profiling supports two modes - `manual` and `trace`. The two modes are mutually exclusive, and cannot be used at the same time.
 
 In `manual` mode, the profiling data collection can be managed via calls to `sentry_sdk.profiler.start_profiler` and `sentry_sdk.profiler.stop_profiler`. You are entirely in the in control of when the profiler runs.
 
@@ -70,13 +70,13 @@ sentry_sdk.profiler.stop_profiler()
 
 ### Managing profile sampling rates
 
-Sentry SDK supports an additional `profile_session_sample_rate` that will enable or disable profiling for the entire session. This can be used if you want to control session sampling rates at the service level as the sampling decision is evaluated only once at SDK init.
+Sentry SDK supports an additional `profile_session_sample_rate` that must be set to a non-zero value to enable continuous profiling. This can be used to control session sampling rates at the service level as the sampling decision is evaluated only once at SDK init.
 
 This is useful for cases where you deploy your service many times, but would only like a subset of those services to be profiled.
 
 ### Upgrading from Older SDK versions
 
-Continuous profiling was experimental in SDK versions prior to `2.24.1`. Learn how to upgrade <PlatformLink to="/profiling/troubleshooting/#continuous-profiling">here</PlatformLink>.
+Continuous profiling was experimental in SDK versions prior to `2.24.1` and will be deprecated. Data sent by these older versions will not be accepted in the near future. Learn how to upgrade <PlatformLink to="/profiling/troubleshooting/#continuous-profiling">here</PlatformLink>.
 
 ## Enable Transaction Based Profiling