fix: architectural change

src/data/nav.yml

@@ -68,10 +68,12 @@
       pages:
         - title: Spin up Geek movie shop architecture
           url: '/automate-workflows/error-inbox/spin-up-geek-movie'
-        - title: Create a workload
-          url: '/automate-workflows/error-inbox/create-a-workload'
-        - title: Track and triage errors in error inbox
-          url: '/automate-workflows/error-inbox/set-up-error-inbox'
+        - title: Set up errors inbox
+          url: '/automate-workflows/error-inbox/set-up-errors-inbox'
+        - title: Triage your errors
+          url: '/automate-workflows/error-inbox/triage-errors'
+        - title: Manage your triaged errors
+          url: '/automate-workflows/error-inbox/manage-errors'
 - title: Build apps
   icon: nr-build-apps
   url: '/build-apps'

src/markdown-pages/automate-workflows/error-inbox/index.mdx

@@ -2,13 +2,13 @@
 path: '/automate-workflows/error-inbox'
 title: 'Resolve Errors Faster with Full Stack Error Tracking'
 template: 'LabOverviewTemplate'
-description: 'Use New Relic to qucikly track errors in your application with the help of error inbox.'
+description: 'Use New Relic to qucikly track errors in your application with the help of errors inbox.'
 ---
 
 <Intro>
 
 You're a developer of an eCommerce website called Geek's movie shop. You made some recent changes in your site's architecture and introduced some new features. The changes are ready to go live. However, you know that it's hard to identify the blast radius of errors once the application is in production. Since the changes are going to impact thousands of your customers, you want to find out if these changes will have any negative effect on them before pushing it to production. 
-To ensure a smooth experience for your customers, you can use Error Inbox to track errors across you stack and take action on them before they impact your customers. 
+To ensure a smooth experience for your customers, you can use errors inbox to track errors across you stack and take action on them before they impact your customers. 
 
 </Intro>
 
@@ -27,8 +27,9 @@ Errors inbox is not available in the EU region.
 In this lab, you:
 
 - Spin up the infrastructure for Geek's movie shop
-- Create a workload in New Relic 
-- Track and triage errors in error Inbox
+- Set up errors inbox
+- Triage your errors in errors inbox
+- Manage your triaged errors
 
 </div>
 

src/markdown-pages/automate-workflows/error-inbox/manage-errors.mdx

@@ -0,0 +1,87 @@
+---
+path: '/automate-workflows/error-inbox/manage-errors'
+title: 'Manage your triaged errors'
+template: 'GuideTemplate'
+description: 'Managed your triaged errors in errors inbox'
+duration: 15
+procIdx: 4
+---
+
+<Callout variant="course" title="lab">
+
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox. 
+
+Each procedure in the lab builds upon the last, so make sure you've completed the last procedure, [Triage your errors](/automate-workflows/error-inbox/triage-errors), before starting this one.
+
+</Callout>
+
+## Change filter
+By default, errors inbox show all the unresolved errors on the main screen. Once the error status is updated to resolved or ignored, you no longer see the error on the main screen. However, you can change the filter to view these errors.
+
+The main screen of errors inbox has a filter pane right below the top nav.
+![filters pane of errors inbox](../../../images/error-inbox/filters-pane.png)
+
+Click **Unresolved** to change the filter value.
+![chnage filter value](../../../images/error-inbox/change-filter.png)
+
+Here, you see three options in the dropdown. Select **Ignored**.
+![view ignored error groups](../../../images/error-inbox/view-ignored-errors.png)
+
+Your errors inbox now show all the ignored error groups.
+![ignored error groups](../../../images/error-inbox/ignored-error-groups.png)
+
+## Optional
+
+### Connect errors inbox to Jira
+Connect errors inbox to jira to qucikly and easily create tickets containing error details and link to the stack trace. It allows you to collaborate and resolve errors faster.
+
+Connect your errors inbox to jira:
+<Steps>
+<Step>
+
+Click on the Jira integration icon on the far right side of the error group you want to connect to Jira.
+![jira integration](../../../images/error-inbox/jira-integration.png)
+</Step>
+<Step>
+
+Click **Add JIRA Workspace** from the dropdown.
+![add jira workspace](../../../images/error-inbox/add-jira-workspace.png)
+</Step>
+<Step>
+
+Fill in the fields on the next page and click **Test connection** to ensure that your details are correct. Then, click **Save destination**.
+![add jira destination](../../../images/error-inbox/add-jira-destination.png)
+</Step>
+<Step>
+
+Next, set up a template. Click the jira integration icon against the error group and select **Add New Template +**.
+![add new template](../../../images/error-inbox/add-new-template.png)
+</Step>
+<Step>
+
+Add **Jira destination**, **Project**, and **Issue type** on the next page and click **Update message** to save the template. 
+![edit template](../../../images/error-inbox/edit-template.png)
+
+<Callout variant='tip'>
+
+Here, you can also click **Send test notification** to preview the ticket in your jira board before saving the template. Note that a test notification will create a jira ticket in your workspace.
+</Callout>
+</Step>
+</Steps>
+
+Now you can create jira ticket by clicking the jira integration icon on the far right side of the error group and selecting a template. 
+
+<Callout variant='tip'>
+
+You can also connect errors inbox with Slack and CodeStream. Read [our docs](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/) to learn more about the supported integrations.
+
+</Callout>
+
+# Summary:
+In this lab, you set up errors inbox to track and triage errors in your application. You also managed triaged errors in errors inbox and integrated your errors inbox with jira to help you effectively collaborate and resolve errors faster from across your stack. 
+
+# Homework
+Now that you know how to track and triage errors using errors inbox, here are some other things to familiarize yourself even more with errors inbox.
+- Read our documentation on [errors inbox](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/)
+- Read our blog [Collaborate and fix errors quickly with Errors Inbox and workloads](https://newrelic.com/blog/how-to-relic/track-errors-errors-inbox)
+- Read our blog [Error Tracking Across Your Entire Stack with New Relic Errors Inbox](https://newrelic.com/blog/how-to-relic/error-tracking-with-errors-inbox)