diff --git a/docs/user/alerting/action-types/jira.asciidoc b/docs/user/alerting/action-types/jira.asciidoc
index 02f2a9be89254..0740cf7838b15 100644
--- a/docs/user/alerting/action-types/jira.asciidoc
+++ b/docs/user/alerting/action-types/jira.asciidoc
@@ -66,7 +66,7 @@ API token (or password)::  Jira API authentication token (or password) for HTTP
 Jira actions have the following configuration properties:
 
 Subaction::        The subaction to perform: `pushToService`, `getIncident`, `issueTypes`, `fieldsByIssueType`, `issues`, `issue`, or `getFields`.
-Subaction Params:: The parameters of the subaction.
+Subaction params:: The parameters of the subaction.
 
 ==== `pushToService` subaction configuration
 
diff --git a/docs/user/alerting/action-types/resilient.asciidoc b/docs/user/alerting/action-types/resilient.asciidoc
index 4b0b0a9730a2c..dfa95e2deec00 100644
--- a/docs/user/alerting/action-types/resilient.asciidoc
+++ b/docs/user/alerting/action-types/resilient.asciidoc
@@ -66,7 +66,7 @@ API key secret::  The authentication key secret for HTTP Basic authentication.
 IBM Resilient actions have the following configuration properties:
 
 Subaction::        The subaction to perform: `pushToService`, `getFields`, `incidentTypes`, or `severity`.
-Subaction Params:: The parameters of the subaction.
+Subaction params:: The parameters of the subaction.
 
 ==== `pushToService` subaction configuration
 
diff --git a/docs/user/alerting/action-types/servicenow.asciidoc b/docs/user/alerting/action-types/servicenow.asciidoc
index 1e4923a7d449e..d1ee1b9357737 100644
--- a/docs/user/alerting/action-types/servicenow.asciidoc
+++ b/docs/user/alerting/action-types/servicenow.asciidoc
@@ -61,7 +61,7 @@ Password::  Password for HTTP Basic authentication.
 ServiceNow actions have the following configuration properties:
 
 Subaction::        The subaction to perform: `pushToService`, `getFields`, `getIncident`, or `getChoices`.
-Subaction Params:: The parameters of the subaction.
+Subaction params:: The parameters of the subaction.
 
 ==== `pushToService` subaction configuration
 
diff --git a/x-pack/plugins/actions/README.md b/x-pack/plugins/actions/README.md
index 6546f625af889..6606d5e0aafcd 100644
--- a/x-pack/plugins/actions/README.md
+++ b/x-pack/plugins/actions/README.md
@@ -118,7 +118,7 @@ Built-In-Actions are configured using the _xpack.actions_ namespace under _kiban
 
 - You can use the string "*" in the **allowedHosts** configuration in place of a specific hostname to enable Kibana to target any URL, but keep in mind the potential to use such a feature to execute [SSRF](https://www.owasp.org/index.php/Server_Side_Request_Forgery) attacks from your server.
 
-- The **allowedHosts** configuration applies to built-in action types (such as Slack, or PagerDuty) as well. Uniquely, the _PagerDuty Action Type_ has been configured to support the service's Events API (at _https://events.pagerduty.com/v2/enqueue_, which you can read about [here](https://v2.developer.pagerduty.com/docs/events-api-v2)) as a default, but this too, must be included in the allowedHosts before the PagerDuty action can be used.
+- The **allowedHosts** configuration applies to built-in action types (such as Slack and PagerDuty). While the _PagerDuty Action Type_ has been configured to support the service's Events API (at _https://events.pagerduty.com/v2/enqueue_, which you can read about in [Pagerduty's documentation](https://v2.developer.pagerduty.com/docs/events-api-v2)), the PagerDuty domain must still be included in the allowedHosts configuration before the action can be used.
 
 ### Configuration Utilities