rm 'add additional' phrase from docs (#1020)

* rm 'add additional' phrase from docs * these > more
2026-09-25 12:38:05 +00:00 · 2023-12-06 18:35:48 -05:00
parent 9bcdc440c5
commit e479cc33e3
82 changed files with 98 additions and 98 deletions
@@ -74,7 +74,7 @@ To get your own custom application metrics into Prometheus, you have to collect

 ### ServiceMonitors and PodMonitors

-Once all your workloads expose metrics in a Prometheus format, you have to configure Prometheus to scrape it. Under the hood Rancher is using the [prometheus-operator](https://github.com/prometheus-operator/prometheus-operator). This makes it easy to add additional scraping targets with ServiceMonitors and PodMonitors. Many Helm charts let you create these monitors directly. You can also find more information in the Rancher documentation.
+Once all of your workloads expose metrics in a Prometheus format, you must configure Prometheus to scrape them. Under the hood, Rancher uses the [prometheus-operator](https://github.com/prometheus-operator/prometheus-operator). This makes it easy to add scraping targets with ServiceMonitors and PodMonitors. Many Helm charts already include an option to create these monitors directly. You can also find more information in the Rancher documentation.

 ### Prometheus Push Gateway

@@ -104,7 +104,7 @@ Option to change the range of ports that can be used for [NodePort services](htt

 #### TLS Alternate Names

-Add additional hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert.
+Add hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert.

 #### Authorized Cluster Endpoint

@@ -212,7 +212,7 @@ Option to change the range of ports that can be used for [NodePort services](htt

 #### TLS Alternate Names

-Add additional hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert.
+Add hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert.

 #### Authorized Cluster Endpoint

@@ -299,7 +299,7 @@ You can enable notifications to any notifiers based on the build status of a pip

    :::

-1. For each recipient, select which notifier type from the dropdown. Based on the type of notifier, you can use the default recipient or override the recipient with a different one. For example, if you have a notifier for _Slack_, you can update which channel to send the notification to. You can add additional notifiers by clicking **Add Recipient**.
+1. For each recipient, select which notifier type from the dropdown. Based on the type of notifier, you can use the default recipient or override the recipient with a different one. For example, if you have a notifier for _Slack_, you can update which channel to send the notification to. You can add more notifiers by clicking **Add Recipient**.

 ### Configuring Notifications by YAML

@@ -54,7 +54,7 @@ _New in v2.6.4_

 You can now provision node driver clusters from an air-gapped cluster configured to use a proxy for outbound connections.

-In addition to setting the default rules for a proxy server as shown above, you will need to add additional rules, shown below, to provision node driver clusters from a proxied Rancher environment.
+In addition to setting the default rules for a proxy server as shown above, you must also add the following rules to provision node driver clusters from a proxied Rancher environment:

 You will configure your filepath according to your setup, e.g., `/etc/apt/apt.conf.d/proxy.conf`: