updates based on PR feedback

Author: Shannon Anahata

docs/platforms/python/tracing/configure-sampling/index.mdx

@@ -4,13 +4,16 @@ description: "Learn how to configure sampling in your app."
 sidebar_order: 30
 ---
 
-Sentry's tracing functionality helps you monitor application performance by capturing distributed traces, attaching attributes, and span performance across your application. However, capturing traces for every transaction can generate significant volumes of data. Sampling allows you to control the amount of spans that are sent to Sentry from your application.
+Sentry's tracing functionality helps you monitor application performance by capturing distributed traces, attaching attributes, and adding span performance metrics across your application. However, capturing traces for every transaction can generate significant volumes of data. Sampling allows you to control the amount of spans that are sent to Sentry from your application.
+
+Effective sampling is key to getting the most value from Sentry's performance monitoring while minimizing overhead. The `traces_sampler` function gives you precise control over which transactions to record, allowing you to focus on the most important parts of your application.
 
 ## Sampling Configuration Options
 
 The Python SDK provides two main options for controlling the sampling rate:
 
 1. Uniform Sample Rate (`traces_sample_rate`)
+
 This option sets a fixed percentage of transactions to be captured:
 
 <PlatformContent includePath="/performance/traces-sample-rate" />
@@ -196,7 +199,7 @@ sentry_sdk.init(
 
 ## The Sampling Context Object
 
-When the `traces_sampler` function is called, it receives a `sampling_context` object with valuable information to help make sampling decisions:
+When the `traces_sampler` function is called, the Sentry SDK  passes a `sampling_context` object with information from the relevant span to help make sampling decisions:
 
 ```python
 {
@@ -282,8 +285,4 @@ message = {
 queue.send(json.dumps(message))
 ```
 
-## Conclusion
-
-Effective sampling is key to getting the most value from Sentry's performance monitoring while minimizing overhead. The `traces_sampler` function gives you precise control over which transactions to record, allowing you to focus on the most important parts of your application.
-
 By implementing a thoughtful sampling strategy, you'll get the performance insights you need without overwhelming your systems or your Sentry quota.

docs/platforms/python/tracing/instrumentation/index.mdx

@@ -26,9 +26,13 @@ In Python, spans are typically created using a context manager, which automatica
 ```python
 import sentry_sdk
 
+# Start a span for a task
 with sentry_sdk.start_span(op="task", name="Create User"):
     # Your code here
     # The span will automatically end when exiting this block
+    user = create_user(email="[email protected]")
+    send_welcome_email(user)
+    # The span automatically ends here when the 'with' block exits
 ```
 
 Alternatively, you can create spans manually and control their lifecycle yourself, which gives you more flexibility but also more responsibility:
@@ -41,6 +45,8 @@ try:
     # Your code here
 finally:
     # Remember to always end your spans
+    # If you don't call span.finish(), the span will remain open indefinitely,
+    # causing memory leaks and incorrect timing data
     span.finish()
 ```
 
@@ -177,7 +183,7 @@ See <PlatformLink to="/tracing/distributed-tracing/">Distributed Tracing</Platfo
 
 ### Adding Span Attributes
 
-You can capture additional context with span attributes. These can be key-value pairs of various Python types:
+Span attributes customize information you can get through tracing. This information can be found in the traces views in Sentry, once you drill into a span. You can capture additional context with span attributes. These can be key-value pairs of various Python types.
 
 ```python
 import sentry_sdk

redirects.js

@@ -988,12 +988,16 @@ const userDocsRedirects = [
     destination: '/platforms/kotlin/guides/kotlin-multiplatform/:path*',
   },
   {
-    source: '/platforms/python/:productfeature/troubleshooting/:path*',
-    destination: '/platforms/python/troubleshooting/:path*',
-  },
-  {
-    source: '/platforms/python/guides/:guide/troubleshooting/:path*',
-    destination: '/platforms/python/troubleshooting/:path*',
+  source: '/platforms/python/:productfeature/troubleshooting/:path*',
+  destination: '/platforms/python/troubleshooting/:path*',
+  }, 
+   {
+   source: '/platforms/python/guides/:guide/troubleshooting/:path*',
+   destination: '/platforms/python/troubleshooting/:path*',
+   }, 
+   {
+    source: '/platforms/python/tracing/trace-propagation/:path*',
+    destination: '/platforms/python/tracing/distributed-tracing/:path*',
   },
   {
     source: '/platforms/ruby/guides/:guide/:productfeature/troubleshooting/:path*',