Clarify daily cap explanation and update documentation link

Updated the wording for clarity and improved the link reference in the daily cap section.

Author: DaleKoetke

support/azure/azure-monitor/log-analytics/billing/set-up-a-daily-cap.md

@@ -15,7 +15,7 @@ This article helps you learn how to set up a daily cap limit for a Log Analytics
 
 ## Strategies for safeguarding against unexpected data ingestion surges
 
-The daily cap on a Log Analytics workspace enables you to avoid unexpected increases in charges for data ingestion by stopping the collection of billable data for the rest of the day whenever a specified threshold is reached. Daily caps are typically used by organizations that are particularly cost-conscious. They shouldn't be used as a method to reduce costs but, instead, as a preventative measure to make sure that you don't exceed a particular budget. Learn more about using the daily cap [here](../../../../../azure/azure-monitor/logs/daily-cap.md).
+The daily cap on a Log Analytics workspace enables you to avoid unexpected increases in charges for data ingestion by stopping the collection of billable data for the rest of the day whenever a specified threshold is reached. Daily caps are typically used by organizations that are particularly cost-conscious. They shouldn't be used as a method to reduce costs but, instead, as a preventative measure to make sure that you don't exceed a particular budget. Learn more in the Log Analytics Daily Cap documentation.
 
 When data collection stops, you effectively have no monitoring of features or resources that rely on that workspace. Instead of relying on the daily cap alone, you can create an alert rule to notify yourself when data collection reaches a specified level before the daily cap is reached. Notification enables you to address any increases before data collection shuts down, or even to temporarily disable collection for less critical resources.