Addressing Pedro suggestions

Author: Maddy-Cloudflare

src/content/docs/log-explorer/api.mdx

@@ -16,57 +16,7 @@ Log Explorer is available to users with the following permissions:
 
 Note that these permissions exist at the account and zone level and you need the appropriate permission level for the datasets you wish to query.
 
-Authentication with the API can be done via an authentication header or API token. Append your API call with either of the following additional parameters.
-
-- **Authentication header**
-
-  - `X-Auth-Email` - the Cloudflare account email address associated with the domain
-  - `X-Auth-Key` - the Cloudflare API key
-
-- **API token**
-
-  - `Authorization: Bearer <API_TOKEN>` To create an appropriately scoped API token, refer to [Create API token](/fundamentals/api/get-started/create-token/) documentation. Copy and paste the token into the authorization parameter for your API call.
-
-## Enable datasets
-
-Use the Log Explorer API to enable Log Explorer for each dataset you wish to store. It may take a few minutes after a log stream is enabled before you can view the logs.
-
-The following `curl` command is an example for enabling the zone-level dataset `http_requests`, as well as the expected response when the command succeeds.
-
-```bash
-curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/explorer/datasets \
---header "Authorization: Bearer <API_TOKEN>" \
---json '{
-  "dataset": "http_requests"
-}'
-```
-
-```json output
-{
-  "result": {
-    "dataset": "http_requests",
-    "object_type": "zone",
-    "object_id": "<ZONE ID>",
-    "created_at": "2025-06-03T14:33:16Z",
-    "updated_at": "2025-06-03T14:33:16Z",
-    "dataset_id": "01973635f7e273a1964a02f4d4502499",
-    "enabled": true
-  },
-  "success": true,
-  "errors": [],
-  "messages": []
-}
-```
-
-If you would like to enable an account-level dataset, replace `zones/{zone_id}` with `accounts/{account_id}` in the `curl` command. For example:
-
-```bash
-curl https://api.cloudflare.com/client/v4/accounts/{account_id}/logs/explorer/datasets \
---header "Authorization: Bearer <API_TOKEN>" \
---json '{
-  "dataset": "access_requests"
-}'
-```
+Authentication with the API can be done via an API token or API key with an email. Refer to [Create API token](/fundamentals/api/get-started/create-token/) for further instructions.
 
 ## Query data
 

src/content/docs/log-explorer/custom-dashboards.mdx

@@ -9,6 +9,7 @@ Custom dashboards allow you to create tailored dashboards to monitor application
 
 :::note
 Enterprise customers can create up to 100 dashboards.
+
 Customers on Pro and Business plans can create up to 5 dashboards.
 :::
 
@@ -25,8 +26,8 @@ To create a new dashboard:
 
 When creating a dashboard, you have two options: building one from scratch or using a pre-designed template.
 
-- A **from-scratch dashboard** gives you full control over its structure, allowing you to choose the exact datasets, metrics, and visualizations that fit your needs. This approach is ideal if you have specific monitoring goals or need a highly customized view of your data.
-- On the other hand, **templates** provide a faster way to set up a dashboard with commonly used metrics and charts. They are useful for standard use cases, such as monitoring security threats, API performance, or bot traffic. Templates help you get started quickly while still allowing modifications to fit your requirements.
+- A **templates** provide a faster way to set up a dashboard with commonly used metrics and charts. They are useful for standard use cases, such as monitoring security threats, API performance, or bot traffic. Templates help you get started quickly while still allowing modifications to fit your requirements.
+- On the other hand, **from-scratch dashboard** gives you full control over its structure, allowing you to choose the exact datasets, metrics, and visualizations that fit your needs. This approach is ideal if you have specific monitoring goals or need a highly customized view of your data.
 
 Choosing between these options depends on whether you need a quick setup with predefined insights or a fully customized dashboard tailored to your unique analysis needs.
 

src/content/docs/log-explorer/log-search.mdx

@@ -65,11 +65,6 @@ You can filter and view your logs via the Cloudflare dashboard or the API.
 7. A query preview is displayed. Select **Custom SQL** to change the query.
 8. Select **Run query** when you are done. The results are displayed below within the **Query results** section.
 
-:::note
-
-
-
-
 For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), go to **Custom SQL**, and enter the following SQL query:
 
 ```sql
@@ -111,8 +106,6 @@ After selecting all the fields for your query, you can save it by selecting **Sa
 
 You can also access the Log Explorer dashboard directly from the [Security Analytics dashboard](/waf/analytics/security-analytics/#logs). When doing so, the filters you applied in Security Analytics will automatically carry over to your query in Log Explorer.
 
-:::
-
 ## Optimize your queries
 
 All the tables supported by Log Explorer contain a special column called `date`, which helps to narrow down the amount of data that is scanned to respond to your query, resulting in faster query response times. The value of `date` must be in the form of `YYYY-MM-DD`. For example, to query logs that occurred on October 12, 2023, add the following to your `WHERE` clause: `date = '2023-10-12'`. The column supports the standard operators of `<`, `>`, and `=`.
@@ -157,8 +150,6 @@ All fields listed in [Log Fields](/logs/reference/log-fields/) for the [supporte
 
 Log Explorer performs best when query parameters focus on narrower ranges of time. You may experience query timeouts when your query would return a large quantity of data. Consider refining your query to improve performance.
 
-If your query times out with an HTTP status of 524 (Gateway Timeout), consider using one of the [streaming output formats](/logs/log-explorer/#output-formats), such as `application/x-ndjson`.
-
 ### Why don't I see any logs in my queries after enabling the dataset?
 
 Log Explorer starts ingesting logs from the moment you enable the dataset. It will not display logs for events that occurred before the dataset was enabled. Make sure that new events have been generated since enabling the dataset, and check again.