Merge pull request #2631 from MicrosoftDocs/main638838114519048752sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

data-explorer/kusto/query/bag-set-key-function.md

@@ -34,7 +34,7 @@ Returns a `dynamic` property-bag with specified key-value pairs. If the input ba
 
 ## Examples
 
-### Use a root-level key
+The following example demonstrates how to set a root-level key in a property bag.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -54,7 +54,8 @@ datatable(input: dynamic) [
 |{<br>  "key1": 1,<br>  "key2": 2<br>}|{<br>  "key1": 1,<br>  "key2": 2,<br>  "key3": 3<br>}|
 |{<br>  "key1": 1,<br>  "key3": "abc"<br>}|{<br>  "key1": 1,<br>  "key3": 3<br>}|
 
-### Use a JSONPath key
+The following example demonstrates how to set a JSONPath key in a property bag.
+
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/bag-unpack-plugin.md

@@ -60,7 +60,7 @@ The `bag_unpack` plugin returns a table with as many records as its tabular inpu
 
 ## Examples
 
-### Expand a bag
+The following example demonstrates how to expand a bag.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -85,9 +85,7 @@ datatable(d:dynamic)
 |40 |Dave   |
 |30 |Jasmine|
 
-### Expand a bag with OutputColumnPrefix
-
-Expand a bag and use the `OutputColumnPrefix` option to produce column names that begin with the prefix 'Property_'.
+The following example demonstrates how to expand a bag and use the `OutputColumnPrefix` option to produce column names that begin with the prefix 'Property_'.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -112,9 +110,7 @@ datatable(d:dynamic)
 |40          |Dave         |
 |30          |Jasmine      |
 
-### Expand a bag with columnsConflict
-
-Expand a bag and use the `columnsConflict` option to resolve conflicts between existing columns and columns produced by the `bag_unpack()` operator.
+The following example demonstrates how to expand a bag and use the `columnsConflict` option to resolve conflicts between existing columns and columns produced by the `bag_unpack()` operator.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -162,9 +158,8 @@ datatable(Name:string, d:dynamic)
 |40 |Old_name |
 |30 |Old_name |
 
-### Expand a bag with ignoredProperties
 
-Expand a bag and use the `ignoredProperties` option to ignore certain properties in the property bag.
+The following example demonstrates how to expand a bag and use the `ignoredProperties` option to ignore certain properties in the property bag.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -190,9 +185,7 @@ datatable(d:dynamic)
 |Dave|
 |Jasmine|
 
-### Expand a bag with a query-defined OutputSchema
-
-Expand a bag and use the `OutputSchema` option to allow various optimizations to be evaluated before running the actual query.
+The following example demonstrates how to expand a bag and use the `OutputSchema` option to allow various optimizations to be evaluated before running the actual query.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -217,7 +210,7 @@ datatable(d:dynamic)
 |Dave     |  40  |
 |Jasmine  |  30  |
 
-Expand a bag and use the `OutputSchema` option to allow various optimizations to be evaluated before running the actual query. Use a wildcard `*` to return all columns of the input table.
+The following example demonstrates how to expand a bag and use the `OutputSchema` option to allow various optimizations to be evaluated before running the actual query. Use a wildcard `*` to return all columns of the input table.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/bag-zip.md

@@ -36,7 +36,7 @@ Returns a [dynamic](scalar-data-types/dynamic.md) property-bag.
 
 ## Examples
 
-In the following example, the array of keys and the array of values are the same length and are zipped together into a dynamic property bag.
+The following example shows how to use `bag_zip()` to create a property-bag from two arrays. The first array contains the keys, and the second array contains the values. The resulting property-bag contains the keys and values zipped together.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -55,9 +55,7 @@ Data
 |--|--|--|
 | ['a','b','c'] | [1,'2',3.4] | {'a': 1,'b': '2','c': 3.4} |
 
-### More keys than values
-
-In the following example, the array of keys is longer than the array of values. The missing values are filled with nulls.
+The following example shows how to use `bag_zip()` when the arrays have different lengths. In this case, the resulting property-bag contains null values for the missing keys.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -76,9 +74,7 @@ Data
 |--|--|--|
 | ['a','b','c'] | [1,'2'] | {'a': 1,'b': '2','c': null} |
 
-### More values than keys
-
-In the following example, the array of values is longer than the array of keys. Values with no matching keys are ignored.
+The following example shows how to use `bag_zip()` when the arrays have different lengths. In this case, the resulting property-bag contains null values for the missing keys.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -97,9 +93,7 @@ Data
 |--|--|--|
 | ['a','b'] | [1,'2',2.5] | {'a': 1,'b': '2'} |
 
-### Non-string keys
-
-In the following example, there are some values in they keys array that aren't of type string. The non-string values are ignored.
+The following example demonstrates how `bag_zip()` handles cases where the keys array contains non-string values. Any key that isn't a string is excluded from the resulting property-bag.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -118,9 +112,7 @@ Data
 |--|--|--|
 | ['a',8,'b'] | [1,'2',2.5] | {'a': 1,'b': 2.5} |
 
-### Fill values with null
-
-In the following example, the parameter that is supposed to be an array of values isn't an array, so all values are filled with nulls.
+The following example demonstrates how `bag_zip()` behaves when the parameter intended to be an array of values is not actually an array. In this case, all resulting property values are set to null.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -139,9 +131,7 @@ Data
 |--|--|--|
 | ['a',8,'b'] | 1 | {'a': null,'b': null} |
 
-### Null property-bag
-
-In the following example, the parameter that is supposed to be an array of keys isn't an array, so the resulting property-bag is null.
+The following example demonstrates how `bag_zip()` behaves when the parameter intended to be an array of keys is not actually an array. In this case, the resulting property-bag is null.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/base64-decode-toarray-function.md

@@ -27,7 +27,9 @@ Decodes a base64 string to an array of long values.
 
 Returns an array of long values decoded from a base64 string.
 
-## Example
+## Examples
+
+The following example shows how to use `base64_decode_toarray()` to decode a base64 string into an array of long values.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/base64-decode-toguid-function.md

@@ -27,7 +27,9 @@ Decodes a base64 string to a [GUID](scalar-data-types/guid.md).
 
 Returns a [GUID](scalar-data-types/guid.md) decoded from a base64 string.
 
-## Example
+## Examples
+
+The following example shows how to use `base64_decode_toguid()` to decode a base64 string into a GUID.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/base64-decode-tostring-function.md

@@ -29,7 +29,9 @@ Decodes a base64 string to a UTF-8 string.
 
 Returns UTF-8 string decoded from base64 string.
 
-## Example
+## Examples
+
+The following example shows how to use `base64_decode_tostring()` to decode a base64 string into a UTF-8 string.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/base64-encode-fromarray-function.md

@@ -29,6 +29,8 @@ Returns the base64 string encoded from the bytes array. Note that byte is an int
 
 ## Examples
 
+The following example shows how to use `base64_encode_fromarray()` to encode a bytes array into a base64 string.
+
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
 > <a href="https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAA8tJLVFIqixJLY5PLCpKrFSwVSjJL05OzEks0igoyswDSiYWp5qZxKekJuenpMaX5IOVaSgFG4dVpbhb2CppalpzQVRClKTEQ3UUlwBF04EGQvmpeWAT0orycyFmIFmrCQCPOEFEhwAAAA==" target="_blank">Run the query</a>

data-explorer/kusto/query/base64-encode-fromguid-function.md

@@ -27,7 +27,9 @@ Encodes a [GUID](scalar-data-types/guid.md) to a base64 string.
 
 Returns a base64 string encoded from a GUID.
 
-## Example
+## Examples
+
+The following example shows how to use `base64_encode_fromguid()` to encode a GUID into a base64 string.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/base64-encode-tostring-function.md

@@ -29,7 +29,9 @@ Encodes a string as base64 string.
 
 Returns *string* encoded as a base64 string.
 
-## Example
+## Examples
+
+The following example shows how to use `base64_encode_tostring()` to encode a string into a base64 string.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]

data-explorer/kusto/query/basket-plugin.md

@@ -38,7 +38,9 @@ Each pattern is represented by a row in the results. The first column is the seg
 > [!NOTE]
 > The algorithm uses sampling to determine the initial frequent values. Therefore, the results could slightly differ between multiple runs for patterns whose frequency is close to the threshold.
 
-## Example
+## Examples
+
+The following example uses the `basket` plugin to find frequent patterns in the data.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]
@@ -66,7 +68,7 @@ StormEvents
 |6|1310|22.3|||YES|
 |7|1291|21.9||Thunderstorm Wind||
 
-### Example with custom wildcards
+The following example demonstrates using the `basket` plugin with a weight column and custom wildcards to find frequent patterns.
 
 :::moniker range="azure-data-explorer"
 > [!div class="nextstepaction"]