Update call-summary-updates-log-schema.md

Author: amagginetti

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

@@ -43,6 +43,8 @@ When using the call summary updates log schema, always refer to the highest `Cal
 
 ### More about log versions and data latency
 
+The CallSummaryUpdates log may require approximately 60 minutes to generate 
+
 After a call ends, an initial version (version 1) of the log is sent to the CallSummaryUpdates and CallDiagnosticUpdates tables. Initial versions may contain `null` values, if more information becomes available updated versions of the logs are created with more complete information. For example, client data can be delayed because of network connectivity issues between the client computer and our servers, or something as simple as a user closing the lid on their laptop post-call before their client data was sent and re-opening it hours (or days) later. 
 
 
@@ -355,4 +357,4 @@ If you have multiple Azure Communications Services resource IDs, you must enable
 - Learn about the [insights dashboard to monitor Voice Calling and Video Calling logs](/azure/communication-services/concepts/analytics/insights/voice-and-video-insights).
 
 - Learn how to use call logs to diagnose call quality and reliability
-  issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
+  issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)