Merge pull request #83 from openobserve/docs-404-and-uppercase-issues

fixed 404 issues and uppercase URL issue

Author: DebashisBorgohainO2

docs/images/multi-window-4.png renamed to docs/images/multi-window-add-destination.png

@@ -30,7 +30,7 @@ This opens up the pipeline editor.
         - In the **Build Query** section, select the **Stream Type** (Logs, Metrics, or Traces) and **Stream Name**. Use the seach bar to search for the desired field in the source stream. 
         - In the **SQL Query** section, write a query to fetch data from a source. For **Metrics**, you also have the option to write **PromQL**.
         ![scheduled pipeline](../../images/create-pipeline-sch-query.png)
-        - Under **Set Variables**, schedule the query execution by setting the **Frequency** and **Period**. For more details, visit [Pipelines in OpenObserve](Pipelines-in-OpenObserve.md).
+        - Under **Set Variables**, schedule the query execution by setting the **Frequency** and **Period**. For more details, visit [Pipelines in OpenObserve](../pipelines-in-openobserve/).
         - Adjust the time filter and click **Run Query** to view the output.
         ![scheduled pipeline](../../images/create-pipeline-sch-output.png) 
         <br>In the above example, data is ingested periodically into the stream `default`. The query runs every 6 minutes and fetches all data that was ingested into the stream `default` in the preceding 6-minute interval.
@@ -96,7 +96,7 @@ This opens up the pipeline editor.
 
 ### Step 7: Save the pipeline
 
-After you click Save, it gets activated automatically. Learn how to [manage pipelines](Manage-Pipelines.md).
+After you click Save, it gets activated automatically. Learn how to [manage pipelines](../manage-pipelines/).
 
 ![active pipeline](../../images/pipeline8_save_pipeline.png)
 
@@ -167,4 +167,4 @@ Each run continues at fixed intervals from that point onward, such as 23:08, 23:
 
 
 ## Next Step
-- [Manage Pipelines](Manage-Pipelines.md) 
+- [Manage Pipelines](../manage-pipelines/) 

docs/images/multi-window-6.png renamed to docs/images/multi-window-frequency.png

@@ -76,5 +76,5 @@ To configure an external destination for pipelines:
 
 
 ## Next Steps
-- [Create and Use Pipelines](Create-and-Use-Pipelines.md)
-- [Manage Pipelines](Manage-Pipelines.md)
+- [Create and Use Pipelines](create-and-use-pipelines.md)
+- [Manage Pipelines](manage-pipelines.md)

docs/images/multi-window-5.png renamed to docs/images/multi-window-vrl-editor.png

@@ -1,5 +1,5 @@
 
-This guide explains how to use the configurable delay feature for [scheduled pipelines](Pipelines-in-OpenObserve.md).
+This guide explains how to use the configurable delay feature for [scheduled pipelines](../create-and-use-pipelines/).
 This feature allows you to delay the execution of a scheduled pipeline by a set number of minutes after its scheduled start time. This is useful to ensure data completeness and accommodate late-arriving events before the pipeline runs.
 
 ## How to Configure Delay
@@ -34,5 +34,5 @@ At 10:00 AM (scheduled time), the pipeline executes at 10:02 AM, processing data
 - **Data Window Unchanged**: Delay only affects when execution starts. It does not change the data range.
 
 **Related Links**<br>
-For steps on creating scheduled pipelines, see [Scheduled Pipelines](Create-and-Use-Pipelines.md).  
+For steps on creating scheduled pipelines, see [Scheduled Pipelines](../create-and-use-pipelines/).  
 

docs/user-guide/Pipelines/Create-and-Use-Pipelines.md

@@ -62,4 +62,4 @@ If any validation errors occur during import, refer to the following resolutions
 The imported pipeline appears in the **Pipelines** tab.   
 
 ## Related Links
-- [Manage Pipelines](Manage-Pipelines.md)
+- [Manage Pipelines](../manage-pipelines/)

docs/user-guide/Pipelines/Pipelines-in-OpenObserve.md

@@ -2,8 +2,8 @@ In OpenObserve, pipelines are data processing workflows used to transform logs,
 
 **Learn more:**
 
-- [Pipelines in OpenObserve](Pipelines-in-OpenObserve.md)
-- [Create and Use Pipelines](Create-and-Use-Pipelines.md)
-- [Import and Export Pipelines](import-and-export-pipelines.md)
-- [Manage Pipelines](Manage-Pipelines.md)
-- [Configurable Delay in Scheduled Pipelines](onfigurable-delay-in-scheduled-pipelines.md)
+- [Pipelines in OpenObserve](../pipelines/pipelines-in-openobserve/)
+- [Create and Use Pipelines](../pipelines/create-and-use-pipelines/)
+- [Import and Export Pipelines](../pipelines/import-and-export-pipelines/)
+- [Manage Pipelines](../pipelines/manage-pipelines/)
+- [Configurable Delay in Scheduled Pipelines](../pipelines/configurable-delay-in-scheduled-pipelines/)

docs/user-guide/Pipelines/configurable-delay-in-scheduled-pipelines.md

@@ -1,9 +1,8 @@
 nav:
     - Alerts Overview: index.md
     - Alerts in OpenObserve: alerts.md
-    - Alert Destinations: destinations.md
     - Alert Folders: alert-folders.md
     - Alert Conditions: alert-conditions.md
     - Import and Export Alerts: import-export-alerts.md
     - Multi-window Selector in Scheduled Alerts (SQL Mode): multi-window-selector-scheduled-alerts-concept.md
-    - Use Multi-window Selector in Scheduled Alerts: multi-window-selector-scheduled-alerts.md
+    - Use Multi-window Selector in Scheduled Alerts: how-to-access-multi-window-selector-scheduled-alerts.md

docs/user-guide/Pipelines/import-and-export-pipelines.md

@@ -16,7 +16,7 @@ To access multi-window selector in new alerts:
 4. Under **Alert Setup**, select **Scheduled Alerts**.   
 5. Navigate to the **Multi-window Selector** section.
 
-![access multi-window](../../images/multi-window.png)
+![access multi-window](../../images/multi-window-period.png)
 
 ### In Existing Alerts
 
@@ -212,7 +212,7 @@ if length(result) >= 2 {
 
 .
 ```
-![vrl editor](../../images/multi-window-5.png)
+![vrl editor](../../images/multi-window-vrl-editor.png)
 
 **Understand the VRL Function Output**
 
@@ -257,7 +257,7 @@ Set the **Threshold** as **>= 1**
 
 Determines how often the alert manager runs the query throughout the day (e.g., every 30 minutes).
 
-![frequency](../../images/multi-window-6.png)
+![frequency](../../images/multi-window-frequency.png)
 
 **Important:**
 
@@ -284,7 +284,7 @@ At 10:30 AM, OpenObserve alert manager executes SQL for:
 
 Specify where you want to receive the alert notification- email or webhook. 
 
-![add destination](../../images/multi-window-4.png)
+![add destination](../../images/multi-window-add-destination.png)
 
 ### Step 8: Create Row Template
 
@@ -310,8 +310,8 @@ Details: Count difference: {{ diff }}
 
 ## FAQ
 
-**What is a window in the Multi-window Selector?** <br>
-A *window* is a specific time range of data. It depends on the period you set in the alert.
+**Q.** **What is a window in the Multi-window Selector?** <br>
+**A.** A *window* is a specific time range of data. It depends on the period you set in the alert.
 If you set the period to 4 hours, each window will cover exactly 4 hours of data.
 
 - The **current window** is simply the most recent 4-hour block of time before the evaluation. If the current time is **April 10th at 4:00 PM**, then the current window covers **April 10th from 12:00 PM to 4:00 PM**.
@@ -320,11 +320,11 @@ If you set the period to 4 hours, each window will cover exactly 4 hours of data
 Every window you select is just a copy of the same time range (defined by the period), shifted back by the amount of time you choose.
 <br>
 
-**Does the period control the window length?**<br>
-Yes. The period defines the duration of each window. If you set the period to 4 hours, then every window — whether it's the current window or any past window — will be exactly 4 hours long.
+**Q.** **Does the period control the window length?**<br>
+**A.** Yes. The period defines the duration of each window. If you set the period to 4 hours, then every window — whether it's the current window or any past window — will be exactly 4 hours long.
 
-**Does the alert manager run multiple queries inside one window?** <br>
-No. For each evaluation, the alert manager runs:
+**Q.** **Does the alert manager run multiple queries inside one window?** <br>
+**A.** No. For each evaluation, the alert manager runs:
 
 - One query for the current window
 - One separate query for each additional past window you select
@@ -337,8 +337,8 @@ For example:
 - If you set frequency to every 12 hours, it runs the queries every 12 hours.
 So, frequency controls when the alert manager checks, and period controls what time range is checked at each evaluation.
 
-**What happens if I forget to include `#ResultArray#` in my VRL function?** <br>
-If you do not include `#ResultArray#`, your VRL function will receive a flat array:**  
+**Q.** **What happens if I forget to include `#ResultArray#` in my VRL function?** <br>
+**A.** If you do not include `#ResultArray#`, your VRL function will receive a flat array:**  
 
 ``` linenums="1"
 [