fix: small fixes

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

@@ -15,27 +15,40 @@ Each procedure in the lab builds upon the last, so make sure you've completed th
 
 </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.
+You're now observing all the errors in errors inbox and you're trying to debug your application ASAP so you could make your site live. You also want to keep a track of all the triaged errors so you could track progress and (optionally) create tasks to resolve the other errors.
+
+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 your triaged errors.
+
+In this procedure, you view your triaged errors and (optionally) integrate Jira with errors inbox.
+
+## View triaged errors
+
+Change the filter in errors inbox to view your triaged 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)
+Here, you see three options in the dropdown. Select **Resolved**.
+![view resolved error groups](../../../images/error-inbox/view-resolved-errors.png)
+
+Your errors inbox now show all the resolved error groups, if any.
+![resolved error groups](../../../images/error-inbox/resolved-error-groups.png)
 
-Your errors inbox now show all the ignored error groups, if any.
-![ignored error groups](../../../images/error-inbox/ignored-error-groups.png)
+You don't see any error group here because none of the errors were marked resolved. If this was your real world application, you could resolve the error, mark the error as resolved and track your resolved errors here.
+
+<Callout variant='tip'>
+
+If you want to observe your ignored error groups instead of resolved, you could set the filter to **Ignored** here. Ignored filter show all the ignored error groups, if any, in errors inbox.
+</Callout>
 
 ## Optional
+Now you have a list of issues that you need to fix. You want to create tasks in your workspace so you could collaborate with your teammates and easily keep a track. Connect errors inbox to Jira to qucikly and easily create tickets containing error details and link to the stack trace. This allows you to collaborate and resolve errors faster.
 
 ### 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:
+Connect your errors inbox to Jira:
 <Steps>
 <Step>
 
@@ -77,10 +90,10 @@ You can also connect errors inbox with Slack and CodeStream. Read [our docs](htt
 
 </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. 
+## Summary:
+In this lab, you set up errors inbox to proactively observe and catch errors from across your stack. You analyzed the errors in full context and triaged them before they could affect your customers. 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
+## 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)

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

@@ -15,9 +15,11 @@ Each procedure in the lab builds upon the last, so make sure you've completed th
 
 </Callout>
 
-Errors inbox provides a unified error tracking to detect and triage errors from across your stack. Since you want to ensure a smooth experience for your customers, you can use errors inbox to analyze the errors in full context and resolve them before they impact your customers. 
+Although your application is still running in development but now, you're able to observe errors across your application in errors inbox. Since you want to ensure a smooth experience for your customers, the next step is to use errors inbox to analyze the errors in full context and triage them before you push changes to production.  
 
-In this procedure, you track and triage errors across your stack using errors inbox. 
+Triaging helps removing the noise from your errors inbox so you focus on the high impact errors and resolve them before they affect your customers.
+
+In this procedure, you track and triage errors across your workload using errors inbox. 
 
 <Callout variant='important'>
 
@@ -27,19 +29,20 @@ Errors inbox is not available in the EU region.
 
 ## Triage your errors in errors inbox
 
-You can triage error groups directly from the main screen. Triaging helps removing the noise from your errors inbox so you focus on the high impact errors.  
+You can triage error groups directly from the main screen. 
 
 ### See error details
 
-By default, errors inbox shows all your unresolved errors on one screen. To understand the root cause of these errors, you need more details. For instance:
+You see all the unresolved errors across your application in errors inbox but now you want to understand the root cause of the errors. To debug your application, you need more details. You see the error details on error details page:
 
 Click on **pika.exceptions:ChannelWrongStateError** error.
 ![pika.exceptions:ChannelWrongStateError error](../../../images/error-inbox/channel-wrong-state-error.png)
 
-This takes you to error details page. You find full context of the issue here including **Occurances**, **Stack Trace**, and others.
+This takes you to error details page. 
 ![error detail page](../../../images/error-inbox/error-detail-page.png)
 
-Stack trace is especially important since it helps you narrow down the cause of the problem. 
+Here, you find full context of the issue including **Occurances**, **Stack Trace**, and others. Stack trace is especially important since it helps you narrow down the cause of the problem. 
+
 Under **Stack Trace**, click **Show all** in bottom right corner.
 ![show full stack trace](../../../images/error-inbox/show-full-stack-trace.png)
 
@@ -56,15 +59,16 @@ You can also integrate [CodeStream](https://newrelic.com/codestream) with your e
 
 ### Set error statuses
 
-Each error in errors inbox has **unresolved** status by defulat. But you can set your error status as resolved, or ignored and filter your inbox by status. 
+You were told that another developer on your team fixed **pika.exceptions:ChannelWrongStateError** and you want to change it's status now.
+Each error in errors inbox has unresolved status by defulat. But you can set your error status as resolved, or ignored.  
 
 #### Set the error status as 'Resolved'
-Once you fixed the issue, you come back to errors inbox and change its status to resolved. 
+Since you were told that the issue was fixed, you come back to errors inbox and change its status to resolved. 
 
 Navigate to **Errors inbox** in New Relic One.
 ![errors inbox](../../../images/error-inbox/errors-inbox.png)
 
-You were told that another developer on your team has fixed **pika.exceptions:ChannelWrongStateError** but the errors inbox still has this issue marked as unresolved. Change it's status:
+Change your error status:
 
 Click **Unresolved** against the error.
 ![channel wrong state error](../../../images/error-inbox/channel-wrong-state.png)
@@ -102,7 +106,7 @@ The error is now assigned to you.
 Currently assigning an error group to a user does not send a notification. Notifications of assignment and changes to error groups will be coming soon.
 </Callout>
 
-Once you assign error in errors inbox, it keeps a track of who worked on the error.
+Once you assign error in errors inbox, it keeps a track of who worked on the error. In case you come back to see this error again sometime later, it'll be easier for you to keep a track of who worked on this error. 
 
 <Callout variant="course" title="lab">