From ed94de25c32505f13924a946585623d9ea70d03c Mon Sep 17 00:00:00 2001 From: FrankHassanabad Date: Wed, 11 Nov 2020 14:27:07 -0700 Subject: [PATCH] Updates docs a bit --- .../detections/components/rules/step_define_rule/index.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugins/security_solution/public/detections/components/rules/step_define_rule/index.tsx b/x-pack/plugins/security_solution/public/detections/components/rules/step_define_rule/index.tsx index 0d8898eb312ae..f06d4bdef74cb 100644 --- a/x-pack/plugins/security_solution/public/detections/components/rules/step_define_rule/index.tsx +++ b/x-pack/plugins/security_solution/public/detections/components/rules/step_define_rule/index.tsx @@ -194,7 +194,7 @@ const StepDefineRuleComponent: FC = ({ * * queryBar.value === defaultQueryBar (Has the user changed the input of '' yet?) * * queryBar.value === threatQueryBarDefaultValue (Has the user changed the input of '*:*' yet?) * This is a stronger guarantee than "isPristine" off of the forms as that value can be reset - * if you go to step 2) and then back to step 2) or the form is reset in another way. Using + * if you go to step 2) and then back to step 1) or the form is reset in another way. Using * the reference compare we know factually if the data is changed as the references must change * in the form libraries form the initial defaults. */