Merge pull request #13861 from ammartens/patch-2

Update intro-synthetic-monitoring.mdx

src/content/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx

@@ -329,7 +329,7 @@ Synthetic monitoring includes the following features:
 After you've set up some synthetic monitors, we recommend these next steps:
 
 * Check how your synthetics data turns your aggregated results into [metrics](/docs/synthetics/new-relic-synthetics/dashboards/synthetics-overview-dashboard), allowing you to see patterns and identify causes of poor performance. 
-* See how[each and every monitor result](/docs/synthetics/new-relic-synthetics/using-monitors/viewing-monitor-results#understanding)is broken down.
+* See how [each and every monitor result](/docs/synthetics/new-relic-synthetics/using-monitors/viewing-monitor-results#understanding) is broken down.
 * Want to supplement your synthetics data with real-user data? Check out our [Improve your website's performance](/docs/journey-performance/improve-website-performance) tutorial.
 * Create [alerts that notify you](/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics) if your website or API endpoint is inaccessible. You can even expand your geographical coverage or monitor internal websites by creating [private locations](/docs/synthetics/new-relic-synthetics/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations).
 * You can also [query your monitor results](/docs/using-new-relic/data/understand-data/query-new-relic-data) for a closer look. New Relic retains monitor results for thirteen months, ensuring you can compare usage year over year.