[Various] Image alt text updates for bots, ssl, dns, and LB (cloudfla…

…re#4031) * Updates to alt text for load balancing and bots * Updates to ssl alt text * Capitalized letter
dpuga1 · Apr 6, 2022 · 7c89121 · 7c89121
1 parent 1d0cb7d
commit 7c89121
Show file tree

Hide file tree

Showing 15 changed files with 28 additions and 76 deletions.
diff --git a/content/bots/bot-analytics/biz-and-ent.md b/content/bots/bot-analytics/biz-and-ent.md
@@ -14,7 +14,7 @@ Business and Enterprise customers without Bot Management can use **Bot Analytics
 
 To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
 
-![Bot Analytics on Dashboard](/bots/static/bot-analytics-dashboard-biz.png)
+![View Bot Analytics in the Cloudflare Dashboard. For more details, keep reading.](/bots/static/bot-analytics-dashboard-biz.png)
 
 ## Features
 

diff --git a/content/bots/bot-analytics/bm-subscription.md b/content/bots/bot-analytics/bm-subscription.md
@@ -14,7 +14,7 @@ Enterprise customers with Bot Management can use **Bot Analytics** to dynamicall
 
 To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
 
-![Bot Analytics on Dashboard](/bots/static/bot-analytics-dashboard-ent.png)
+![View Bot Analytics in the Cloudflare Dashboard. For more details, keep reading.](/bots/static/bot-analytics-dashboard-ent.png)
 
 ## Features
 

diff --git a/content/bots/get-started/bm-subscription.md b/content/bots/get-started/bm-subscription.md
@@ -51,7 +51,7 @@ For **automated** traffic, sort through the IP addresses, ASNs, and other data p
 
 Use the slider tool to identify **other traffic groups**. For example, you may find that traffic from your mobile app is routinely scored at 12.
 
-![Bot score distribution](/bots/static/bot-score-distribution.png)
+![Example of a bot score distribution](/bots/static/bot-score-distribution.png)
 
 At the end of your analysis, you should:
 

diff --git a/content/bots/get-started/pro.md b/content/bots/get-started/pro.md
@@ -31,7 +31,7 @@ Use the **Bot Report** to monitor bot traffic for the past 24 hours.
 
 To access the **Bot Report**, go to **Security** > **Bots**. If you see a double-digit percentage of automated traffic, you may want to upgrade to [Bot Management](/bots/get-started/bm-subscription/) to save money on origin costs and protect your domain from large-scale attacks.
 
-![Bot report traffic distribution](/bots/static/bot-report-pro.png)
+![Example traffic distribution as part of a bot report](/bots/static/bot-report-pro.png)
 
 ### Firewall events
 

diff --git a/content/dns/zone-setups/full-setup/setup.md b/content/dns/zone-setups/full-setup/setup.md
@@ -76,7 +76,7 @@ Once you have added a domain (also known as a _zone_) to Cloudflare, that domain
 1.  Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2.  On **Overview**, copy the information from **Replace with Cloudflare's nameservers**.
 
-    ![get nameserver names from the Overview page of your domain](/dns/static/nameserver-names.png)
+    ![Find nameserver names on the Overview page of your domain](/dns/static/nameserver-names.png)
 
 {{<Aside type="note">}}
 Cloudflare automatically assigns nameservers to a domain and these assignments cannot be changed. For more details, refer to [Nameserver assignments](/dns/zone-setups/reference/nameserver-assignment/).

diff --git a/content/load-balancing/additional-options/deploy-containerized-applications.md b/content/load-balancing/additional-options/deploy-containerized-applications.md
@@ -10,40 +10,6 @@ meta:
 
 Cloudflare’s Load Balancer distributes global traffic intelligently across Google Kubernetes Engine (GKE) and Amazon Web Services EC2 (AWS). Cloudflare’s native Kubernetes support provides a multi-cloud deployment that is transparent to end users.
 
-![Application deployed across Google Kubernetes Engine and AWS](/load-balancing/static/images/best-practices-2.png)
+![Diagram of an application deployed across Google Kubernetes Engine and AWS](/load-balancing/static/images/best-practices-2.png)
 
-## Prerequisites
-
-Before you begin, be sure you have the following:
-
-- Access to Google Cloud Platform (GCP)
-- Access to AWS
-- Docker image
-- A domain on Cloudflare (on the Free, Pro, or Business plan) with a Load Balancing subscription, configurable in **Traffic** on the dashboard
-
-## Deploying a containerized web application on Google Kubernetes Engine
-
-You will be using [Google Cloud Shell](https://cloud.google.com/shell/) interface, which comes preinstalled with the gcloud console, docker, and kubectl command-line tools used below. If you use Cloud Shell, you do not need to install these command-line tools on your workstation.
-
-### Getting started
-
-Go to the [Kubernetes Engine](https://console.cloud.google.com/kubernetes?_ga=2.151836153.-1932148812.1510627946). Click the **Activate Google Cloud Shell** button at the top of the console window. A Cloud Shell session with a command prompt will open in a new frame at the bottom of the console.
-
-![Use the Cloud Shell in Google Kubernetes Engine](/load-balancing/static/images/best-practices-3.png)
-
-Set default configuration values by running the following commands:
-
-- `gcloud config set project PROJECT_ID`
-- `gcloud config set compute/zone us-west1-a`
-
-## Deploying a web application
-
-1.  Create a container cluster to run the container image. A cluster consists of a pool of Compute Engine VM instances running Kubernetes.
-
-    - Run the following command to create a three-node cluster (our cluster name is _camilia-cluster_): `gcloud container clusters create camilia-cluster --num-nodes=3`
-
-    - It may take several minutes for the cluster to be created. Once the command is complete, run the following command to see the cluster’s three worker VM instances: `gcloud compute instances list`
-
-2.  Deploy the application to the cluster. Use the kubectl command-line tool to deploy and manage applications on a Kubernetes Engine cluster.
-    You can create a simple nginx docker container, for example, using the following command (_camilia-nginx_ is the name for the deployment):
-    `kubectl run camilia-nginx --image=nginx --port 80`
+For more details on implementation, refer to our [Support Knowledgebase](https://support.cloudflare.com/hc/articles/115003384591).
diff --git a/content/load-balancing/additional-options/load-balancing-rules/expressions.md b/content/load-balancing/additional-options/load-balancing-rules/expressions.md
@@ -77,7 +77,7 @@ Compound expressions are easier to scan when displayed in the Expression Builder
 
 This Expression Builder screenshot shows the example compound expression described earlier. Compound expressions are easier to scan when displayed in the Expression Builder’s visual interface.
 
-![Expression Builder in Load Balancing tab of Traffic app](/load-balancing/static/images/rules-builder-1.png)
+![Example rule configuration visible in the Expression Builder](/load-balancing/static/images/rules-builder-1.png)
 
 The **Expression Preview** displays the expression in text:
 
@@ -92,13 +92,7 @@ For a walkthrough, refer to [Creating Load Balancing rules](/load-balancing/addi
 
 The Expression Editor is a text-only interface for creating Load Balancing expressions. Although it lacks the visual simplicity of the Expression Builder, the Expression Editor supports advanced features such as support for grouping symbols (parentheses).
 
-To access the Expression Editor in the **Traffic** app, click **Edit expression** in the **Create Custom Rule** dialog:
-
-![Edit expression link in Create Custom Rule dialog](/load-balancing/static/images/rules-builder-edit-expression-link.png)
-
-The Expression Editor displays:
-
-![Expression Editor in Load Balancing tab of Traffic app](/load-balancing/static/images/rules-editor-1.png)
+To access the Expression Editor in the **Traffic** app, click **Edit expression** in the **Create Custom Rule** dialog.
 
 To return to the builder, click **Use expression builder**.
 

diff --git a/content/load-balancing/additional-options/load-balancing-rules/reference.md b/content/load-balancing/additional-options/load-balancing-rules/reference.md
@@ -10,7 +10,7 @@ The fields available for load balancing rules depend on whether Cloudflare proxi
 
 If you use the wrong type of fields, you might see unexpected behavior from load balancing rules. For best results, always use the fields associated with your traffic's proxy status.
 
-![select load balancer fields based on the proxy status header](/load-balancing/static/images/proxy-status.png)
+![Choose load balancer fields based on the proxy status header](/load-balancing/static/images/proxy-status.png)
 
 ## Fields supported regardless of proxy
 

diff --git a/content/load-balancing/additional-options/override-http-host-headers.md b/content/load-balancing/additional-options/override-http-host-headers.md
@@ -56,4 +56,4 @@ For a list of origins that override a monitor's `Host` header:
 2.  Select **Advanced health check settings**.
 3.  If you have origin overrides, you will see **Origin host header overrides**.
 
-![List of origin host header overrides](/load-balancing/static/images/origin-host-header-override.png)
+![Example configuration of origin host header overrides](/load-balancing/static/images/origin-host-header-override.png)
diff --git a/content/load-balancing/additional-options/pagerduty-integration.md b/content/load-balancing/additional-options/pagerduty-integration.md
@@ -8,10 +8,6 @@ weight: 41
 
 To integrate Cloudflare Health Check notifications with PagerDuty, follow the steps outlined in PagerDuty’s [Email Integration Guide](https://www.pagerduty.com/docs/guides/email-integration-guide/). If you do not have a PagerDuty account, you will first need to set that up.
 
-PagerDuty will generate an email address that will create incidents based on emails sent to that address.
-
-If you already have email integration configured in PagerDuty, you can find the designated email address by going to **Configuration > Services > Email** (under **Integrations**).
-
-![Locate your existing email in Pagerdutry](/load-balancing/static/images/monitors-1.png)
+PagerDuty will generate an email address that will create incidents based on emails sent to that address. For help locating that email address, refer to the [PagerDuty documentation](https://www.pagerduty.com/docs/guides/email-integration-guide/).
 
 When creating the Notifier object, configure the email to go to the PagerDuty integration email. Consequently, whenever a pool or origin goes down, an Incident will be created to capture it.
diff --git a/content/load-balancing/additional-options/planned-maintenance.md b/content/load-balancing/additional-options/planned-maintenance.md
@@ -39,14 +39,14 @@ To remove a server from rotation while still preserving session continuity, set
 1.  On a new or existing load balancer, go to the **Hostname** step.
 2.  Make sure you have enabled **Session Affinity**.
 3.  For **Origin drain duration**, enter a time in seconds. If this value is less than the **Session TTL** value, you will affect existing sessions.
-    ![Session affinity configuration with origin drain](/load-balancing/static/images/session-affinity-3.png)
+    ![Example configuration of session affinity with origin drain](/load-balancing/static/images/session-affinity-3.png)
 4.  Save your changes to the load balancer.
 5.  Click **Manage Pools**.
 6.  Disable an origin. Your load balancer will gradually drain sessions from that origin.
 7.  On your load balancer, expand your pools to find the disabled origin. You will see the estimated **Drain Time** counting down.
-    ![Manage Load Balancer table with draining in progress](/load-balancing/static/images/session-affinity-4.png)
+    ![Example showing load balancer draining in progress](/load-balancing/static/images/session-affinity-4.png)
 8.  When a drain is **Complete**, there are no longer any connections to that origin.
-    ![Manage Load Balancer table with draining complete](/load-balancing/static/images/session-affinity-5.png)
+    ![Example showing load balancer draining complete](/load-balancing/static/images/session-affinity-5.png)
 9.  Perform your required maintenance or upgrades.
 10. To bring your origin back online, re-enable the origin.
 

diff --git a/content/ssl/_partials/_email-validation-process.md b/content/ssl/_partials/_email-validation-process.md
@@ -7,6 +7,6 @@ _build:
 
 The addresses listed in this field will receive an email from `[email protected]`. They should either click **Review Certificate Request** or the `https://certvalidate.cloudflare.com` hyperlink.
 
-![Certificate Validation Email](/ssl/static/certvalidate-email.png)
+![Example of the Certificate Validation Email](/ssl/static/certvalidate-email.png)
 
 As soon as the domain owner has clicked the link in this email and clicked **Approve** on the validation page, the certificate will move through the [various statuses](/ssl/ssl-tls/certificate-statuses/) until it becomes **Active**.
diff --git a/content/ssl/client-certificates/enable-mtls.md b/content/ssl/client-certificates/enable-mtls.md
@@ -11,15 +11,7 @@ To enable mutual Transport Layer Security (mTLS) for a host from the Cloudflare
 1.  Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and application.
 2.  Navigate to **SSL** > **Client Certificates**.
 3.  To enable mTLS for a host, click the **Edit** link in the **Hosts** section of the **Client Certificates** card.
-
-![Client Certificates card](/ssl/static/ssl-client-certs-card-edit-link.png)
-
-A text input and save controls display.
-
-![Enable mTLS Hosts input](/ssl/static/ssl-client-certs-host-input.png)
-
-1.  Enter the name of a host in your current application and press `Enter`.
-
-2.  Click **Save**.
+4.  Enter the name of a host in your current application and press `Enter`.
+5.  Click **Save**.
 
 Now that you have enabled mTLS for your host, you can enforce mTLS with [API Shield™](/api-shield/security/mtls/configure/).
diff --git a/content/ssl/origin-configuration/authenticated-origin-pull/explanation.md b/content/ssl/origin-configuration/authenticated-origin-pull/explanation.md
@@ -24,8 +24,12 @@ Cloudflare enforces authenticated origin pulls by adding an extra layer of TLS c
 
 **Standard TLS handshake**
 
-![Standard TLS handshake](/ssl/static/client-auth-tls-standard.png)
+![Diagram showing the Standard TLS handshake](/ssl/static/client-auth-tls-standard.png)
+
+For more details, refer to [What is a TLS handshake?](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/).
 
 **TLS handshake with authenticated origin pulls**
 
-![Client authenticated TLS handshake](/ssl/static/client-auth-tls-handshake.png)
+![Diagram showing the client authenticated TLS handshake](/ssl/static/client-auth-tls-handshake.png)
+
+For more details, refer to the [introductory blog post](https://blog.cloudflare.com/protecting-the-origin-with-tls-authenticated-origin-pulls/).
diff --git a/content/ssl/origin-configuration/ssl-modes.md b/content/ssl/origin-configuration/ssl-modes.md
@@ -50,7 +50,7 @@ When you set your encryption mode to **Off**, your application:
 - Will be marked as "not secure" by Chrome and other browsers, reducing visitor trust.
 - Will be penalized in [SEO rankings](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html).
 
-![SSL Encryption set to off](/ssl/static/ssl-encryption-mode-off.png)
+![With an encryption mode of Off, your application does not encrypt traffic between the visitor and Cloudflare or between Cloudflare and your server.](/ssl/static/ssl-encryption-mode-off.png)
 
 {{<Aside type="note">}}
 
@@ -76,7 +76,7 @@ Choose this option when you cannot set up an SSL certificate on your origin or y
 
 If your application contains sensitive information (personalized data, user login), use [**Full**](#full) or [**Full (Strict)**](#full-strict) modes instead.
 
-![SSL Encryption set to Flexible](/ssl/static/ssl-encryption-mode-flexible.png)
+![With an encryption mode of Flexible, your application encrypts traffic between the visitor and Cloudflare, but not between Cloudflare and your server.](/ssl/static/ssl-encryption-mode-flexible.png)
 
 ---
 
@@ -100,7 +100,7 @@ The certificate presented by the origin will **not be validated in any way**. It
 
 Without using [**Full (strict)**](#full-strict), a malicious party could technically hijack the connection and present their own certificate.
 
-![SSL Encryption set to Full](/ssl/static/ssl-encryption-mode-full.png)
+![With an encryption mode of Full, your application encrypts traffic going to and coming from Cloudflare but does not validate your origin certificate.](/ssl/static/ssl-encryption-mode-full.png)
 
 ---
 
@@ -126,7 +126,7 @@ Before enabling **Full (strict)** mode, make sure your origin allows HTTPS conne
 
 {{<render file="_ssl-mode-errors.md">}}
 
-![SSL Encryption set to Full (strict)](/ssl/static/ssl-encryption-mode-full-strict.png)
+![With an encryption mode of Full (strict), your application encrypts traffic going to and coming from Cloudflare.](/ssl/static/ssl-encryption-mode-full-strict.png)
 
 ---