Update AZFD0015 documentation for clarity and accuracy; exclude diagnostic events from filename checks

Author: ggailey777

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0015.md

@@ -9,7 +9,7 @@ ms.date: 02/10/2026
 
 # AZFD0015: Timer trigger schedule is not a CRON expression
 
-This event occurs when a timer trigger is configured with a non-CRON schedule expression (such as a `TimeSpan`) on a Consumption plan where the scale controller only supports CRON expressions.
+This event occurs when the schedule for an Azure Functions Timer trigger running in a Consumption or Flex Consumption plan is configured with a non-CRON  expression (such as a `TimeSpan`). For these hosting plans, the scale controller only supports CRON expressions.
 
 | | Value |
 |-|-|
@@ -18,21 +18,21 @@ This event occurs when a timer trigger is configured with a non-CRON schedule ex
 
 ## Event description
 
-Azure Functions timer triggers support both [CRON expressions][cron] and constant interval expressions (such as `TimeSpan` values like `"00:05:00"`). However, the scale controller used by Consumption plans only understands CRON expressions. When a non-CRON schedule is used on these plans, the timer trigger starts and fires correctly, but the scale controller can't interpret the schedule. This may lead to unexpected scaling behavior.
+Timer triggers support both [CRON expressions][cron] and constant interval expressions (such as `TimeSpan` values like `"00:05:00"`). However, the scale controller used by the Consumption and Flex Consumption plans can only interpret CRON expressions. When a non-CRON schedule is used when hosted on these plans, the timer trigger starts and fires correctly, but the scale controller can't interpret the schedule. This behavior can lead to unexpected scaling behavior.
 
-This warning currently applies to Linux Consumption plans. On Windows Consumption and Flex Consumption plans, non-CRON expressions are blocked entirely and produce a startup error.
+This warning currently applies to Consumption plan apps running on Linux. For Consumption plan apps running on Windows and apps hosted in a Flex Consumption plan, non-CRON expressions are blocked entirely, which results in a startup error.
 
 ## How to resolve the event
 
-Replace your timer trigger's schedule expression with an equivalent CRON expression. CRON expressions can use either 5 fields (minute granularity) or 6 fields (second granularity).
+Replace the schedule expression for your Timer trigger with an equivalent CRON expression. CRON expressions can use either five fields (minute granularity) or six fields (second granularity).
 
 For example, instead of a `TimeSpan` of `"00:05:00"` (every 5 minutes), use the CRON expression `"0 */5 * * * *"` (6-digit) or `"*/5 * * * *"` (5-digit).
 
-For more information on CRON expressions in Azure Functions, see [Timer trigger for Azure Functions][timer-trigger].
+For more information on CRON expressions in Azure Functions, see [NCRONTAB expressions][cron] in the Timer trigger reference.
 
 ## When to suppress the event
 
-This event shouldn't be suppressed. While the timer fires correctly today, the scale controller can't interpret non-CRON schedules, which may result in scaling issues. Migrating to a CRON expression ensures correct behavior.
+This event shouldn't be suppressed. While the timer fires correctly today, the scale controller can't interpret non-CRON schedules, which can cause scaling issues. Migrating to a CRON expression ensures correct behavior.
 
 [cron]: /azure/azure-functions/functions-bindings-timer#ncrontab-expressions
 [timer-trigger]: /azure/azure-functions/functions-bindings-timer

docfx.json

@@ -1859,6 +1859,11 @@
           "articles/site-recovery/**/*.md"
         ]
       },
+      "filename-incomplete": {
+        "exclude": [
+          "articles/azure-functions/errors-diagnostics/**/*.md"
+        ]
+      },
       "sensitive-language-sl": {
         "exclude": [
           "articles/azure-netapp-files/azure-netapp-files-create-volumes.md",