better text

Author: vgrozdanic

develop-docs/backend/application-domains/options.mdx

@@ -23,8 +23,8 @@ Follow these rules when adding new options:
 The value of an option can be any pickleable value.
 
 <Alert level="info">
-  It is safe to declare and use an option in the same pull request, you don't need to
-  split them up.
+  It is safe to declare and use an option in the same pull request, you don't
+  need to split them up.
 </Alert>
 
 ## Using Options
@@ -56,8 +56,8 @@ options.set("performance.some-feature-rate", 0.01)
 ```
 
 <Alert level="info">
-  If you do not have access to the shell, you'll need to contact OPS to set the option
-  value for you.
+  If you do not have access to the shell, you'll need to contact OPS to set the
+  option value for you.
 </Alert>
 
 ### Options UI
@@ -75,7 +75,7 @@ if in_random_rollout("performance.some-feature-rate"):
     do_feature_stuff()
 ```
 
-However, be careful! Using `in_random_rollout` uses `random.random` under the hood, and will cause your feature to be enabled and disabled randomly between page requests. This may be unacceptable for user-facing features. To avoid this, you can use the `sample_modulo` helper. e.g.,
+However, be careful! `in_random_rollout` uses `random.random` under the hood, and will cause your feature to be enabled and disabled randomly between page requests. This may be unacceptable for user-facing features. To avoid this, you can use the `sample_modulo` helper. e.g.,
 
 ```python
 from sentry.utils.options import sample_modulo
@@ -124,6 +124,6 @@ options.delete("performance.some-feature-rate")
 ```
 
 <Alert level="info">
-  If you do not have access to the shell, you'll need to contact OPS to remove the option
-  for you.
+  If you do not have access to the shell, you'll need to contact OPS to remove
+  the option for you.
 </Alert>