newrelic · bradleycamacho · Jul 22, 2023 · Jun 29, 2023 · Jun 29, 2023 · Jul 18, 2023
@@ -8,7 +8,6 @@ reviewers:
   - homelessbirds
   - nbaenam
   - a-sassman
-  - stumblefiend
   - zuluecho9
   - ally-sassman
   - akristen

diff --git a/src/announcements/docs-q2-survey.mdx b/src/announcements/docs-q2-survey.mdx
@@ -0,0 +1,10 @@
+---
+startDate: 2023-07-21
+endDate: 2023-07-28
+---
+
+# Tell us how we're doing!
+
+Got feedback? Let us know so we can make our content more relevant for users like you.
+
+[Share your thoughts in our short, 3 minute survey.](https://docs.google.com/forms/d/e/1FAIpQLSfOXaw1-YKkDRMUoLSpmHEo1y2NJa9BSCbM47k3Hw9h9NZi3g/viewform?usp=sf_link)
diff --git a/src/content/docs/apm/agents/java-agent/troubleshooting/no-data-appears-java.mdx b/src/content/docs/apm/agents/java-agent/troubleshooting/no-data-appears-java.mdx
@@ -46,7 +46,7 @@ After sending a request to your web application, data should appear in the APM U
 
       * If you see a `-javaagent` argument: The issue is either in agent startup, or the agent is unable to communicate through your firewall to [our collector's IP range](/docs/using-new-relic/cross-product-functions/install-configure/networks).
       * If you don't see a `-javaagent` argument: The argument wasn't passsed to your JVM. Check your startup scripts or other resources to ensure there's nothing preventing it from being passed. For more info about how to pass the argument for your environment, see [Include the Java agent with a JVM argument](/docs/agents/java-agent/installation/include-java-agent-jvm-argument).
-   4. If niether solution works, keep reading.
+   4. If neither solution works, keep reading.
 4. Verify that your `newrelic.jar` and `newrelic.yml` files are in the same [directory](/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#java-agent). If you have specified a non-default location for the config file using the `newrelic.config.file` system property, ensure that the config file does exist in that location and is correctly formatted.
 5. [Generate `finest` level logs](/docs/agents/java-agent/troubleshooting/generating-logs-troubleshooting), and check the logs for errors. In the event no log file can be found, see [No log file (Java)](/docs/agents/java-agent/troubleshooting/no-log-file-java).
 6. Check the application server logs for errors related to the New Relic Java agent. You can see the troubleshooting pages [Error bootstrapping Java agent](/docs/agents/java-agent/troubleshooting/error-bootstrapping-new-relic-java-agent) and [Errors starting Java app server](/docs/agents/java-agent/troubleshooting/errors-starting-java-app-server) for examples of observable errors in application server logs that prevent the java agent data from reporting.

diff --git a/src/content/docs/change-tracking/change-tracking-view-analyze.mdx b/src/content/docs/change-tracking/change-tracking-view-analyze.mdx
@@ -207,7 +207,7 @@ After you create a marker using GraphQL, you can use NRQL in the [query builder]
 Try these examples or create your own queries:
 
 <Callout variant="tip">
-  For details about the data structure and attribute definitions, see our [data dictionary](/attribute-dictionary/?dataSource=Change+tracking&event=Deployments).
+  For details about the data structure and attribute definitions, see our [data dictionary](/attribute-dictionary/?dataSource=Change+tracking).
 </Callout>
 
 <CollapserGroup>

diff --git a/src/content/docs/errors-inbox/browser-tab.mdx b/src/content/docs/errors-inbox/browser-tab.mdx
@@ -94,8 +94,11 @@ Stack traces can show you where in the code an error is originating from to help
 
 ### Troubleshoot missing stack traces [#troubleshoot]
 
- Some reasons why you may not see a stack trace for an error:
-    * If errors are not thrown, they will not produce a stack trace.
+Here are some reasons you don't see a stack trace for an error:
+    * If errors are not thrown there won't be a stack trace. 
+        - Example of a thrown errror that will NOT have a stack trace: throw `this is an error string`.
+        - Example of a thrown errror that will  have a stack trace: throw new Error `this is an error string`.
+
     * The Javascript is hosted on a CDN or another external location, and New Relic can't see the errors originating from those scripts. This can be solved in some cases by using cross-origin resource sharing (CORS).
     * It is an AngularJS error. For more on this, see [Missing Angular errors](/docs/browser/new-relic-browser/troubleshooting/angularjs-errors-do-not-appear).
     * The error is a `SyntaxError` or `Script error`: These occur while the script is loading, so they do not produce a stack trace.

diff --git a/src/images/accounts_screenshot-full_user-menu-location.webp b/src/images/accounts_screenshot-full_user-menu-location.webp
diff --git a/src/images/browser_screenshot-full_filtered-web-vitals.webp b/src/images/browser_screenshot-full_filtered-web-vitals.webp
diff --git a/src/images/browser_screenshot-full_page-url-view.webp b/src/images/browser_screenshot-full_page-url-view.webp
diff --git a/src/images/queries-nrql_screenshot-crop_event-count-in-query-builder.webp b/src/images/queries-nrql_screenshot-crop_event-count-in-query-builder.webp
diff --git a/src/images/queries-nrql_screenshot-full_query-builder.webp b/src/images/queries-nrql_screenshot-full_query-builder.webp
diff --git a/src/nav/alerts-applied-intelligence.yml b/src/nav/alerts-applied-intelligence.yml
@@ -3,6 +3,9 @@ path: /docs/alerts-applied-intelligence
 pages:
   - title: Introduction to alerts and applied intelligence
     path: /docs/alerts-applied-intelligence/overview
+  - title: Create and manage alerts
+    label: Tutorial
+    path: /docs/tutorial-create-alerts/create-new-relic-alerts
   - title: Alerting best practice guide
     path: /docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices
   - title: Detect problems in your system

diff --git a/src/nav/apm.yml b/src/nav/apm.yml
@@ -3,6 +3,9 @@ path: /docs/apm
 pages:
   - title: Get started with APM
     path: /introduction-apm
+  - title: My app is slow
+    label: Tutorial
+    path: /docs/tutorial-app-slow/root-causes
   - title: Guides
     pages:
     - title: Troubleshoot with the summary page

diff --git a/src/nav/browser.yml b/src/nav/browser.yml
@@ -3,6 +3,9 @@ path: /docs/browser
 pages:
   - title: Get started with browser monitoring
     path: /docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring
+  - title: Improve your website's performance
+    label: Tutorial
+    path: /docs/tutorial-app-performance/instrument-your-site
   - title: Guides
     pages:
       - title: Browser monitoring best practices

diff --git a/src/nav/logs.yml b/src/nav/logs.yml
@@ -3,6 +3,9 @@ path: /docs/logs
 pages:
   - title: Get started with log management
     path: /docs/logs/get-started/get-started-log-management
+  - title: Manage large amounts of logs
+    label: Tutorial
+    path: /docs/tutorial-large-logs/get-started-managing-large-logs
   - title: Logging best practices
     path: /docs/logs/get-started/logging-best-practices
   - title: Log management and security

diff --git a/src/nav/new-relic-solutions.yml b/src/nav/new-relic-solutions.yml
@@ -67,8 +67,6 @@ pages:
             path: /docs/new-relic-solutions/get-started/networks
           - title: Supported browsers
             path: /docs/new-relic-solutions/get-started/supported-browsers-new-relics-ui
-      - title: Build your own New Relic apps
-        path: /docs/new-relic-solutions/new-relic-one/build-custom-new-relic-one-application
       - title: Transition guide for new platform UI
         path: /docs/new-relic-solutions/new-relic-one/new-navigation-transition-guide
   - title: New Relic mobile apps
@@ -183,10 +181,12 @@ pages:
             path: /docs/more-integrations/terraform/terraform-modules
           - title: Manage multiple environments
             path: /docs/more-integrations/terraform/terragrunt
-  - title: Tutorials
+  - title: Build on New Relic UI
     pages:
       - title: New Relic CLI
         path: /docs/new-relic-solutions/tutorials/new-relic-cli
+      - title: Build your own New Relic apps
+        path: /docs/new-relic-solutions/new-relic-one/build-custom-new-relic-one-application
       - title: Create a "Hello, World!" app in New Relic
         path: /docs/new-relic-solutions/tutorials/build-hello-world-app
       - title: Build a New Relic app with React hooks

diff --git a/src/nav/root.yml b/src/nav/root.yml
@@ -8,14 +8,15 @@ pages:
     path: tutorial-app-slow
   - title: Improve your website's performance
     path: tutorial-app-performance
+  - title: Tutorials and guides
+  - title: Create and manage alerts
+    path: tutorial-create-alerts
   - title: Manage large amounts of logs
     path: tutorial-large-logs
   - title: Prepare for peak demand
     path: tutorial-peak-demand
   - title: Migrate from Datadog 
     path: tutorial-dd-migration
-  - title: Create alerts
-    path: tutorial-create-alerts
   - title: Guides and best practices
     path: new-relic-solutions
   - title: Monitor your data

diff --git a/src/nav/tutorial-create-alerts.yml b/src/nav/tutorial-create-alerts.yml
@@ -1,9 +1,9 @@
-title: Creating alerts
+title: Create and manage alerts
 path: /docs/tutorial-create-alerts
 pages:
   - title: Getting started with New Relic alerts
     path: /docs/tutorial-create-alerts/create-new-relic-alerts
   - title: Create chart alerts
     path: /docs/tutorial-create-alerts/create-an-alert
   - title: Improve your stack with alerts
-    path: /docs/tutorial-create-alerts/improve-with-alerts
+    path: /docs/tutorial-create-alerts/improve-with-alerts