Apply suggestions from code review

Maddy-Cloudflare · pedrosousa · web-flow · commit 69d55b63b4b2 · 2025-06-18T17:39:31.000+01:00
Co-authored-by: Pedro Sousa &lt;680496+pedrosousa@users.noreply.github.com&gt;
diff --git a/src/content/docs/log-explorer/api.mdx b/src/content/docs/log-explorer/api.mdx
@@ -27,22 +27,21 @@ Authentication with the API can be done via an authentication header or API toke
 
   - `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.
 
-## Manage Datasets
+## 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.
+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>" \
---header "Content-Type: application/json" \
---data '{
+--json '{
   "dataset": "http_requests"
 }'
 ```
 
-```json
+```json output
 {
   "result": {
     "dataset": "http_requests",
@@ -59,13 +58,12 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/explorer/datasets
 }
 ```
 
-If you would like to enable an account-level dataset, replace `zones/{zone_id}` with `accounts/{account_id}` in the curl command. For example:
+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>" \
---header "Content-Type: application/json" \
---data '{
+--json '{
   "dataset": "access_requests"
 }'
 ```
@@ -74,15 +72,15 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/logs/explorer/da
 
 Log Explorer includes a SQL API for submitting queries. 
 
-For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), and use the following SQL query:
+For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
 
 ```bash
 curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/explorer/query/sql \
 --header "Authorization: Bearer <API_TOKEN>" \
 --url-query query="SELECT clientRequestScheme, clientRequestHost, clientRequestMethod, edgeResponseStatus, clientRequestUserAgent FROM http_requests WHERE RayID = '806c30a3cec56817' LIMIT 1"
 ```
 
-Which returns the following HTTP request details:
+This command returns the following HTTP request details:
 
 ```json
 {
@@ -101,15 +99,15 @@ Which returns the following HTTP request details:
 }
 ```
 
-Another example to find Cloudflare Access requests with selected columns from a specific timeframe, you can perform the following SQL query:
+As another example, you could find Cloudflare Access requests with selected columns from a specific timeframe by performing the following SQL query:
 
 ```bash
 curl https://api.cloudflare.com/client/v4/account/{account_id}/logs/explorer/query/sql \
 --header "Authorization: Bearer <API_TOKEN>" \
 --url-query query="SELECT CreatedAt, AppDomain, AppUUID, Action, Allowed, Country, RayID, Email, IPAddress, UserUID FROM access_requests WHERE Date >= '2025-02-06' AND Date <= '2025-02-06' AND CreatedAt >= '2025-02-06T12:28:39Z' AND CreatedAt <= '2025-02-06T12:58:39Z'"
 ```
 
-Which returns the following request details:
+This command returns the following request details:
 
 ```json
 {
diff --git a/src/content/docs/log-explorer/custom-dashboards.mdx b/src/content/docs/log-explorer/custom-dashboards.mdx
@@ -73,7 +73,7 @@ The available metrics and filters vary based on the dataset you want to use. For
 You can also adjust the scope of your analytics by entering filter conditions. This allows you to focus on the most relevant data.
 
 1. Select **Add filter**.
-2. Select a **field**, an **operator**, and a **value**. For example, to filter events by source IP address, select the _Source IP_ field, select the _equals_ operator, and enter the _IP address_.
+2. Select a **field**, an **operator**, and a **value**. For example, to filter events by source IP address, select the _Source IP_ field, select the _equals_ operator, and enter the IP address.
 3. Select **Apply**.
 
 ### Create a dashboard from a template
diff --git a/src/content/docs/log-explorer/index.mdx b/src/content/docs/log-explorer/index.mdx
@@ -11,8 +11,7 @@ import { Description, Feature, RelatedProduct } from "~/components"
 Store and explore your Cloudflare logs directly within the Cloudflare dashboard or API.
 </Description>
 
-
-Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third party tools.
+Log Explorer is Cloudflare's native observability and forensics product that enables security teams and developers to analyze, investigate, and monitor issues directly from the Cloudflare dashboard, without the expense and complexity of forwarding logs to third-party tools.
 
 Log Explorer provides access to Cloudflare logs with all the context available within the Cloudflare platform. You can monitor security and performance issues with custom dashboards or investigate and troubleshoot issues with log search. Benefits include: 
 
@@ -24,11 +23,11 @@ Log Explorer provides access to Cloudflare logs with all the context available w
 ## Features
 
 <Feature header="Log Search" href="/log-explorer/log-search/">
-Search logs enable you to store and explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
+Explore your Cloudflare logs directly within the Cloudflare dashboard or [API](/log-explorer/api/).
 </Feature>
 
 <Feature header="Custom dashboards" href="/log-explorer/custom-dashboards/">
-Custom dashboards enable you to design customized views for tracking application security, performance, and usage metrics.
+Design customized views for tracking application security, performance, and usage metrics.
 </Feature>
 
 <Feature header="Manage datasets" href="/log-explorer/manage-datasets/">
@@ -42,9 +41,9 @@ Manage configuration and perform queries via the API.
 ## Related products
 
 <RelatedProduct header="Logpush" href="/logs/" product="logs">
-Forward Cloudflare logs to third party tools for debugging, identifying configuration adjustments, and creating analytics. 
+Forward Cloudflare logs to third-party tools for debugging, identifying configuration adjustments, and creating analytics dashboards.
 </RelatedProduct>
 
 <RelatedProduct header="Analytics" href="/analytics/" product="analytics">
-Cloudflare visualizes the metadata collected by our products in the Cloudflare dashboard.
+Visualize the metadata collected by our products in the Cloudflare dashboard.
 </RelatedProduct>
diff --git a/src/content/docs/log-explorer/log-search.mdx b/src/content/docs/log-explorer/log-search.mdx
@@ -7,15 +7,15 @@ sidebar:
 
 import { TabItem, Tabs, Render } from "~/components";
 
-Log Explorer enables you to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API. Giving you visibility into your logs without the need to forward them to third parties. Logs are stored on Cloudflare's global network using the R2 object storage platform and can be queried via the Dashboard or SQL API.
+Log Explorer enables you to store and explore your Cloudflare logs directly within the Cloudflare dashboard or API, giving you visibility into your logs without the need to forward them to third-party services. Logs are stored on Cloudflare's global network using the R2 object storage platform and can be queried via the dashboard or SQL API.
 
 ## SQL queries supported
 
-The diagram below displays the example sql grammar for SELECT statements as a railroad syntax diagram:
+The diagram below displays the example sql grammar for `SELECT` statements as a railroad syntax diagram:
 
-![Supported sql grammar](~/assets/images/log-explorer/supported-sql-grammar-graph.png)
+![Supported SQL grammar](~/assets/images/log-explorer/supported-sql-grammar-graph.png)
 
-Any path from left to right forms a valid query. There is a limit of 25 predicates in the `WHERE`  clause. Predicates can be grouped using parenthesis. If the `LIMIT`  clause is not specified, then the default limit of 10000 is applied. The maximum number for the `LIMIT` clause is 10000. Results are returned in descending order by time.
+Any path from left to right forms a valid query. There is a limit of 25 predicates in the `WHERE` clause. Predicates can be grouped using parenthesis. If the `LIMIT` clause is not specified, then the default limit of 10,000 is applied. The maximum number for the `LIMIT` clause is 10,000. Results are returned in descending order by time.
 
 Examples of queries include:
 
@@ -44,11 +44,11 @@ The `ORDER BY` clause is used to sort the result set by one or more columns in a
 
 ### LIMIT
 
-The `LIMIT` clause is used to constrain the number of rows returned by a query. It is often used in conjunction with the `ORDER BY` clause to retrieve the top N rows or to implement pagination.
+The `LIMIT` clause is used to constrain the number of rows returned by a query. It is often used in conjunction with the `ORDER BY` clause to retrieve the top `N` rows or to implement pagination.
 
 :::note
 
-Log Explorer does not support `JOINs`, `DDL`, `DML`, or `EXPLAIN` queries.
+Log Explorer does not support `JOIN`, `DDL`, `DML`, or `EXPLAIN` queries.
 
 :::
 
@@ -57,7 +57,7 @@ Log Explorer does not support `JOINs`, `DDL`, `DML`, or `EXPLAIN` queries.
 You can filter and view your logs via the Cloudflare dashboard or the API.
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Go to  **Log Explorer** > **Log Search**.
+2. Go to **Log Explorer** > **Log Search**.
 3. Select the **Dataset** you want to use and in **Columns** select the dataset fields. If you selected a zone scoped dataset, select the zone you would like to use.
 4. Enter a **Limit**. A limit is the maximum number of results to return, for example, 50.
 5. Select the **Time period** from which you want to query, for example, the previous 12 hours.
@@ -73,47 +73,41 @@ You can filter and view your logs via the Cloudflare dashboard or the API.
 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
-	SELECT 
-		clientRequestScheme, 
-		clientRequestHost, 
-		clientRequestMethod, 
-		edgeResponseStatus, 
-		clientRequestUserAgent 
-	FROM http_requests 
-	WHERE RayID = '806c30a3cec56817' 
-	LIMIT 1
+SELECT 
+	clientRequestScheme, 
+	clientRequestHost, 
+	clientRequestMethod, 
+	edgeResponseStatus, 
+	clientRequestUserAgent 
+FROM http_requests 
+WHERE RayID = '806c30a3cec56817' 
+LIMIT 1
 ```
 
 
-Another example to find Cloudflare Access requests with selected columns from a specific timeframe, you can perform the following SQL query:
+As another example, to find Cloudflare Access requests with selected columns from a specific timeframe you could perform the following SQL query:
 
 ```sql
-	SELECT 
-  		CreatedAt, 
-		AppDomain, 
-		AppUUID, 
-		Action, 
-		Allowed, 
-		Country, 
-		RayID, 
-		Email, 
-		IPAddress, 
-		UserUID 
-	FROM access_requests 
-	WHERE Date >= '2025-02-06' AND Date <= '2025-02-06' AND CreatedAt >= '2025-02-06T12:28:39Z' AND CreatedAt <= '2025-02-06T12:58:39Z'
+SELECT 
+	CreatedAt, 
+	AppDomain, 
+	AppUUID, 
+	Action, 
+	Allowed, 
+	Country, 
+	RayID, 
+	Email, 
+	IPAddress, 
+	UserUID 
+FROM access_requests 
+WHERE Date >= '2025-02-06' AND Date <= '2025-02-06' AND CreatedAt >= '2025-02-06T12:28:39Z' AND CreatedAt <= '2025-02-06T12:58:39Z'
 ```
 
-
-
-
-
-
-
 ### Save queries
 
 After selecting all the fields for your query, you can save it by selecting **Save query**. Provide a name and description to help identify it later. To view your saved and recent queries, select **Queries** — they will appear in a side panel where you can insert a new query, or delete any query.
 
-## Integrated with Security Analytics
+## Integration with Security Analytics
 
 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.
 
@@ -124,26 +118,27 @@ You can also access the Log Explorer dashboard directly from the [Security Analy
 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 `=`.
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Go to  **Log Explorer** > **Log Search** > **Custom SQL**.
+2. Go to **Log Explorer** > **Log Search** > **Custom SQL**.
 3. Enter the following SQL query:
 
 ```sql
-	SELECT 
-		clientip, 
-		clientrequesthost, 
-		clientrequestmethod, 
-		clientrequesturi, 
-		edgeendtimestamp, 
-		edgeresponsestatus, 
-		originresponsestatus, 
-		edgestarttimestamp, 
-		rayid, 
-		clientcountry, 
-		clientrequestpath, date
-	FROM 
-		http_requests
-	WHERE 
-		date = '2023-10-12' LIMIT 500
+SELECT
+	clientip, 
+	clientrequesthost, 
+	clientrequestmethod, 
+	clientrequesturi, 
+	edgeendtimestamp, 
+	edgeresponsestatus, 
+	originresponsestatus, 
+	edgestarttimestamp, 
+	rayid, 
+	clientcountry, 
+	clientrequestpath, 
+	date
+FROM 
+	http_requests
+WHERE 
+	date = '2023-10-12' LIMIT 500
 ```
 
 ### Additional query optimization tips
@@ -156,7 +151,7 @@ All the tables supported by Log Explorer contain a special column called `date`,
 
 ### Which fields (or columns) are available for querying?
 
-All fields listed in the datasets [Log Fields](/logs/reference/log-fields/) are viewable in Log Explorer. For filtering, only fields with simple values, such as those of type `bool`, `int`, `float`, or `string` are supported. Fields with key-value pairs are currently not supported. For example, you cannot use the fields `RequestHeaders` and `Cookies` from the HTTP requests dataset in a filter.
+All fields listed in [Log Fields](/logs/reference/log-fields/) for the [supported datasets](/log-explorer/manage-datasets/#supported-datasets) are viewable in Log Explorer. For filtering, only fields with simple values, such as those of type `bool`, `int`, `float`, or `string` are supported. Fields with key-value pairs are currently not supported. For example, you cannot use the fields `RequestHeaders` and `Cookies` from the HTTP requests dataset in a filter.
 
 ### Why does my query not complete or time out?
 
diff --git a/src/content/docs/log-explorer/manage-datasets.mdx b/src/content/docs/log-explorer/manage-datasets.mdx
@@ -11,12 +11,11 @@ Log Explorer allows you to enable or disable which datasets are available to que
 
 ## Supported datasets
 
-Log Explorer currently supports:
+Log Explorer currently supports the following datasets:
 
 - [HTTP requests](/logs/reference/log-fields/zone/http_requests/) (`FROM http_requests`)
 - [Firewall events](/logs/reference/log-fields/zone/firewall_events/) (`FROM firewall_events`)
 
-
 ## Enable Log Explorer
 
 In order for Log Explorer to begin storing logs, you need to enable the desired datasets. You can do this via the dashboard or the API.
@@ -30,20 +29,19 @@ In order for Log Explorer to begin storing logs, you need to enable the desired
 It may take a few minutes for the logs to become available for querying.
 :::
 
-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.
+If you are using the API, 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.
+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>" \
---header "Content-Type: application/json" \
---data '{
+--json '{
   "dataset": "http_requests"
 }'
 ```
 
-```json
+```json output
 {
   "result": {
     "dataset": "http_requests",
@@ -60,13 +58,12 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/explorer/datasets
 }
 ```
 
-If you would like to enable an account-level dataset, replace `zones/{zone_id}` with `accounts/{account_id}` in the curl command. For example:
+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>" \
---header "Content-Type: application/json" \
---data '{
+--json '{
   "dataset": "access_requests"
 }'
 ```
