Updating titles, nav and update dates (#16963)

* Updating titles, nav and update dates

* Changing tabs to spaces!

* Fixing tabs in Microsoft SASE doc

* Update extending-cloudflares-benefits-to-saas-providers-end-customers.mdx

Minor change to title

---------

Co-authored-by: Claire Waters <[email protected]>

Author: 2 people

src/content/docs/reference-architecture/architectures/cdn.mdx

@@ -1,15 +1,16 @@
 ---
-title: Content Delivery Network (CDN)
+title: Content Delivery Network (CDN) Reference Architecture
 pcx_content_type: reference-architecture
+products:
+  - Cache
+  - CDN
 sidebar:
   order: 1
-head:
-  - tag: title
-    content: "Reference Architecture: Cloudflare Content Delivery Network (CDN)"
-
+  label: Content Delivery Network (CDN)
+updated: 2022-12-02
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 ## Introduction
 
@@ -23,14 +24,14 @@ To build a stronger baseline understanding of Cloudflare, we recommend the follo
 
 <Render file="what-is-cloudflare-link" />
 
-* What is a CDN? | [Website](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) (5 minute read)
-* Analyst Report: [Cloudflare named Leader in 2024 GigaOm Radar for Content Delivery Networks](https://www.cloudflare.com/lp/gigaom-radar-cdn/) (20 minute read)
+- What is a CDN? | [Website](https://www.cloudflare.com/learning/cdn/what-is-a-cdn/) (5 minute read)
+- Analyst Report: [Cloudflare named Leader in 2024 GigaOm Radar for Content Delivery Networks](https://www.cloudflare.com/lp/gigaom-radar-cdn/) (20 minute read)
 
 Those who read this reference architecture will learn:
 
-* How Cloudflare CDN can significantly improve the delivery of content to your customers
-* How anycast IP routing is important in ensuring reliable CDN performance
-* The range of tiered caching options and how to choose the one for your needs
+- How Cloudflare CDN can significantly improve the delivery of content to your customers
+- How anycast IP routing is important in ensuring reliable CDN performance
+- The range of tiered caching options and how to choose the one for your needs
 
 ## Traditional challenges deploying web applications
 
@@ -49,11 +50,11 @@ The servers hosting the websites are called origin servers. When clients access
 
 Enhancements in HTTP/2 and HTTP/3 allow for multiplexing multiple requests to the same server over a single TCP connection, thus saving server resources. However, compute and network resources are still consumed as servers respond to these requests. As more clients access the website, the following can result:
 
-* The origin server starts to become overloaded with requests, impacting availability; companies start looking at scaling out to handle the additional load
-* As each request has to make its way to the origin server, performance and user experience is impacted due to latency
-* The latency for end users becomes proportional to the distance between the client and origin server, thus resulting in varying experiences based on client location. This is especially true for specific countries that may experience latency due to traffic from or to that country, like China.
-* As origin servers respond to the increasing requests, bandwidth, egress, and compute costs increase drastically
-* Even as customers scale out to handle the increased demand in traffic, they are left exposed to both infrastructure-level and application-level distributed denial-of-service (DDoS) attacks
+- The origin server starts to become overloaded with requests, impacting availability; companies start looking at scaling out to handle the additional load
+- As each request has to make its way to the origin server, performance and user experience is impacted due to latency
+- The latency for end users becomes proportional to the distance between the client and origin server, thus resulting in varying experiences based on client location. This is especially true for specific countries that may experience latency due to traffic from or to that country, like China.
+- As origin servers respond to the increasing requests, bandwidth, egress, and compute costs increase drastically
+- Even as customers scale out to handle the increased demand in traffic, they are left exposed to both infrastructure-level and application-level distributed denial-of-service (DDoS) attacks
 
 In Figure 1 below, there is no CDN present and there is an origin server sitting in the US. As clients access the website, the first step is DNS resolution, typically done by the user’s ISP. The next step is the HTTP request sent directly to the origin server. The user experience will vary depending on their location. For example, you can see the latency is much lower for users in the US, where the origin server is located. For users outside the US, the latency increases, thus resulting in a higher round-trip time (RTT).
 
@@ -73,13 +74,13 @@ CDNs decrease latency and increase performance by having many data center locati
 
 ### Impacts
 
-* **Improved website load time**: Instead of every client making a request to the origin server, which could be located a considerable distance away, the request is routed to a local server that responds with cached content, thus decreasing latency and increasing overall performance. Regardless of where the origin server and clients are located, performance will be more consistent for all users, as the CDN will serve locally cached content when possible.
+- **Improved website load time**: Instead of every client making a request to the origin server, which could be located a considerable distance away, the request is routed to a local server that responds with cached content, thus decreasing latency and increasing overall performance. Regardless of where the origin server and clients are located, performance will be more consistent for all users, as the CDN will serve locally cached content when possible.
 
-* **Increased content availability and redundancy:** Because every client request no longer needs to be sent to the origin server, CDNs provide not only performance benefits, but also availability and redundancy. Requests are load balanced over local servers with cached content; these servers respond to local requests, significantly decreasing overall load on the origin server. The origin server only is contacted when needed (when content is not cached or for dynamic non-cacheable content).
+- **Increased content availability and redundancy:** Because every client request no longer needs to be sent to the origin server, CDNs provide not only performance benefits, but also availability and redundancy. Requests are load balanced over local servers with cached content; these servers respond to local requests, significantly decreasing overall load on the origin server. The origin server only is contacted when needed (when content is not cached or for dynamic non-cacheable content).
 
-* **Improved website security:** A CDN acts as a reverse proxy and sits in front of origin servers. Thus it can provide enhanced security such as DDoS mitigation, improvements to security certificates, and other optimizations.
+- **Improved website security:** A CDN acts as a reverse proxy and sits in front of origin servers. Thus it can provide enhanced security such as DDoS mitigation, improvements to security certificates, and other optimizations.
 
-* **Reduced bandwidth costs:** Because CDNs use cached content to respond to requests, the number of requests sent to the origin server is reduced, thus also reducing associated bandwidth costs.
+- **Reduced bandwidth costs:** Because CDNs use cached content to respond to requests, the number of requests sent to the origin server is reduced, thus also reducing associated bandwidth costs.
 
 ### Routing requests to CDN nodes
 
@@ -99,9 +100,9 @@ The Cloudflare CDN, which is discussed in more detail in the next section, uses
 
 Using an anycast-based CDN has several advantages:
 
-* Incoming traffic is routed to the nearest data center with the capacity to process the requests efficiently.
-* Availability and redundancy is inherently provided. Since multiple nodes have the same IP address, if one node were to fail, requests are simply routed to another node in close proximity.
-* Because anycast distributes traffic across multiple data centers, it increases the overall surface area, thus preventing any one location from becoming overwhelmed with requests. For this reason, anycast networks are very resilient to DDoS attacks.
+- Incoming traffic is routed to the nearest data center with the capacity to process the requests efficiently.
+- Availability and redundancy is inherently provided. Since multiple nodes have the same IP address, if one node were to fail, requests are simply routed to another node in close proximity.
+- Because anycast distributes traffic across multiple data centers, it increases the overall surface area, thus preventing any one location from becoming overwhelmed with requests. For this reason, anycast networks are very resilient to DDoS attacks.
 
 ## Introducing the Cloudflare CDN
 
@@ -124,12 +125,12 @@ Figure 3 is a view of the Cloudflare CDN on the global anycast network. In addit
 
 In the above diagram, there are a few important key points to understand about the Cloudflare CDN and the global anycast network it resides on:
 
-* An important differentiator is that Cloudflare utilizes one global network and runs every service on every server in every Cloudflare data center, thus providing end users the closest proximity to Cloudflare’s services, with the highest scale, resiliency, and performance.
-* Cloudflare is a reverse proxy, meaning it receives requests from clients and proxies the requests back to the customer’s origin servers. Thus, every request traverses through Cloudflare’s network before reaching the customer’s network. Since Cloudflare has hardened and protected its infrastructure at the edge (ingress), all customers are consequently also protected from infrastructure-level and volumetric DDoS attacks. Requests and traffic must go through the protected Cloudflare network before reaching the customer’s origin server.
-* The Cloudflare CDN leverages the Cloudflare global anycast network. Thus the incoming request is routed to and answered by the node closest to the user.
-* The inherent benefits of anycast are decreased latency, network resiliency, higher availability, and increased security due to larger surface area for absorbing both legitimate traffic loads and DDoS attacks. Cloudflare’s global anycast network spans [hundreds of cities worldwide](https://www.cloudflare.com/network/), reaching 95% of the world’s Internet-connected population within 50 milliseconds while providing over 280 Tbps of network capacity and DDoS protection capability.
-* Edge nodes within the Cloudflare network cache content from the origin server and are able to respond to requests via a cached copy. Cloudflare also provides [DNS](/dns/), [DDoS protection](/ddos-protection/), [WAF](/waf/), and other performance, reliability, and security services using the same edge architecture.
-* [Argo](/argo-smart-routing/) uses optimized routing and caching technology across the Cloudflare network to deliver responses to users more quickly, reliably, and securely. Argo includes Smart Routing and [Tiered Cache](/cache/how-to/tiered-cache/). Cloudflare leverages Argo to provide an enhanced CDN solution.
+- An important differentiator is that Cloudflare utilizes one global network and runs every service on every server in every Cloudflare data center, thus providing end users the closest proximity to Cloudflare’s services, with the highest scale, resiliency, and performance.
+- Cloudflare is a reverse proxy, meaning it receives requests from clients and proxies the requests back to the customer’s origin servers. Thus, every request traverses through Cloudflare’s network before reaching the customer’s network. Since Cloudflare has hardened and protected its infrastructure at the edge (ingress), all customers are consequently also protected from infrastructure-level and volumetric DDoS attacks. Requests and traffic must go through the protected Cloudflare network before reaching the customer’s origin server.
+- The Cloudflare CDN leverages the Cloudflare global anycast network. Thus the incoming request is routed to and answered by the node closest to the user.
+- The inherent benefits of anycast are decreased latency, network resiliency, higher availability, and increased security due to larger surface area for absorbing both legitimate traffic loads and DDoS attacks. Cloudflare’s global anycast network spans [hundreds of cities worldwide](https://www.cloudflare.com/network/), reaching 95% of the world’s Internet-connected population within 50 milliseconds while providing over 280 Tbps of network capacity and DDoS protection capability.
+- Edge nodes within the Cloudflare network cache content from the origin server and are able to respond to requests via a cached copy. Cloudflare also provides [DNS](/dns/), [DDoS protection](/ddos-protection/), [WAF](/waf/), and other performance, reliability, and security services using the same edge architecture.
+- [Argo](/argo-smart-routing/) uses optimized routing and caching technology across the Cloudflare network to deliver responses to users more quickly, reliably, and securely. Argo includes Smart Routing and [Tiered Cache](/cache/how-to/tiered-cache/). Cloudflare leverages Argo to provide an enhanced CDN solution.
 
 ### Tiered Cache
 
@@ -230,10 +231,8 @@ When combined with Tiered Caching and Argo Smart Routing, Cache Reserve can be a
 
 :::note
 
-
 Using [Image Resizing](/images/transform-images/) with Cache Reserve will not result in resized images being stored in Cache Reserve since Image Resizing takes place after reading from Cache Reserve. Resized images will be cached in other available tiers when they are served after resizing.
 
-
 :::
 
 ### Traffic flow: Cache Reserve topology

src/content/docs/reference-architecture/architectures/cloudflare-sase-with-microsoft.mdx

@@ -1,11 +1,16 @@
 ---
-title: Cloudflare SASE with Microsoft
+title: Reference Architecture using Cloudflare SASE with Microsoft
 pcx_content_type: reference-architecture
+products:
+  - Access
+  - Gateway
+  - CASB
+  - Email Security
 sidebar:
   order: 1
-head:
-  - tag: title
-    content: "Reference Architecture: Architecture using Cloudflare SASE with Microsoft"
+  label: Cloudflare SASE with Microsoft
+updated: 2024-13-06
+
 ---
 
 import { Render } from "~/components";

src/content/docs/reference-architecture/architectures/load-balancing.mdx

@@ -1,11 +1,12 @@
 ---
-title: Load Balancing
+title: Load Balancing Reference Architecture
 pcx_content_type: reference-architecture
+products:
+  - Load Balancing
 sidebar:
   order: 1
-head:
-  - tag: title
-    content: "Reference Architecture: Cloudflare Load Balancing Reference Architecture"
+  label: Load Balancing
+updated: 2024-02-26
 ---
 
 import { Render } from "~/components";