Merge pull request #228414 from zeinab-mk/patch-38

Update concept-best-practices-scanning.md

Author: prmerger-automator[bot]

articles/purview/concept-best-practices-scanning.md

@@ -143,7 +143,7 @@ After you register your source in the relevant [collection](./how-to-create-and-
     - **Scan type and schedule**
         - The scan process can be configured to run full or incremental scans.
         - Run the scans during non-business or off-peak hours to avoid any processing overload on the source.
-        - **start recurrence at** must be at least 1 minute lesser than the **schedule scan time**, otherwise, the scan will be triggered in next recurrence. 
+        - **Start recurrence at** must be at least 1 minute lesser than the **schedule scan time**, otherwise, the scan will be triggered in next recurrence. 
         - Initial scan is a full scan, and every subsequent scan is incremental. Subsequent scans can be scheduled as periodic incremental scans.
         - The frequency of scans should align with the change management schedule of the data source or business requirements. For example:
             - If the source structure could potentially change weekly, the scan frequency should be in sync. Changes include new assets or fields within an asset that are added, modified, or deleted.