Editorial changes

Author: charlotte-hoblik

docs/reference/release-notes/8.19.0.asciidoc

@@ -17,7 +17,7 @@ Discovery-Plugins::
 The `discovery-ec2` plugin now uses AWS SDK v2 instead of v1, as AWS plans to deprecate SDK v1 before the end of Elasticsearch 8.19’s support period. AWS SDK v2 introduces several behavior changes that affect configuration.
 
 **Impact:**
-If you use the `discovery-ec2` plugin, your existing settings may no longer be compatible. Notable changes include but not limited to:
+If you use the `discovery-ec2` plugin, your existing settings may no longer be compatible. Notable changes include, but may not be limited to:
 
 * AWS SDK v2 does not support the EC2 IMDSv1 protocol.
 * AWS SDK v2 does not support the `aws.secretKey` or `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system properties.
@@ -30,7 +30,7 @@ Test the upgrade in a non-production environment. Adapt your configuration to th
 * If you use IMDS to determine the availability zone of a node or to obtain credentials for accessing the EC2 API, ensure that it supports the IMDSv2 protocol.
 * If applicable, discontinue use of the `aws.secretKey` and `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system properties.
 * If applicable, specify that you wish to use the insecure HTTP protocol to access the EC2 API by setting `discovery.ec2.endpoint` to a URL which starts with `http://`.
-* Either supply both an access key and a secret key using the keystore settings `discovery.ec2.access_key` and `discovery.ec2.secret_key`, or configure neither of these settings.
+* Either supply both an access key and a secret key using the `discovery.ec2.access_key` and `discovery.ec2.secret_key` keystore settings, or configure neither of these settings.
 
 For more information, view {es-pull}122062[#122062].
 ===============
@@ -109,22 +109,22 @@ Snapshot/Restore::
 The `repository-s3` plugin now uses AWS SDK v2 instead of v1, as AWS will deprecate SDK v1 before the end of Elasticsearch 8.19’s support period. The two SDKs differ in behavior, which may require updates to your configuration.
 
 **Impact:**
-Existing `repository-s3` configurations may no longer be compatible. Notable differences in AWS SDK v2 include but not limited to:
+Existing `repository-s3` configurations may no longer be compatible. Notable differences in AWS SDK v2 include, but may not be limited to:
 
-* AWS SDK v2 requires users to specify the region to use for signing requests, or else to run in an environment in which it can determine the correct region automatically. The older SDK would try to determine the region based on the endpoint URL as specified with the `s3.client.${CLIENT_NAME}.endpoint` setting, together with other data drawn from the operating environment, and would ultimately fall back to `us-east-1` if no better value could be found.
+* AWS SDK v2 requires users to specify the region to use for signing requests, or else to run in an environment in which it can determine the correct region automatically. The older SDK used to determine the region based on the endpoint URL as specified with the `s3.client.${CLIENT_NAME}.endpoint` setting, together with other data drawn from the operating environment, and fell back to `us-east-1` if no better value was found.
 * AWS SDK v2 does not support the EC2 IMDSv1 protocol.
 * AWS SDK v2 does not support the `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
 * AWS SDK v2 does not permit specifying a choice between HTTP and HTTPS so the `s3.client.${CLIENT_NAME}.protocol` setting is deprecated and no longer has any effect.
-* AWS SDK v2 does not permit control over throttling for retries, so the the `s3.client.${CLIENT_NAME}.use_throttle_retries` setting is deprecated and no longer has any effect.
-* AWS SDK v2 requires the use of the V4 signature algorithm, so the `s3.client.${CLIENT_NAME}.signer_override` setting is deprecated and no longer has any effect.
+* AWS SDK v2 does not permit control over throttling for retries, so the `s3.client.${CLIENT_NAME}.use_throttle_retries` setting is deprecated and no longer has any effect.
+* AWS SDK v2 requires the use of the V4 signature algorithm, therefore, the `s3.client.${CLIENT_NAME}.signer_override` setting is deprecated and no longer has any effect.
 * AWS SDK v2 does not support the `log-delivery-write` canned ACL.
 * AWS SDK v2 counts 4xx responses differently in its metrics reporting.
 * AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2 could use either a regional endpoint or the global `https://sts.amazonaws.com` one.
 
 **Action:**
 Test the upgrade in a non-production environment. Adapt your configuration to the new SDK functionality. This includes, but may not be limited to, the following items:
 
-* Specify the correct signing region using the `s3.client.${CLIENT_NAME}.region` setting on each node. {es} will try and determine the correct region based on the endpoint URL and other data drawn from the operating environment but cannot guarantee to do so correctly in all cases.
+* Specify the correct signing region using the `s3.client.${CLIENT_NAME}.region` setting on each node. {es} will try to determine the correct region based on the endpoint URL and other data drawn from the operating environment, but might not do so correctly in all cases.
 * If you use IMDS to determine the availability zone of a node or to obtain credentials for accessing the EC2 API, ensure that it supports the IMDSv2 protocol.
 * If applicable, discontinue use of the `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
 * If applicable, specify that you wish to use the insecure HTTP protocol to access the S3 API by setting `s3.client.${CLIENT_NAME}.endpoint` to a URL which starts with `http://`.