diff --git a/docs/product/releases/health/index.mdx b/docs/product/releases/health/index.mdx
index bb3101677f369..c58e48edf7983 100644
--- a/docs/product/releases/health/index.mdx
+++ b/docs/product/releases/health/index.mdx
@@ -30,45 +30,25 @@ Sentry distinguishes between two kinds of sessions:
### User-Mode/Application-Mode Sessions
-
+A user- or application-mode session begins with the start of the application.
+Or, it begins with bringing the already started application back from
+background to the foreground. In this context, a user is defined by one or
+more of the following: a unique ID or UUID, username, or email.
--
- A user- or application-mode session begins with the start of the application.
- Or, it begins with bringing the already started application back from
- background to the foreground. In this context, a user is defined by one or
- more of the following: a unique ID or UUID, username, or email.
-
-
-
-
--
- This type of session ends with the closing of the application or with the
- application being sent to the background. If the application is in the
- background for less than 30 seconds, we do not start the session again.
- Applications that are active even on the background (for example, a music
- player) should track the sessions manually for the background process.
-
-
-
+This type of session ends with the closing of the application or with the
+application being sent to the background. If the application is in the
+background for less than 30 seconds, we do not start the session again.
+Applications that are active even on the background (for example, a music
+player) should track the sessions manually for the background process.
### Server-Mode/Request-Mode Sessions
-
-
--
- Server- or request-mode sessions roughly correspond to HTTP requests or RPC
- calls in a server setting. A session is started when the server receives a
- request, and terminates when the server sends a response.
-
-
-
-
--
- These are typically high in volume since each session corresponds to a single
- request.
-
+Server or request-mode sessions roughly correspond to HTTP requests or RPC
+calls in a server setting. A session is started when the server receives a
+request, and terminates when the server sends a response.
-
+These are typically high in volume since each session corresponds to a single
+request.
Sessions, whether application-mode or request-mode, are submitted to Sentry so you can track the usage and adoption of your application. When a user of your application experiences a crash, error, or abnormal exit, the session will be flagged accordingly, and Sentry calculates derived metrics. The metrics include data such as the number of users that didn't experience a crash in the specified time range.