small fix to dashboards (#791)

Author: tanushree-sharma

docs/observability/how_to_guides/dashboards.mdx

@@ -32,7 +32,7 @@ Prebuilt dashboards are broken down into the following sections:
 | LLM Calls       | LLM call count and latency. Includes all runs where run type is "llm".                                                                                                                                                                                                                       |
 | Cost & Tokens   | Total and per-trace token counts and costs, broken down by token type. Costs are measured using [LangSmith's cost tracking](/observability/how_to_guides/log_llm_trace#manually-provide-token-counts).                                                                                       |
 | Tools           | Run counts, error rates, and latency stats for tool runs broken down by tool name. Includes runs where run type is "tool". Limits to top 5 most frequently occurring tools.                                                                                                                  |
-| Run Types       | Run counts, error rates, and latency stats for runs that are immediate children of the root run. This helps in understanding the the high-level execution path of agents. Limits to top 5 most frequently occuring tool names. <sup>1</sup>                                                  |
+| Run Types       | Run counts, error rates, and latency stats for runs that are immediate children of the root run. This helps in understanding the the high-level execution path of agents. Limits to top 5 most frequently occuring run names. <sup>1</sup>                                                   |
 | Feedback Scores | Aggregate stats for the top 5 most frequently occurring types of feedback. Charts show average score for numerical feedback and category counts for categorical feedback.                                                                                                                    |
 
 <sup>1</sup> For example, for the following trace, the following runs have a depth