Merge pull request #217770 from ynpandey/patch-8

Updated v1/how-to-monitor-datasets.md

Author: prmerger-automator[bot]

articles/machine-learning/v1/how-to-monitor-datasets.md

@@ -351,7 +351,7 @@ Limitations and known issues for data drift monitors:
 
     | Feature type | Data type | Condition | Limitations | 
     | ------------ | --------- | --------- | ----------- |
-    | Categorical | string, bool, int, float | The number of unique values in the feature is less than 100 and less than 5% of the number of rows. | Null is treated as its own category. | 
+    | Categorical | string | The number of unique values in the feature is less than 100 and less than 5% of the number of rows. | Null is treated as its own category. | 
     | Numerical | int, float | The values in the feature are of a numerical data type and do not meet the condition for a categorical feature. | Feature dropped if >15% of values are null. | 
 
 * When you have created a data drift monitor but cannot see data on the **Dataset monitors** page in Azure Machine Learning studio, try the following.
@@ -383,4 +383,4 @@ Limitations and known issues for data drift monitors:
 
 * Head to the [Azure Machine Learning studio](https://ml.azure.com) or the [Python notebook](https://github.com/Azure/MachineLearningNotebooks/blob/master/how-to-use-azureml/work-with-data/datadrift-tutorial/datadrift-tutorial.ipynb) to set up a dataset monitor.
 * See how to set up data drift on [models deployed to Azure Kubernetes Service](how-to-enable-data-collection.md).
-* Set up dataset drift monitors with [Azure Event Grid](../how-to-use-event-grid.md).
+* Set up dataset drift monitors with [Azure Event Grid](../how-to-use-event-grid.md).