From f98af08be8f8a60dd1881f53e37a7fa463ff3b81 Mon Sep 17 00:00:00 2001
From: goodroot <9484709+goodroot@users.noreply.github.com>
Date: Mon, 25 Nov 2024 13:39:35 -0800
Subject: [PATCH] casing

---
 documentation/reference/function/window.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/documentation/reference/function/window.md b/documentation/reference/function/window.md
index 4b14a085..3fa1f49c 100644
--- a/documentation/reference/function/window.md
+++ b/documentation/reference/function/window.md
@@ -664,15 +664,15 @@ This example:
 - Uses rolling 1-minute window
 - Shows order book activity patterns
 
-## Notes and Restrictions
+## Notes and restrictions
 
-### ORDER BY Behavior
+### ORDER BY behavior
 - ORDER BY in OVER clause determines the logical order for window functions
 - Independent of the query-level ORDER BY
 - Required for window-only functions
 - Required for RANGE frames
 
-### Frame Specifications
+### Frame specifications
 - ROWS frames:
   - Based on physical row counts
   - More efficient for large datasets
@@ -683,12 +683,12 @@ This example:
   - Require ORDER BY on timestamp or numeric column
   - Support time-based intervals (e.g., '1h', '5m')
 
-### Exclusion Behavior
+### Exclusion behavior
 - Using `EXCLUDE CURRENT ROW` with frame end at `CURRENT ROW`:
   - Automatically adjusts end boundary to `1 PRECEDING`
   - Ensures consistent results across queries
 
-### Window-Only Function Restrictions
+### Window-only function restrictions
 - Always require ORDER BY clause
 - Cannot be used in:
   - WHERE clauses
@@ -696,7 +696,7 @@ This example:
   - Window function arguments
 - Do not support frame clauses
 
-### Performance Considerations
+### Performance considerations
 - ROWS frames typically perform better than RANGE frames for large datasets
 - Partitioning can improve performance by processing smaller chunks of data
 - Consider index usage when ordering by timestamp columns