Merge pull request #126931 from changeworld/patch-6

Fix typo: propogate -> propagate

Author: v-dirichards

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

@@ -42,7 +42,7 @@ When using the Call Diagnostics Updates Log Schema, always refer to the highest
 
 ### More about log versions and data latency
 
-The call diagnostics updates log schema may require approximately 60 minutes following the end of a call to propogate data, most logs may be available within 40 minutes. 
+The call diagnostics updates log schema may require approximately 60 minutes following the end of a call to propagate data, most logs may be available within 40 minutes. 
 
 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.