diff --git a/docs/en/observability/categorize-logs.asciidoc b/docs/en/observability/categorize-logs.asciidoc
index 76af9c4c48..4162f3d128 100644
--- a/docs/en/observability/categorize-logs.asciidoc
+++ b/docs/en/observability/categorize-logs.asciidoc
@@ -32,7 +32,7 @@ message categories, and detects unusually high message counts in the categories.
    log rate categorizations.
 2. Choose a time range for the {ml} analysis. By default, the {ml} job analyzes
    log messages no older than four weeks and continues indefinitely.
-3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the log sources advanced setting. Update this setting by going to *Management* → *Advanced Settings* and searching for _logs sources_.
+3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the *logs source* advanced setting. Update this setting by going to *Management* → *Advanced Settings* and searching for _logs source_.
 4. Click *Create ML job*. The job is created, and it starts to run. It takes a few
    minutes for the {ml} robots to collect the necessary data. After the job
    processed the data, you can view the results.
diff --git a/docs/en/observability/explore-logs.asciidoc b/docs/en/observability/explore-logs.asciidoc
index 5ee8594d05..f2ffdaa7cb 100644
--- a/docs/en/observability/explore-logs.asciidoc
+++ b/docs/en/observability/explore-logs.asciidoc
@@ -22,8 +22,8 @@ Viewing data in Logs Explorer requires `read` privileges for *Discover* and *Int
 [[find-your-logs]]
 == Find your logs
 
-By default, Logs Explorer shows all of your logs, according to the index patterns set in the *log sources* advanced setting.
-Update this setting by going to *Stack Management* → *Advanced Settings* and searching for _logs sources_.
+By default, Logs Explorer shows all of your logs, according to the index patterns set in the *logs source* advanced setting.
+Update this setting by going to *Stack Management* → *Advanced Settings* and searching for __.
 
 If you need to focus on logs from a specific integration, select the integration from the logs menu:
 
diff --git a/docs/en/observability/inspect-log-anomalies.asciidoc b/docs/en/observability/inspect-log-anomalies.asciidoc
index 8790f716bc..985b586086 100644
--- a/docs/en/observability/inspect-log-anomalies.asciidoc
+++ b/docs/en/observability/inspect-log-anomalies.asciidoc
@@ -35,7 +35,7 @@ Create a {ml} job to detect anomalous log entry rates automatically.
 
 1. Select *Anomalies*, and you'll be prompted to create a {ml} job which will carry out the log rate analysis.
 2. Choose a time range for the {ml} analysis.
-3. Add the Indices that contain the logs you want to analyze.
+3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the *logs source* advanced setting. Update this setting by going to *Management* → *Advanced Settings* and searching for _logs source_.
 4. Click *Create {ml-init} job*.
 5. You're now ready to explore your log partitions.
 
diff --git a/docs/en/serverless/logging/view-and-monitor-logs.mdx b/docs/en/serverless/logging/view-and-monitor-logs.mdx
index f1928fc7e2..a1e1e68c4a 100644
--- a/docs/en/serverless/logging/view-and-monitor-logs.mdx
+++ b/docs/en/serverless/logging/view-and-monitor-logs.mdx
@@ -22,8 +22,8 @@ For more on assigning Kibana privileges, refer to the [((kib)) privileges](((kib
 
 ## Find your logs
 
-By default, Logs Explorer shows all of your logs according to the index patterns set in the *log sources* advanced setting.
-Update this setting by going to *Management* → *Advanced Settings* and searching for _logs sources_.
+By default, Logs Explorer shows all of your logs according to the index patterns set in the **logs source** advanced setting.
+Update this setting by going to *Management* → *Advanced Settings* and searching for _logs source_.
 
 If you need to focus on logs from a specific integrations, select the integration from the logs menu: