feedback

Author: chargome

docs/contributing/pages/components.mdx

@@ -382,15 +382,19 @@ If you're writing product feature specific docs, you can specify markers within
 
 ````markdown
 ```go
-  // ___product_option_start___ performance
+  // ___PRODUCT_OPTION_START___ performance
   // your code here
-  // ___product_option_end___ performance
+  // ___PRODUCT_OPTION_END___ performance
 ```
 ````
 
-the general syntax is `// ___product_option_start___ feature` where `feature` is the feature id (e.g. `performance`, `profiling` or `session-replay`).
+the syntax uses the standard comment style of the programming language you're documenting. For example:
+
+- TypeScript/JavaScript: `// ___PRODUCT_OPTION_START___ feature`
+- Python: `# ___PRODUCT_OPTION_START___ feature`
+
+where `feature` is the feature id (e.g. `performance`, `profiling` or `session-replay`).
 
-You can specify multiple features by separating them with a comma:
 
 The range visibility will be controlled by the `OnboardingOptionButtons` component:
 
@@ -439,13 +443,13 @@ import (
 // To initialize Sentry's handler, you need to initialize Sentry itself beforehand
 if err := sentry.Init(sentry.ClientOptions{
 	Dsn: "___PUBLIC_DSN___",
-  // ___product_option_start___ performance
+  // ___PRODUCT_OPTION_START___ performance
 	EnableTracing: true,
 	// Set TracesSampleRate to 1.0 to capture 100%
 	// of transactions for performance monitoring.
 	// We recommend adjusting this value in production,
 	TracesSampleRate: 1.0,
-  // ___product_option_end___ performance
+  // ___PRODUCT_OPTION_END___ performance
   // Adds request headers and IP for users,
   // visit: https://docs.sentry.io/platforms/go/data-management/data-collected/ for more info
   SendDefaultPII: true,