update formatting

Author: mdbirnstiehl

solutions/observability/apps/errors-2.md

@@ -6,11 +6,6 @@ mapped_urls:
 
 # Errors [apm-errors]
 
-::::{tip}
-[Errors](/solutions/observability/apps/errors.md) are groups of exceptions with a similar exception or log message.
-::::
-
-
 *Errors* are groups of exceptions with a similar exception or log message. The **Errors** overview provides a high-level view of the exceptions that APM agents catch, or that users manually report with APM agent APIs. Like errors are grouped together to make it easy to quickly see which errors are affecting your services, and to take actions to rectify them.
 
 A service returning a 5xx code from a request handler, controller, etc., will not create an exception that an APM agent can catch, and will therefore not show up in this view.

solutions/observability/apps/logs.md

@@ -24,6 +24,9 @@ Logs displayed on this page are filtered on `service.name`
 ::::
 
 ## Integrate with logging frameworks [apm-logs-correlation]
+```{applies_to}
+stack: all
+```
 
 Elastic APM integrates with popular logging frameworks, making it easy to correlate your logs and traces. This enables you to:
 

solutions/observability/apps/mobile-service-overview.md

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-mobile-service-overview.html
+applies_to:
+  stack: all
 ---
 
 # Mobile service overview [apm-mobile-service-overview]
@@ -27,6 +29,7 @@ Understand the impact of slow application load times and variations in applicati
 
 Note: due to the way crash rate is calculated (crashes per session) it is possible to have greater than 100% rate, due to fact that a session may contain multiple crashes.
 
+
 :::{image} ../../../images/observability-mobile-location.png
 :alt: mobile service overview centered on location map
 :class: screenshot
@@ -37,6 +40,7 @@ Note: due to the way crash rate is calculated (crashes per session) it is possib
 
 Optimize your end-user experience and your application QA strategy based on your most used device models and operating system versions.
 
+
 :::{image} ../../../images/observability-mobile-most-used.png
 :alt: mobile service overview showing most used devices
 :class: screenshot
@@ -51,6 +55,7 @@ The **Transactions** table displays a list of *transaction groups* for the selec
 
 By default, transaction groups are sorted by *Impact* to show the most used and slowest endpoints in your service. If there is a particular endpoint you are interested in, click **View transactions** to view a list of similar transactions on the [transactions overview](transactions-2.md) page.
 
+
 :::{image} ../../../images/observability-traffic-transactions.png
 :alt: Traffic and transactions
 :class: screenshot
@@ -73,6 +78,7 @@ If there is no HTTP status, both transactions and spans are considered successfu
 
 The **Dependencies** table displays a list of downstream services or external connections relevant to the service at the selected time range. The table displays latency, throughput, failed transaction rate, and the impact of each dependency. By default, dependencies are sorted by *Impact* to show the most used and the slowest dependency. If there is a particular dependency you are interested in, click **[View dependencies](dependencies.md)** to learn more about it.
 
+
 ::::{note}
 Displaying dependencies for services instrumented with the Real User Monitoring (RUM) agent requires an agent version ≥ v5.6.3.
 ::::
@@ -83,6 +89,7 @@ Displaying dependencies for services instrumented with the Real User Monitoring
 :class: screenshot
 :::
 
+
 :::{image} ../../../images/observability-mobile-tp.png
 :alt: mobile service overview showing latency
 :class: screenshot