AWS prescriptive-guidance documentation change
Summary
Formatting change: Removed bold formatting from section number in markdown table
Security assessment
Purely syntactic change to monitoring section header formatting without altering data quality monitoring content
Diff
diff --git a/prescriptive-guidance/latest/mlops-checklist/monitoring.md b/prescriptive-guidance/latest/mlops-checklist/monitoring.md index a91c9e287..95c494972 100644 --- a//prescriptive-guidance/latest/mlops-checklist/monitoring.md +++ b//prescriptive-guidance/latest/mlops-checklist/monitoring.md @@ -13 +13 @@ Continuous monitoring surfaces possible model issues such as data quality, distr -**6.1 Model monitoring: data quality detection** | Rule-based monitoring is in place to know when incoming data deviates from model training data. This type of monitoring creates a schema from the training data, sets constraints based on that schema, and then runs exceptions when a violation occurs. +6.1 Model monitoring: data quality detection| Rule-based monitoring is in place to know when incoming data deviates from model training data. This type of monitoring creates a schema from the training data, sets constraints based on that schema, and then runs exceptions when a violation occurs.