update docs

Author: DebashisBorgohainO2

docs/.pages

@@ -1,8 +1,6 @@
 nav:
 - Introduction: index.md
-- Downloads: downloads.md
 - Getting started: getting-started.md
-- Screenshots: screenshots.md
 - Quickstart: quickstart.md
 - Enterprise Edition Installation Guide: openobserve-enterprise-edition-installation-guide.md
 - Releases: releases.md

docs/user-guide/.pages

@@ -2,17 +2,14 @@ nav:
     - Concepts: concepts.md
     - Log Search: logs
     - Metrics: metrics
-    - Real User Monitoring (RUM): rum.md
-    - Organizations: organizations.md
-    - Users: users.md
     - Streams: streams
     - Ingestion: ingestion.md
     - Pipelines: Pipelines
     - Alerts: alerts
     - Dashboards: dashboards
     - Actions: actions
     - Functions: functions
-    - Migration: migration
+    - Real User Monitoring (RUM): rum.md
     - Identity and Access Management (IAM): identity-and-access-management
     - Management: management
     - Profile: profile

docs/user-guide/management/alert-destinations.md

@@ -19,7 +19,7 @@ Webhooks are ideal for integrating OpenObserve alerts with third-party platforms
 4. Fill the following sections:
 
     - **Name**: Enter a descriptive name for the Webhook destination such as **SlackNotifications**. 
-    > Note: Characters like :, ?, /, #, and spaces are not allowed.
+    > **Note**: Characters like :, ?, /, #, and spaces are not allowed.
     - **Template**: Choose a template from the dropdown menu. Refer to [Templates](templates.md) to create or manage templates.
     - **URL**: Specify the Webhook endpoint URL where notifications will be sent.
     - **Method**: Select the HTTP method depending on the Webhook's requirements.
@@ -31,17 +31,16 @@ Webhooks are ideal for integrating OpenObserve alerts with third-party platforms
 
 ![alert destination](../../images/alert-destination-webhook-slack.png)
 
-### Example
+!!! Note "Example"
+    - **Name**: Slack Alerts  
+    - **Template**: SlackTemplate  
+    - **URL**: `https://hooks.slack.com/services/T02QBH105PF/B04C7NLLLRE/HY3fXf123`  
+    - **Method**: POST
+    - **Output Format**: JSON  
+    - **Headers**: 
 
-- **Name**: Slack Alerts  
-- **Template**: SlackTemplate  
-- **URL**: `https://hooks.slack.com/services/T02QBH105PF/B04C7NLLLRE/HY3fXf123`  
-- **Method**: POST
-- **Output Format**: JSON  
-- **Headers**: 
-
-    - **Key**: Authorization  
-    - **Value**: Basic cm9vdEBleGFtcGxlLmNvbTpDb21wbGV4GFzcy  
+        - **Key**: Authorization  
+        - **Value**: Basic cm9vdEBleGFtcGxlLmNvbTpDb21wbGV4GFzcy  
 
 
 ## Configure Email Destinations
@@ -58,11 +57,10 @@ Email destinations are used for delivering alert notifications directly to speci
 5. Click **Save** to create the Email destination.
 
 
-### Example
-
-- **Name**: Critical Alerts  
-- **Template**: EmailTemplate  
-- **Recipients**: `[email protected]; [email protected]`  
+!!! Note "Example"
+    - **Name**: Critical Alerts  
+    - **Template**: EmailTemplate  
+    - **Recipients**: `[email protected]; [email protected]`  
 
 ## Additional Notes
 ![list_Destinations](../../images/destinations/4.jpg)
@@ -80,20 +78,20 @@ By following this guide, you can set up Webhook and Email destinations to ensure
 To send email alerts, OpenObserve requires SMTP configuration. This can be done by setting the appropriate environment variables when starting OpenObserve.
 
 
-#### Start OpenObserve with SMTP Configuration
+### Start OpenObserve with SMTP Configuration
 
 Use the following command to configure OpenObserve to send email alerts via Gmail:
 
 ```bash
-ZO_SMTP_ENABLED=true \
-ZO_SMTP_HOST="smtp.gmail.com" \
-ZO_SMTP_PORT=587 \
-ZO_SMTP_USER_NAME="your-user-name" \
-ZO_SMTP_PASSWORD="your-app-password" \
-ZO_SMTP_FROM_EMAIL="your-email-address" \
-ZO_SMTP_ENCRYPTION="starttls" \
-ZO_ROOT_USER_EMAIL="[email protected]" \
-ZO_ROOT_USER_PASSWORD="Complexpass#123" \
+ZO_SMTP_ENABLED=true 
+ZO_SMTP_HOST="smtp.gmail.com" 
+ZO_SMTP_PORT=587 
+ZO_SMTP_USER_NAME="your-user-name" 
+ZO_SMTP_PASSWORD="your-app-password" 
+ZO_SMTP_FROM_EMAIL="your-email-address" 
+ZO_SMTP_ENCRYPTION="starttls" 
+ZO_ROOT_USER_EMAIL="[email protected]" 
+ZO_ROOT_USER_PASSWORD="Complexpass#123" 
 ./openobserve
 ```
 Replace the placeholders (your-email-address, your-app-password, etc.) with your actual SMTP details.

docs/user-guide/management/cipher-keys.md

@@ -8,7 +8,7 @@ Follow these steps to create and configure Cipher Keys in OpenObserve:
 
 ### Step 1: Navigate to the Cipher Keys Section
 
-1. From the top navigation bar, click the gear icon (**Management**).  
+1. From the top navigation bar, click the gear icon to open the **Management** page.  
 2. Select **Cipher Keys**.
 
 ![cipher-keys](../../images/cipher-keys1.png)
@@ -43,7 +43,9 @@ After you have filled in all the details, click **Save**. Your new Cipher Key is
 
 After creating the Cipher Key, write queries using the `decrypt()` function in the following formats to decrypt encrypted logs:
 
-```SELECT decrypt (<field name which is encrypted>, ‘<Name of the Cipher Key>’ ) as <name the decrypted log field> from <stream name>;```
+```
+SELECT decrypt (<field name which is encrypted>, ‘<Name of the Cipher Key>’ ) as <name the decrypted log field> from <stream name>;
+```
 
 Let’s say you have the following setup:
 
@@ -53,13 +55,24 @@ Let’s say you have the following setup:
 - You want to name the decrypted field `decrypted_user_data` in the query results.
 
 The query to decrypt and retrieve the logs would look like this:  
-```SELECT decrypt(user_data, 'user_data_decryption_key') as decrypted_user_data FROM user_activity_stream;```
+```
+SELECT decrypt(user_data, 'user_data_decryption_key') as decrypted_user_data FROM user_activity_stream;
+```
 
 Additionally, you can use the `decrypt()` function:
 
-- **With the WHERE clause**: The following query retrieves the `user_id` from the `user_activity_stream` where the decrypted `user_data` matches the string '`John Doe`':  ```Select user_id from user_activity_stream where decrypt(user_data,'user_data_decryption_key') = 'John Doe';``` 
-- **With match* functions**: The following query will decrypt the `user_data` field using the `user_data_decryption_key` and match the decrypted value with `'John’:` ```SELECT user_id FROM user_activity_stream WHERE str_match_all(decrypt(user_data, 'user_data_decryption_key'), 'John Doe’);```  
-- **With the LIKE clause**: This query will decrypt the `user_data` field using the `user_data_decryption_key` and return results where the decrypted data contains the substring '`John`': ```SELECT user_id FROM user_activity_stream WHERE decrypt(user_data, 'user_data_decryption_key') LIKE '%John%';```
+- **With the WHERE clause**: The following query retrieves the `user_id` from the `user_activity_stream` where the decrypted `user_data` matches the string '`John Doe`':  
+```
+Select user_id from user_activity_stream where decrypt(user_data,'user_data_decryption_key') = 'John Doe';
+``` 
+- **With match* functions**: The following query will decrypt the `user_data` field using the `user_data_decryption_key` and match the decrypted value with `'John’`: 
+```
+SELECT user_id FROM user_activity_stream WHERE str_match_all(decrypt(user_data, 'user_data_decryption_key'), 'John Doe’);
+```  
+- **With the LIKE clause**: This query will decrypt the `user_data` field using the `user_data_decryption_key` and return results where the decrypted data contains the substring '`John`': 
+```
+SELECT user_id FROM user_activity_stream WHERE decrypt(user_data, 'user_data_decryption_key') LIKE '%John%';
+```
 
 **Note:** 
 

docs/user-guide/metrics/downsampling-metrics.md

@@ -8,8 +8,10 @@ Downsampling summarizes historical data into fewer data points. Each summarized
 
 Downsampling is configured using the following environment variables.:
 
-- `O2_COMPACT_DOWNSAMPLING_INTERVAL`: Defines how often the downsampling job runs (interval), in seconds. <br>**Example:** `O2_COMPACT_DOWNSAMPLING_INTERVAL`: "300" (this downsampling job runs every 5 minutes)  
-- `O2_METRICS_DOWNSAMPLING_RULES`: Specifies which data streams to target and how they should be downsampled using defined rules. You can add a comma-separated list of rules.<br>**Example:** `O2_METRICS_DOWNSAMPLING_RULES`: "o2_cpu_usage:avg:30d:5m, app_analytics:last:10d:10m"
+- `O2_COMPACT_DOWNSAMPLING_INTERVAL`: Defines how often the downsampling job runs or the interval, in seconds. 
+> For example, `O2_COMPACT_DOWNSAMPLING_INTERVAL`: "300", this downsampling job runs every 5 minutes.  
+- `O2_METRICS_DOWNSAMPLING_RULES`: Specifies which data streams to target and how they should be downsampled using defined rules. You can add a comma-separated list of rules.
+> For example, `O2_METRICS_DOWNSAMPLING_RULES`: "o2_cpu_usage:avg:30d:5m, app_analytics:last:10d:10m"
 
 > Refer to the [Downsampling Rule](#downsampling-rule) section. <br> 
 
@@ -56,9 +58,9 @@ Here:
 - **offset**: It defines the age of data eligible for downsampling. For example, 15d for applying downsampling on data older than 15 days.  
 - **step**: The time block used to group data points. For example, 30m for applying downsampling to retain one value every 30 minutes.
 
-#### Sample Downsampling Rules
+### Sample Downsampling Rules
 
-##### Single Rule
+#### Single Rule
 ```yaml
 O2_METRICS_DOWNSAMPLING_RULES: "o2_cpu_metrics:avg:30d:5m"
 ```

docs/user-guide/performance/download-manager.md

@@ -143,7 +143,7 @@ The following examples illustrate how files are assigned to the priority or norm
             The querier does not begin processing the search query until all required files, regardless of whether they were downloaded via the Priority or Normal Queue.
 
 
-## Frequently Asked Questions (FAQ)
+## Frequently Asked Questions 
 
 **Q. My query includes both recent and old data. Do I get results faster with the new system?** <br>
 **A.** Yes. Files within the configured priority window are downloaded immediately. This helps reduce total wait time, even though the query waits for all required files.

docs/user-guide/performance/monitor-download-queue-size-and-disk-cache-metrics.md

@@ -11,7 +11,6 @@ OpenObserve emits four key metrics that track how data files are downloaded and
 - `zo_file_downloader_priority_queue_size`: Number of files in the [**priority** queue](download-manager.md/#dual-queue-system). 
 
 - `zo_query_disk_cache_hit_count`: Number of files that were already on disk when the query was executed. 
-
 - `zo_query_disk_cache_miss_count`: Number of files that were not on disk and had to be downloaded before the query could run.
 
 !!! Note
@@ -167,4 +166,4 @@ If the metrics do not appear:
 
 - Verify that `ZO_SELF_METRIC_CONSUMPTION_ENABLED` is set to **true**.
 - Check that `ZO_SELF_METRIC_CONSUMPTION_ACCEPTLIST` includes all the relevant metric names.
-- Confirm that your dashboard filters match the environment where metrics are enabled (e.g., `main`, `usertest`, etc.)
+- Confirm that your dashboard filters match the environment where metrics are enabled. For example, `main`, `usertest`, etc.

docs/user-guide/streams/stream-details.md

@@ -1,5 +1,5 @@
-After [learning about streams](streams-in-openobserve.md) and [completing the data ingestion](streams-in-openobserve.md/#ingest-data-into-stream), you can view detailed information about a stream. 
-This guide explains how to access the Stream Details panel and the information available in the panel. 
+After data [ingestion is complete](streams-in-openobserve.md/#ingest-data-into-stream), you can view detailed information about a stream using the **Stream Details** panel. 
+This guide explains how to access the **Stream Details** panel and the information available in the panel. 
 
 ## Access