Skip to content

Commit 92d14f3

Browse files
Merge pull request #2458 from MicrosoftDocs/main638683815245381485sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents 59182d4 + 2ef22a8 commit 92d14f3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

data-explorer/kusto/query/assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Did you no, KQL is case-sensitive for everything – table names, table column n
4949

5050
This query has a single tabular expression statement. The statement begins with a reference to a table called *StormEvents* and contains several operators, [`where`](where-operator.md) and [`count`](count-operator.md), each separated by a pipe. The data rows for the source table are filtered by the value of the *StartTime* column and then filtered by the value of the *State* column. In the last line, the query returns a table with a single column and a single row containing the count of the remaining rows.
5151

52-
In contrast to Kusto queries, [Management commands](../management/index.md) are requests to Kusto to process or modify data or metadata. For example, the following management command creates a new Kusto table with two columns, `Level` and `Number`:
52+
In contrast to Kusto queries, [Management commands](../management/index.md are requests to Kusto to process or modify data or metadata. For example, the following management command creates a new Kusto table with two columns, `Level` and `Number`:
5353

5454
```kusto
5555
.create table Logs (Level:string, Text:string)

0 commit comments

Comments
 (0)