Merge pull request #113021 from V-vafune/patch-22

M49051 - Fixing Typo

Author: PRMerger20

articles/azure-monitor/log-query/query-optimization.md

@@ -104,7 +104,7 @@ Heartbeat
 | summarize count() by Computer
 ```
 
-### Use effective aggregation commands and dimmentions in summarize and join
+### Use effective aggregation commands and dimensions in summarize and join
 
 While some aggregation commands like [max()](/azure/kusto/query/max-aggfunction), [sum()](/azure/kusto/query/sum-aggfunction), [count()](/azure/kusto/query/count-aggfunction), and [avg()](/azure/kusto/query/avg-aggfunction) have low CPU impact due to their logic, other are  more complex and include heuristics and estimations that allow them to be executed efficiently. For example, [dcount()](/azure/kusto/query/dcount-aggfunction) uses the HyperLogLog algorithm to provide close estimation to distinct count of large sets of data without actually counting each value; the percentile functions are doing similar approximations using the nearest rank percentile algorithm. Several of the commands include optional parameters to reduce their impact. For example, the [makeset()](/azure/kusto/query/makeset-aggfunction) function has an optional parameter to define the maximum set size, which significantly affects the CPU and memory.