fix links

Author: mdbirnstiehl

solutions/observability/data-set-quality-monitoring.md

@@ -18,7 +18,7 @@ To open **Data Set Quality**, find **Stack Management** in the main menu or use
 ::::{admonition} Requirements
 :class: note
 
-Users with the `viewer` role can view the Data Sets Quality summary. To view the Active Data Sets and Estimated Data summaries, users need the `monitor` [index privilege](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md#privileges-list-indices) for the `logs-*-*` index.
+Users with the `viewer` role can view the Data Sets Quality summary. To view the Active Data Sets and Estimated Data summaries, users need the `monitor` [index privilege](../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md#privileges-list-indices) for the `logs-*-*` index.
 
 ::::
 
@@ -56,7 +56,7 @@ To use Logs Explorer or Discover to find ignored fields in individual logs:
 1. Find data sets with degraded documents using the **Degraded Docs** column of the data sets table.
 2. Click the percentage in the **Degraded Docs** column to open the data set in Logs Explorer or Discover.
 
-The **Documents** table in Logs Explorer or Discover is automatically filtered to show documents that were not parsed correctly. Under the **actions** column, you’ll find the degraded document icon (![degraded document icon](../../../images/serverless-indexClose.svg "")).
+The **Documents** table in Logs Explorer or Discover is automatically filtered to show documents that were not parsed correctly. Under the **actions** column, you’ll find the degraded document icon (![degraded document icon](../../images/serverless-indexClose.svg "")).
 
 Now that you know which documents contain ignored fields, examine them more closely to find the origin of the issue: