[SSL/TLS] Remove previously required browser settings change in tls-13.mdx (#22135)

* [SSL/TLS] Remove previously required browser settings change in tls-13.mdx

* [SSL/TLS] Undo accidental change of a colon

* Remove redundant heading and link to specific protocols page

---------

Co-authored-by: Tom Klein <[email protected]>
Co-authored-by: Rebecca Tamachiro <[email protected]>

Author: 3 people

src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx

@@ -11,19 +11,17 @@ TLS 1.3 enables the latest version of the TLS protocol (when supported) for impr
 
 ## What is TLS 1.3?
 
-TLS 1.3 is the newest, fastest, and most secure version of the TLS protocol. SSL/TLS is the protocol that encrypts communication between users and your website. When web traffic is encrypted with TLS, users will see the green padlock in their browser window.
+TLS 1.3 is the newest, fastest, and most secure version of the [TLS protocol](/ssl/reference/protocols/).
 
-By turning on the TLS 1.3 feature, traffic to and from your website will be served over the TLS 1.3 protocol when supported by clients. TLS 1.3 protocol has improved latency over older versions, has several new features, and is currently supported in both Chrome (starting with release 66), Firefox (starting with release 60), and in development for Safari and Edge browsers.
+By turning on the TLS 1.3 feature, traffic to and from your website will be served over the TLS 1.3 protocol when supported by clients. TLS 1.3 protocol has improved latency over older versions, has several new features, and is currently supported in all updated major browsers.
 
 ## Availability
 
 <FeatureTable id="ssl.tls_13" />
 
 ## Enable TLS 1.3
 
-TLS 1.3 requires a two-step activation: in the Cloudflare dashboard and in the browser.
-
-### Enable TLS 1.3 in Cloudflare settings
+TLS 1.3 can be activated in the Cloudflare dashboard or through the API:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
@@ -39,37 +37,6 @@ To adjust your TLS 1.3 settings with the API, send a [`PATCH`](/api/resources/zo
 
 </TabItem> </Tabs>
 
-### Enable TLS 1.3 in the browser
-
-<Details header="Chrome">
-
-1. In the address bar, enter `chrome://flags` and press **Enter**.
-2. Scroll to locate the **TLS 1.3 Early Data** entry, and set it to _Enabled_. A message saying that the change will take effect the next time you relaunch Chrome will appear.
-3. Select **RELAUNCH NOW** to restart Chrome.
-
-After enabling TLS 1.3, visit a site with TLS 1.3 enabled over HTTPS. Then:
-
-1. Open Chrome **Developer Tools**.
-2. Select the **Security** tab.
-3. Reload the page (Command-R in macOS, Ctrl-R in Windows).
-4. Select the site under **Main origin**.
-5. Under **Connection**, confirm that the protocol is **TLS 1.3**.
-
-</Details>
-
-<Details header="Firefox">
-
-1. In the address bar, enter `about:config` and select to accept the warranty warning.
-2. Search for `security.tls.version.max` and change the value from `3` (the default) to `4`.
-
-After enabling TLS 1.3, visit a site with TLS 1.3 enabled over HTTPS. Then:
-
-1. Select the lock icon in the address bar.
-2. Select **Connection secure** > **More information**.
-3. Under **Technical Details**, verify that the TLS version is TLS 1.3.
-
-</Details>
-
 ### Troubleshooting
 
 Since TLS 1.3 implementations are relatively new, some failures may occur. If you experience errors, submit a Cloudflare Support ticket with the following information: