chore: Remove old IP and TLS cipher suite details (#7225)

* chore: Remove old IP and TLS cipher suite details

* Fix case in warning box to trigger rebuild

* rm extra word now that things compile

src/docs/product/security/ip-ranges.mdx

@@ -17,12 +17,6 @@ apply to self-hosted or single tenant.
 
 Sentry's dashboard and API are both served from a single IP address for all web traffic. The IP address is:
 
-```
-35.188.42.15/32
-```
-
-Starting on September 1, 2023, Sentry's dashboard and API will both be served from a new IP address:
-
 ```
 35.186.247.156/32
 ```
@@ -36,12 +30,6 @@ Sentry's Event Ingestion respects two domains within a Data Source Name (DSN):
 
 Sentry's apex domain (`sentry.io`) accepts events from the same IP address as the Dashboard and API:
 
-```
-35.188.42.15/32
-```
-
-Starting on September 1, 2023, Sentry's apex domain (`sentry.io`) will migrate to the same new IP address as the dashboard and API:
-
 ```
 35.186.247.156/32
 ```
@@ -52,7 +40,7 @@ Sentry's organization subdomains (`o<number>.ingest.sentry.io`) accept events fr
 34.120.195.249/32
 ```
 
-Starting on September 1, 2023, Sentry's legacy ingestion hostname (`app.getsentry.com`) will also migrate to a new IP address:
+Sentry's legacy ingestion hostname (`app.getsentry.com`) accepts events from a separate IP address:
 
 ```
 34.96.102.34/32

src/docs/product/security/ssl.mdx

@@ -9,46 +9,17 @@ description: "Learn how Sentry's SaaS product uses SSL Protocols and Ciphers for
 <Alert title="Note" level="warning">
 
 The contents of this page apply only to Sentry's SaaS product. It **does not**
-apply to Self-hosted or Single Tenant.
+apply to self-hosted or single tenant.
 
 </Alert>
 
-Sentry's API, Dashboard, and Event Submission requires a minimum TLS version of 1.2 to communicate securely.
+Sentry's API, dashboard, and event submission require a minimum TLS version of 1.2 to communicate securely.
 
 Sentry provides a suite of protocols and ciphers that focus on giving our users a balance of security and compatibility. Our servers will negotiate a cipher to the most secure combination the client can support in the preferential order specified below. The set of ciphers depends on the endpoint and negotiated TLS version.
 
-### sentry.io
+### sentry.io and \*.ingest.sentry.io
 
-Sentry's API, Dashboard, and legacy Event Submission (via `sentry.io` domain). Only TLS 1.2 is supported.
-
-Supported ciphers:
-
-- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
-- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
-- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
-- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
-- TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
-- TLS_DHE_RSA_WITH_AES_256_CBC_SHA
-- TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
-- TLS_RSA_WITH_AES_256_GCM_SHA384
-- TLS_RSA_WITH_AES_256_CBC_SHA256
-- TLS_RSA_WITH_AES_256_CBC_SHA
-- TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
-- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
-- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
-- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
-- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
-- TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
-- TLS_DHE_RSA_WITH_AES_128_CBC_SHA
-- TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
-- TLS_RSA_WITH_AES_128_GCM_SHA256
-- TLS_RSA_WITH_AES_128_CBC_SHA256
-- TLS_RSA_WITH_AES_128_CBC_SHA
-- TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
-
-### \*.ingest.sentry.io
-
-For ingestion domains, TLS 1.2 and 1.3 are supported.
+TLS versions 1.2 and 1.3 are supported for both Sentry's API, dashboard, and legacy event submission (via `sentry.io`), and for event ingestion domains (via `*.ingest.sentry.io`).
 
 Supported ciphers: