Update logs-dedicated-clusters.md

Author: yossi-y

articles/azure-monitor/logs/logs-dedicated-clusters.md

@@ -42,11 +42,11 @@ There are two modes of billing for usage on a cluster. These can be specified by
 
 1. **Cluster**: in this case (which is the default), billing for ingested data is done at the cluster level. The ingested data quantities from each workspace associated to a cluster are aggregated to calculate the daily bill for the cluster. 
 
-2. **Workspaces**: the Commitment Tier costs for your Cluster are attributed proportionately to the workspaces in the cluster, by each workspace's data ingestion volume (after accounting for per-node allocations from [Azure Security Center](../../security-center/index.yml) for each workspace.) This full details of this pricing model are explained [here](../manage-cost-storage.md#log-analytics-dedicated-clusters). 
+2. **Workspaces**: the Commitment Tier costs for your Cluster are attributed proportionately to the workspaces in the cluster, by each workspace's data ingestion volume (after accounting for per-node allocations from [Azure Security Center](../../security-center/index.yml) for each workspace.) This full details of this pricing model are explained [here](./manage-cost-storage.md#log-analytics-dedicated-clusters). 
 
 If your workspace is using legacy Per Node pricing tier, when it is linked to a cluster it will be billed based on data ingested against the cluster’s Commitment Tier, and no longer Per Node. Per-node data allocations from Azure Security Center will continue to be applied.
 
-Complete details are billing for Log Analytics dedicated clusters are available [here](../manage-cost-storage.md#log-analytics-dedicated-clusters).
+Complete details are billing for Log Analytics dedicated clusters are available [here](./manage-cost-storage.md#log-analytics-dedicated-clusters).
 
 ## Asynchronous operations and status check