From 63db8a3c0fd834e84a8e37149771da4b2f6de558 Mon Sep 17 00:00:00 2001 From: May Lee Date: Mon, 28 Oct 2024 14:59:43 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Esther Kim --- .../guide/best_practices_for_creating_custom_rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/sensitive_data_scanner/guide/best_practices_for_creating_custom_rules.md b/content/en/sensitive_data_scanner/guide/best_practices_for_creating_custom_rules.md index 20b922066d059..924397e22ac3a 100644 --- a/content/en/sensitive_data_scanner/guide/best_practices_for_creating_custom_rules.md +++ b/content/en/sensitive_data_scanner/guide/best_practices_for_creating_custom_rules.md @@ -16,7 +16,7 @@ Sensitive Data Scanner uses scanning rules to identify, tag, and optionally reda ## Use precise regex patterns -Define regex patterns that are as precise as possible because generic patterns result in more false positives. To refine your regex pattern, add test data in the sample data tester when you are creating a custom rule. See step 2 in [Add a custom scanning rule][2] for more information. +Define regex patterns that are as precise as possible, because generic patterns result in more false positives. To refine your regex pattern, add test data in the sample data tester when creating a custom rule. For more information, see step 2 in [Add a custom scanning rule][2]. {{< img src="sensitive_data_scanner/guides/regex_sample_test.mp4" alt="Testing a regex pattern with a sample that matches and one that does not" video=true >}}