feat: Remove def list syntax (#11238)

Author: chargome

develop-docs/sdk/envelopes.mdx

@@ -119,19 +119,19 @@ Envelopes can have a number of headers which are valid in all situations:
 
 `dsn`
 
-: *String, recommended.* An envelope can be self authenticated.  This means that
+**String, recommended.** An envelope can be self authenticated.  This means that
   the envelope has all the information necessary to be sent to sentry.  In this
   case the full DSN must be stored in this key.
 
 `sdk`
 
-: *Object, recommended.* This can carry the same payload as the <Link to="/sdk/event-payloads/sdk/">`sdk` interface</Link>
+**Object, recommended.** This can carry the same payload as the <Link to="/sdk/event-payloads/sdk/">`sdk` interface</Link>
   in the event payload but can be carried for all events. This means that SDK
   information can be carried for minidumps, session data and other submissions.
 
 `sent_at`
 
-: *String, recommended.* The timestamp when the event was sent from the SDK as string in
+**String, recommended.** The timestamp when the event was sent from the SDK as string in
   [RFC 3339](https://tools.ietf.org/html/rfc3339) format. Used for clock drift
   correction of the event timestamp. The time zone must be UTC.
 
@@ -153,22 +153,22 @@ The timestamp can be generated by any of the following (for example):
 
 JavaScript
 
-: `new Date().toISOString()`
+`new Date().toISOString()`
 
 Python
 
-: `datetime.now(timezone.utc).isoformat()`<br />  
+`datetime.now(timezone.utc).isoformat()`<br />  
   *Don't use `datetime.utcnow()`, as it will omit the time zone.*
 
 .NET
 
-: `DateTime.UtcNow.ToString("o", CultureInfo.InvariantCulture)`  
+`DateTime.UtcNow.ToString("o", CultureInfo.InvariantCulture)`  
   or  
   `DateTimeOffset.UtcNow.ToString("o", CultureInfo.InvariantCulture)`
 
 Java
 
-: `Instant.now().toString()`
+`Instant.now().toString()`
 
 *Also note that the `sent_at` header replaces the `sentry_timestamp` key previously set in authorization headers,
 which has now been fully deprecated.  You should only send `sent_at`, and not `sentry_timestamp`.*
@@ -190,7 +190,7 @@ There are two generic headers for every Item:
 
 `length`
 
-: *int, recommended.* The length of the payload in bytes. If no `length` is
+**int, recommended.** The length of the payload in bytes. If no `length` is
   specified, the payload implicitly goes to the next newline. For payloads
   containing newline characters, the `length` must be specified.
 
@@ -390,7 +390,7 @@ file. It is always associated to an event or transaction.
 
 `attachment_type`
 
-: *String, optional.* The special type of this attachment. Possible values are:
+**String, optional.** The special type of this attachment. Possible values are:
 
   - **`event.attachment` (default)**: A standard attachment without special
     meaning.
@@ -406,7 +406,7 @@ file. It is always associated to an event or transaction.
 
 `content_type`
 
-: *String, optional.* The content type of the attachment payload. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
+**String, optional.** The content type of the attachment payload. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
 
 ### Session
 
@@ -491,15 +491,15 @@ The item contains a user feedback / user report JSON payload:
 
 `email`
 
-: *String, recommended.* The email of the user.
+**String, recommended.** The email of the user.
 
 `name`
 
-: *String, recommended.* The name of the user.
+**String, recommended.** The name of the user.
 
 `comments`
 
-: *String, recommended.* Comments of the user about what happened. 
+**String, recommended.** Comments of the user about what happened. 
 
 **Constraints:**
 
@@ -577,7 +577,7 @@ details.
 
 `length`
 
-: **integer, required.** The size of the Replay recording payload
+**integer, required.** The size of the Replay recording payload
 
 ### Profile
 

develop-docs/sdk/event-payloads/contexts.mdx

@@ -396,7 +396,7 @@ _Optional_. A list of visible UI screens at the current point in time.
 
 `start_type`
 
-: _Optional_. The way the OS started the app. For example, `cold`, `warm`, `cold.prewarmed`, or `warm.prewarmed`.
+_Optional_. The way the OS started the app. For example, `cold`, `warm`, `cold.prewarmed`, or `warm.prewarmed`.
 
 ## Browser Context
 
@@ -824,13 +824,13 @@ The required field is `package` which should contain the package or framework wh
 
 `package`
 
-: **Required.** The package or framework where a missing instrumentation was detected.
+**Required.** The package or framework where a missing instrumentation was detected.
 
 - Example: `express`
 
 `javascript.is_cjs`
 
-: _Optional_. Boolean that indicates if the context was added from a commonjs module.
+_Optional_. Boolean that indicates if the context was added from a commonjs module.
 
 - Example: `true`
 

develop-docs/sdk/event-payloads/replay-recording.mdx

@@ -8,7 +8,7 @@ The recording event is an object with the following required properties:
 
 `type`
 
-: **EventTypeEnum** The `type` describes what type of event it is. See the enum below.
+**EventTypeEnum** The `type` describes what type of event it is. See the enum below.
 
 ```
 EventTypeEnum {
@@ -24,23 +24,23 @@ EventTypeEnum {
 
 `timestamp`
 
-: **float** The timestamp (in milliseconds) at which the event occurs
+**float** The timestamp (in milliseconds) at which the event occurs
 
 `data`
 
-: **unknown** `data` schema is dependent on the `type`. View the [base types](https://github.com/rrweb-io/rrweb/blob/master/packages/types/src/index.ts) or Sentry's [custom types](https://github.com/getsentry/sentry-javascript/blob/master/packages/replay-internal/src/types/replayFrame.ts).
+**unknown** `data` schema is dependent on the `type`. View the [base types](https://github.com/rrweb-io/rrweb/blob/master/packages/types/src/index.ts) or Sentry's [custom types](https://github.com/getsentry/sentry-javascript/blob/master/packages/replay-internal/src/types/replayFrame.ts).
 
 ## Custom Events
 
 Sentry custom events augment the replay with additional context in order to help the user debug issues. Custom events have the following format for the `data` property of the event:
 
 `tag`
 
-: **string** The tag is used to describe the "type" of custom event. This will determine how the event gets used in the UI.
+**string** The tag is used to describe the "type" of custom event. This will determine how the event gets used in the UI.
 
 `payload`
 
-: **object** The `payload` is similar to the upper level `data` attribute, whose schema is dependent on the `tag`.
+**object** The `payload` is similar to the upper level `data` attribute, whose schema is dependent on the `tag`.
 
 In addition to the TypeScript references linked above, the following sections will describe the expected `payload` for custom events.
 

develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx

@@ -82,13 +82,13 @@ in the same envelope as the associated transaction.
 
 `debug_meta`
 
-: *Object, required on native platforms.* This carries the same payload as the <Link
+*Object, required on native platforms.* This carries the same payload as the <Link
 to="/sdk/event-payloads/sdk/">`debug_meta` interface</Link>. It is required to
 have it for native platforms in order to symbolicate. For non-native platforms, you can omit this.
 
 `device`
 
-: *Object, required.* This contains several fields that describe the device the
+*Object, required.* This contains several fields that describe the device the
 profiler is running on.
 
 It can have the following attributes:
@@ -112,17 +112,17 @@ It can have the following attributes:
 
 `environment`
 
-: *String, recommended.* The environment name, such as `production` or
+*String, recommended.* The environment name, such as `production` or
 `staging`. The default value is `production`.
 
 `event_id`
 
-: *String, required.* Hexadecimal string representing a uuid4 value. The length
+*String, required.* Hexadecimal string representing a uuid4 value. The length
 must be exactly 32 characters. Dashes and uppercase letters are not allowed.
 
 `measurements`
 
-: *Object, optional.* This field contains various metrics measured during the profile collection.
+*Object, optional.* This field contains various metrics measured during the profile collection.
 
 A measurement is a collection of measurement values and a unit for those values.
 It will only be shown in the UI if it's been integrated. Right now, we only
@@ -158,7 +158,7 @@ These are the values accepted for `unit`:
 
 `os`
 
-: *Object, required.* Contains information about the OS.
+*Object, required.* Contains information about the OS.
 
 
 It can have the following attributes:
@@ -178,7 +178,7 @@ It can have the following attributes:
 
 `platform`
 
-: *String, required.* This value represents the platform the SDK is submitting
+*String, required.* This value represents the platform the SDK is submitting
 from.
 
 Acceptable values are:
@@ -189,20 +189,20 @@ Acceptable values are:
 
 `profile`
 
-: *Object, required.* It contains all the raw data collected when profiling. See
+*Object, required.* It contains all the raw data collected when profiling. See
 [profile data](#profile-data).
 
 `release`
 
-: *String, required.* The release version of the application.
+*String, required.* The release version of the application.
 
 **Release versions must be unique across all projects in your organization**.
 This value can be the git SHA for the given project, or a product identifier
 with a semantic version (suggested format `[email protected]`).
 
 `runtime`
 
-: *Object, optional.* Contains information about the runtime. Usually only used
+*Object, optional.* Contains information about the runtime. Usually only used
 for platforms allowing several runtimes.
 
 It can have the following attributes:
@@ -220,7 +220,7 @@ It can have the following attributes:
 
 `timestamp`
 
-: *String, recommended.* The timestamp when the profile was captured by the SDK
+*String, recommended.* The timestamp when the profile was captured by the SDK
 as [RFC 3339](https://tools.ietf.org/html/rfc3339) format. This is meant to be
 the anchor for all relative timestamps captured for the profile.
 
@@ -235,7 +235,7 @@ later on.
 
 `transaction`
 
-: *Object, required.* Contains information about the transaction it is
+*Object, required.* Contains information about the transaction it is
 associated with.
 
 It can have the following attributes:
@@ -249,7 +249,7 @@ It can have the following attributes:
 
 `version`
 
-: *String, required.* Represents the version of the Sample format.
+*String, required.* Represents the version of the Sample format.
 
 Acceptable values are:
 - `"1"`
@@ -304,7 +304,7 @@ milliseconds.
 
 `samples`
 
-: *List, required* Contains a list of sample object captured during execution.
+*List, required* Contains a list of sample object captured during execution.
 Each sample can contain the following attributes:
 
 - `elapsed_since_start_ns`: *String, required.* Contains the relative timestamp
@@ -324,7 +324,7 @@ Each sample can contain the following attributes:
 
 `stacks`
 
-: *List, required*. Contains a list of frame indices forming a stack trace.
+*List, required*. Contains a list of frame indices forming a stack trace.
 
 Frames in a stack should be ordered from leaf to root. It means your main frame
 should be at the end of the list.
@@ -334,7 +334,7 @@ the same `stack_id` for each sample that needs it.
 
 `frames`
 
-: *List, required*. Contains a list of frame objects (see [Frame
+*List, required*. Contains a list of frame objects (see [Frame
 Attributes](/sdk/event-payloads/stacktrace/#frame-attributes)).
 
 Each object should contain at least a `filename`, `function` or
@@ -359,7 +359,7 @@ Some attributes are not used at the moment:
 
 `thread_metadata`
 
-: *Object, required.* Contains an object with a field for each thread ID
+*Object, required.* Contains an object with a field for each thread ID
 detected during runtime.
 
 This object can contain these attributes: