feat(content): edited some content and added doc tiles

src/content/docs/tutorial-app-performance/guide-to-monitoring-core-web-vitals.mdx

@@ -202,6 +202,10 @@ Let's say your organization recently updated images on the site’s home page on
     </Collapser>
 </CollapserGroup>
 
+## Get more context with session traces [#session-traces]
+
+
+
 ## What's next? [#next]
 
 This tutorial covered some actions you can take with your core web vitals. You have some options for your next steps.

src/content/docs/tutorial-app-performance/performance-benchmarks.mdx

@@ -8,15 +8,12 @@ redirects:
 
 import sonicSliUiOverview from 'images/sonic_screenshot-full_sli-ui-overview.webp'
 
-import tutorialSLpage from 'images/tutorial_screenshot-cropped_sl-ui-overview.webp'
-
-Your system architecture is made up of hosts, apps, and services that affect and depend on each other. If one part of your architecture underperforms, it can create a cascading chain of events that could lead to critical system outages. Service levels, however, let you apply thresholds to these discrete parts. These thresholds apply a measurement to service behavior, so when performance exceeds or falls below that threshold, you're alerted. Here's how it works: 
+Your system architecture is made up of hosts, apps, and services that affect and depend on each other. If one part of your architecture underperforms, it can create a cascading chain of events that could lead to critical system outages. Service levels, however, let you apply thresholds that make keeping track of your system easier. If performance on a service exceeds or falls below a given threshold, you receive an alert. Here are the layers to service levels: 
 
 * A service level is made up of service level objectives (SLOs). SLOs are goals that represent how you expect your services to behave. 
 * Your SLOs are defined by service level indicators (SLIs). SLIs are key measurements and metrics that determine service availability.
 * On top of these objectives an indicators are alerts. These notify you when your services fail to meet your SLOs. 
 
-
 ## Objectives [#objectives]
 
 This tutorial walks you through creating performance benchmarks with service levels. By the end of the tutorial, you'll have these tasks completed:
@@ -300,9 +297,11 @@ Defining and managing your service levels following the steps below provides the
 
 ## Next steps
 
-Congratulations! You've completed our journey on how to use New Relic to improve your site's performance! Ready to learn more about New Relic features? See our introductory docs on some of our most impactful features below:
+Congratulations! You've completed our journey on how to use New Relic to improve your site's performance! Ready to learn more about using New Relic like a pro? See some of our other tutorials:
+
+<DocTiles>
+    <DocTile title='My app is slow' number='1' path="/docs/tutorial-app-slow/root-causes/">Is your app slow? Check out our tutorial to diagnose and resolve app slowness.</DocTile>
+    <DocTile title='Prepare for peak demand events' number='2' path="/docs/tutorial-peak-demand/get-started/">Prepare your teams for a game day so your app stays live when demand peaks.</DocTile>    
+    <DocTile title='Create alerts' number='3' path="/docs/tutorial-create-alerts"> Stay in the loop about your system's health by creating high quality alerts.</DocTile>
+</DocTiles>
 
-* [Introduction to browser monitoring](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring)
-* [Introduction to alerts](/docs/alerts-applied-intelligence/overview/)
-* [Introduction to synthetics](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring/)
-* [Intro to service level management](/docs/service-level-management/intro-slm/)