fix links

Author: amagginetti

articles/communication-services/concepts/analytics/logs/call-metrics-log-schema.md

@@ -24,7 +24,6 @@ Call Metrics logs contain aggregated calling metrics in daily bins based on attr
 ## Data Concepts
 
 
-
 a separate page that explains "metrics" conceptually
 what is metric - Based on thresholds defined in ACSCallingMetrics.Goal how many distinct api calls succeded or failed in a daily bucket for dimentions liek SDK version, make model, subcode etc
 what does it measure - Failure and success count for a particualr api call or a complex condition like UFD recovering (count of good UFD>= count of bad UFD)
@@ -85,6 +84,7 @@ For the call metric log, there's no difference between P2P and group call scenar
 
 Here's a sample of the Call Metrics log: **Ankesh explain each part what they are**
 
+
 {
   "TenantId": "4e7403f8-515a-4df5-8e13-59f0e2b76e3a",
   "TimeGenerated": "2025-02-03T05:17:39.1840000Z",

articles/communication-services/concepts/analytics/logs/voice-and-video-logs.md

@@ -35,7 +35,9 @@ any quality investigations, and using **[Call Diagnostics](../../voice-video-cal
 
 ## Available logs 
 
-Azure Communication Services creates six types of call logs:
+Azure Communication Services creates six types of call logs and they share a common usage log:
+
+- **Usage Logs**: Contains common information that you can use to reference information across multiple tables. **NEED INPUT FROM TEAM ON THIS**
 
 - **Call Summary Logs**: Contain basic information about the call, including all the relevant IDs, time stamps, endpoints, and SDK information. For each participant within a call, Communication Services creates a distinct call summary log.
 

articles/communication-services/concepts/telephony/troubleshooting-pstn-call-failures.md

@@ -16,7 +16,7 @@ When you're troubleshooting Azure Communication Services PSTN call failures, we
 
 ## Use ResultCategories to troubleshoot failures
 
-The `ResultCategories` array is a property of the [call summary log schema](../analytics/logs/voice-and-video-logs.md#call-summary-log-schema). It contains a list of general reasons that describe how the call ended:
+The `ResultCategories` array is a property of the [Call Summary Log Schema](../analytics/logs/call-summary-log-schema.md). It contains a list of general reasons that describe how the call ended:
 
 - `Success`
 - `Failure`
@@ -27,7 +27,7 @@ This information can help you determine why a call ended without generating a de
 
 ## Use ParticipantEndReason and ParticipantEndSubCode to troubleshoot failures
 
-If the level of detail in `ResultCategories` isn't sufficient when you're troubleshooting PSTN calls, you can use `ParticipantEndReason` and `ParticipantEndSubCode` to understand the reasons why a call ended in greater detail. `ParticipantEndReason` and `ParticipantEndSubCode` are also properties of the [call summary log schema](../analytics/logs/voice-and-video-logs.md#call-summary-log-schema).
+If the level of detail in `ResultCategories` isn't sufficient when you're troubleshooting PSTN calls, you can use `ParticipantEndReason` and `ParticipantEndSubCode` to understand the reasons why a call ended in greater detail. `ParticipantEndReason` and `ParticipantEndSubCode` are also properties of the [Call Summary Log Schema](../analytics/logs/call-summary-log-schema.md).
 
 ### ParticipantEndReason