diff --git a/docs/api/getting-started.md b/docs/api/getting-started.md
index f8af4fa41d..bd75c1cb44 100644
--- a/docs/api/getting-started.md
+++ b/docs/api/getting-started.md
@@ -87,103 +87,21 @@ Sumo Logic has several deployments that are assigned depending on the geographic
 
 Sumo Logic redirects your browser to the correct login URL and also redirects Collectors to the correct endpoint. However, if you're using an API you'll need to manually direct your API client to the correct Sumo Logic API URL.
 
-<table>
-  <tr>
-   <td>Deployment</td>
-   <td>Service Endpoint (login URL)</td>
-   <td>API Endpoint</td>
-   <td>Collection Endpoint</td>
-   <td>Cloud Syslog Endpoint</td>
-   <td>OpenTelemetry Collector Endpoint</td>
-  </tr>
-  <tr>
-   <td>AU</td>
-   <td>https://service.au.sumologic.com</td>
-   <td>https://api.au.sumologic.com/api/</td>
-   <td>https://collectors.au.sumologic.com</td>
-   <td>syslog.collection.au.sumologic.com</td>
-   <td>https://open-collectors.au.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>CA</td>
-   <td>https://service.ca.sumologic.com</td>
-   <td>https://api.ca.sumologic.com/api/</td>
-   <td>https://collectors.ca.sumologic.com</td>
-   <td>syslog.collection.ca.sumologic.com</td>
-   <td>https://open-collectors.ca.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>DE</td>
-   <td>https://service.de.sumologic.com</td>
-   <td>https://api.de.sumologic.com/api/</td>
-   <td>https://collectors.de.sumologic.com</td>
-   <td>syslog.collection.de.sumologic.com</td>
-   <td>https://open-collectors.de.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>EU</td>
-   <td>https://service.eu.sumologic.com</td>
-   <td>https://api.eu.sumologic.com/api/</td>
-   <td>https://collectors.eu.sumologic.com<br/>
-   https://endpoint1.collection.eu.sumologic.com</td>
-   <td>syslog.collection.eu.sumologic.com</td>
-   <td>https://open-collectors.eu.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>FED</td>
-   <td>https://service.fed.sumologic.com</td>
-   <td>https://api.fed.sumologic.com/api/</td>
-   <td>https://collectors.fed.sumologic.com</td>
-   <td>syslog.collection.fed.sumologic.com</td>
-   <td>https://open-collectors.fed.sumologic.com/</td>
-  </tr>
-  <tr>
-   <td>JP</td>
-   <td>https://service.jp.sumologic.com</td>
-   <td>https://api.jp.sumologic.com/api/</td>
-   <td>https://collectors.jp.sumologic.com</td>
-   <td>syslog.collection.jp.sumologic.com</td>
-   <td>https://open-collectors.jp.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>KR</td>
-   <td>https://service.kr.sumologic.com</td>
-   <td>https://api.kr.sumologic.com/api/</td>
-   <td>https://collectors.kr.sumologic.com</td>
-   <td>syslog.collection.kr.sumologic.com</td>
-   <td>https://open-collectors.kr.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>US1</td>
-   <td>https://service.sumologic.com/</td>
-   <td>https://api.sumologic.com/api/</td>
-   <td>https://collectors.sumologic.com<br/>
-   https://endpoint1.collection.sumologic.com<br/>
-   https://endpoint2.collection.sumologic.com<br/>
-   https://endpoint3.collection.sumologic.com<br/>
-   https://endpoint4.collection.sumologic.com<br/>
-   https://endpoint5.collection.sumologic.com</td>
-   <td>syslog.collection.us1.sumologic.com</td>
-   <td>https://open-collectors.sumologic.com</td>
-  </tr>
-  <tr>
-   <td>US2</td>
-   <td>https://service.us2.sumologic.com</td>
-   <td>https://api.us2.sumologic.com/api/</td>
-   <td>https://collectors.us2.sumologic.com<br/>
-https://endpoint1.collection.us2.sumologic.com<br/>
-https://endpoint2.collection.us2.sumologic.com<br/>
-https://endpoint3.collection.us2.sumologic.com<br/>
-https://endpoint4.collection.us2.sumologic.com<br/>
-https://endpoint5.collection.us2.sumologic.com<br/>
-https://endpoint6.collection.us2.sumologic.com<br/>
-https://endpoint7.collection.us2.sumologic.com<br/>
-https://endpoint8.collection.us2.sumologic.com<br/>
-https://endpoint9.collection.us2.sumologic.com/</td>
-   <td>syslog.collection.us2.sumologic.com</td>
-   <td>https://open-collectors.us2.sumologic.com</td>
-  </tr>
-  </table>
+<div class="responsive-table">
+
+| Region | Service<br/>(login URL) | API endpoint | Collection | Syslog | OTel |
+|:--|:--|:--|:--|:--|:--|
+| AU | [service.au.sumologic.com](https://service.au.sumologic.com) | `api.au.sumologic.com/api/` | `collectors.au.sumologic.com` | `syslog.collection.au.sumologic.com` | `open-collectors.au.sumologic.com` |
+| CA | [service.ca.sumologic.com](https://service.ca.sumologic.com) | `api.ca.sumologic.com/api/` | `collectors.ca.sumologic.com` | `syslog.collection.ca.sumologic.com` | `open-collectors.ca.sumologic.com` |
+| DE | [service.de.sumologic.com](https://service.de.sumologic.com) | `api.de.sumologic.com/api/` | `collectors.de.sumologic.com` | `syslog.collection.de.sumologic.com` | `open-collectors.de.sumologic.com` |
+| EU | [service.eu.sumologic.com](https://service.eu.sumologic.com) | `api.eu.sumologic.com/api/` | `collectors.eu.sumologic.com`<br/>`endpoint1.collection.eu.sumologic.com` | `syslog.collection.eu.sumologic.com` | `open-collectors.eu.sumologic.com` |
+| FED | [service.fed.sumologic.com](https://service.fed.sumologic.com) | `api.fed.sumologic.com/api/` | `collectors.fed.sumologic.com` | `syslog.collection.fed.sumologic.com` | `open-collectors.fed.sumologic.com` |
+| JP | [service.jp.sumologic.com](https://service.jp.sumologic.com) | `api.jp.sumologic.com/api/` | `collectors.jp.sumologic.com` | `syslog.collection.jp.sumologic.com` | `open-collectors.jp.sumologic.com` |
+| KR | [service.kr.sumologic.com](https://service.kr.sumologic.com) | `api.kr.sumologic.com/api/` | `collectors.kr.sumologic.com` | `syslog.collection.kr.sumologic.com` | `open-collectors.kr.sumologic.com` |
+| US1 | [service.sumologic.com](https://service.sumologic.com) | `api.sumologic.com/api/` | `collectors.sumologic.com`<br/>`endpoint1-5.collection.sumologic.com` | `syslog.collection.us1.sumologic.com` | `open-collectors.sumologic.com` |
+| US2 | [service.us2.sumologic.com](https://service.us2.sumologic.com) | `api.us2.sumologic.com/api/` | `collectors.us2.sumologic.com`<br/>`endpoint1-9.collection.us2.sumologic.com` | `syslog.collection.us2.sumologic.com` | `open-collectors.us2.sumologic.com` |
+
+</div>
 
 ### Which endpoint should I should use?
 
diff --git a/docs/integrations/amazon-aws/aws-privatelink.md b/docs/integrations/amazon-aws/aws-privatelink.md
index 03422ca434..940f82dd33 100644
--- a/docs/integrations/amazon-aws/aws-privatelink.md
+++ b/docs/integrations/amazon-aws/aws-privatelink.md
@@ -37,78 +37,20 @@ With the NLB-created and ALB-registered as a target, requests over AWS PrivateL
 
 Sumo Logic exposes AWS PrivateLink endpoints to different [regions that depend on your Sumo Logic deployment](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security). If you're using the VPC in a different region where the Sumo Logic PrivateLink endpoint service is set up, you need to set up VPC peering. Either way, you need to create an endpoint.
 
-<table>
-  <tr>
-    <td><strong>Deployment</strong></td>
-    <td><strong>Collection Endpoint</strong></td>
-    <td><strong>OpenTelemetry Collector Endpoint</strong></td>
-    <td><strong>AWS Region of Sumo PrivateLink Endpoint Service</strong></td>
-  </tr>
-  <tr>
-    <td>AU</td>
-    <td>https://collectors.au.sumologic.com</td>
-    <td>https://open-collectors.au.sumologic.com</td>
-    <td>ap-southeast-2</td>
-  </tr>
-  <tr>
-    <td>CA</td>
-    <td>https://collectors.ca.sumologic.com</td>
-    <td>https://open-collectors.ca.sumologic.com</td>
-    <td>ca-central-1</td>
-  </tr>
-  <tr>
-    <td>DE</td>
-    <td>https://collectors.de.sumologic.com</td>
-    <td>https://open-collectors.de.sumologic.com</td>
-    <td>eu-central-1</td>
-  </tr>
-  <tr>
-    <td>EU</td>
-    <td>https://collectors.eu.sumologic.com<br/>
-    https://endpoint1.collection.eu.sumologic.com</td>
-    <td>https://open-collectors.eu.sumologic.com</td>
-    <td>eu-west-1</td>
-  </tr>
-  <tr>
-    <td>JP</td>
-    <td>https://collectors.jp.sumologic.com</td>
-    <td>https://open-collectors.jp.sumologic.com</td>
-    <td>ap-northeast-1</td>
-  </tr>
-    <tr>
-    <td>KR</td>
-    <td>https://collectors.kr.sumologic.com<br/></td>
-    <td>https://open-collectors.kr.sumologic.com</td>
-   <td>ap-northeast-2</td>
-  </tr>
-  <tr>
-    <td>US1</td>
-    <td>https://collectors.sumologic.com<br/>
-    https://endpoint1.collection.sumologic.com<br/>
-    https://endpoint2.collection.sumologic.com<br/>
-    https://endpoint3.collection.sumologic.com<br/>
-    https://endpoint4.collection.sumologic.com<br/>
-    https://endpoint5.collection.sumologic.com</td>
-    <td>https://open-collectors.sumologic.com</td>
-   <td>us-east-1</td>
-  </tr>
-  <tr>
-    <td>US2</td>
-    <td>https://collectors.us2.sumologic.com<br/>
-https://endpoint1.collection.us2.sumologic.com<br/>
-https://endpoint2.collection.us2.sumologic.com<br/>
-https://endpoint3.collection.us2.sumologic.com<br/>
-https://endpoint4.collection.us2.sumologic.com<br/>
-https://endpoint5.collection.us2.sumologic.com<br/>
-https://endpoint6.collection.us2.sumologic.com<br/>
-https://endpoint7.collection.us2.sumologic.com<br/>
-https://endpoint8.collection.us2.sumologic.com<br/>
-https://endpoint9.collection.us2.sumologic.com</td>
-    <td>https://open-collectors.us2.sumologic.com</td>
-    <td>us-west-2</td>
-  </tr>
-</table>
-
+<div class="responsive-table">
+
+| Deployment | Collection endpoint | OpenTelemetry collector endpoint | AWS Region of Sumo PrivateLink endpoint service |
+|:-----------|:---------------------|:----------------------------------|:------------------------------------------------|
+| AU         | `collectors.au.sumologic.com` | `open-collectors.au.sumologic.com` | `ap-southeast-2` |
+| CA         | `collectors.ca.sumologic.com` | `open-collectors.ca.sumologic.com` | `ca-central-1` |
+| DE         | `collectors.de.sumologic.com` | `open-collectors.de.sumologic.com` | `eu-central-1` |
+| EU         | `collectors.eu.sumologic.com`<br/>`endpoint1.collection.eu.sumologic.com` | `open-collectors.eu.sumologic.com` | `eu-west-1` |
+| JP         | `collectors.jp.sumologic.com` | `open-collectors.jp.sumologic.com` | `ap-northeast-1` |
+| KR         | `collectors.kr.sumologic.com` | `open-collectors.kr.sumologic.com` | `ap-northeast-2` |
+| US1        | `collectors.sumologic.com`<br/>`endpoint1.collection.sumologic.com`<br/>`endpoint2.collection.sumologic.com`<br/>`endpoint3.collection.sumologic.com`<br/>`endpoint4.collection.sumologic.com`<br/>`endpoint5.collection.sumologic.com` | `open-collectors.sumologic.com` | `us-east-1` |
+| US2        | `collectors.us2.sumologic.com`<br/>`endpoint1.collection.us2.sumologic.com`<br/>`endpoint2.collection.us2.sumologic.com`<br/>`endpoint3.collection.us2.sumologic.com`<br/>`endpoint4.collection.us2.sumologic.com`<br/>`endpoint5.collection.us2.sumologic.com`<br/>`endpoint6.collection.us2.sumologic.com`<br/>`endpoint7.collection.us2.sumologic.com`<br/>`endpoint8.collection.us2.sumologic.com`<br/>`endpoint9.collection.us2.sumologic.com` | `open-collectors.us2.sumologic.com` | `us-west-2` |
+
+</div>
 
 ### Create an endpoint to connect with the Sumo Logic endpoint service
 
diff --git a/docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md b/docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md
index ccf0373577..fcfc2923d7 100644
--- a/docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md
+++ b/docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md
@@ -51,6 +51,8 @@ This application relies on 45 Scheduled Searches that Save to two different Inde
 <details>
 <summary>View the list of Scheduled Searches (<strong>click to expand</strong>)</summary>
 
+<div class="responsive-table">
+
 <table>
   <tr>
     <td><strong>Folder</strong></td>
@@ -284,6 +286,8 @@ This application relies on 45 Scheduled Searches that Save to two different Inde
   </tr>
 </table>
 
+</div>
+
 * To reduce false positives, the benchmarks and application filter out AWS CloudTrail events from legitimate cloud services including AWS itself and CloudHealth by VMware.
 * Security posture requirements may vary between AWS accounts for a given customer. For example, development accounts might have less strict controls than production accounts. The app supports filtering findings by AWS account ID to facilitate AWS account level posture assessment.
 * The benchmarking models use cohorts calculated from similar AWS accounts.
diff --git a/docs/integrations/app-development/jfrog-artifactory.md b/docs/integrations/app-development/jfrog-artifactory.md
index 28ddbe9a5e..6d29499182 100644
--- a/docs/integrations/app-development/jfrog-artifactory.md
+++ b/docs/integrations/app-development/jfrog-artifactory.md
@@ -114,33 +114,16 @@ In this step, you configure four local file sources, one for each log source lis
 
 The following suffixes are required. For example, you could use `_sourceCategory=<Foo>/artifactory/console`, but the suffix **artifactory/console** must be used.
 
-<table>
-  <tr>
-   <td><strong>Log source</strong></td>
-   <td><strong>File Path</strong></td>
-   <td><strong>Source Category</strong></td>
-  </tr>
-  <tr>
-   <td>Artifactory Server and other microservices</td>
-   <td>$JFROG_HOME/&#60;product&#62;/var/log/artifactory-service.log</td>
-   <td>artifactory/console</td>
-  </tr>
-  <tr>
-   <td>Access</td>
-   <td>$JFROG_HOME/artifactory/var/artifactory/log/artifactory-access.log.</td>
-   <td>artifactory/access</td>
-  </tr>
-  <tr>
-   <td>Request</td>
-   <td>$JFROG_HOME/&#60;product&#62;/var/log/artifactory-request.log</td>
-   <td>artifactory/request</td>
-  </tr>
-  <tr>
-   <td>Traffic</td>
-   <td>$JFROG_HOME/&#60;product&#62;/var/log/artifactory-traffic.*.log</td>
-   <td>artifactory/traffic</td>
-  </tr>
-</table>
+<div class="responsive-table">
+
+| Log source                         | File Path                                                          | Source Category       |
+|:----------------------------------|:--------------------------------------------------------------------|:-----------------------|
+| Artifactory Server and other microservices | `$JFROG_HOME/<product>/var/log/artifactory-service.log`             | `artifactory/console` |
+| Access                            | `$JFROG_HOME/artifactory/var/artifactory/log/artifactory-access.log.` | `artifactory/access`  |
+| Request                           | `$JFROG_HOME/<product>/var/log/artifactory-request.log`            | `artifactory/request` |
+| Traffic                           | `$JFROG_HOME/<product>/var/log/artifactory-traffic.*.log`          | `artifactory/traffic` |
+
+</div>
 
 :::note
 Remember that `_sourceCategory` names are case sensitive. When you run a search using `_sourceCategory`, make sure you use the same case as you did when configuring the source.
diff --git a/src/css/sumo.scss b/src/css/sumo.scss
index 668def513e..5603446f5f 100644
--- a/src/css/sumo.scss
+++ b/src/css/sumo.scss
@@ -981,7 +981,33 @@ html[data-theme='dark'] .node polygon {
   stroke: #2196F3 !important;
 }
 
+// reduce width of wide tables
+.responsive-table {
+  overflow-x: auto;
+  width: 100%;
+  font-size: 0.8rem; /* Shrinks font for tighter layout */
+}
+
+.responsive-table table {
+  width: 100%;
+  table-layout: fixed;
+  border-collapse: collapse;
+}
 
+.responsive-table code {
+  font-size: 0.7rem;
+  line-height: 1.3; /* slightly tighter if desired */
+}
+
+.responsive-table th,
+.responsive-table td {
+  text-align: left;
+  word-break: break-word;
+  white-space: normal;
+  padding: 0.75rem 0.5rem; /* Adds vertical breathing room */
+  max-width: 220px; /* Can adjust based on layout needs */
+  min-width: 65px; /* Can adjust based on layout needs */
+}
 
 // Hub pages
 
@@ -1370,7 +1396,13 @@ html[data-theme='dark'] .featureImage {
   padding: 0 !important;
 }
 
-.title_f1Hy {
+/* Force smaller font size on blog post titles */
+article header h1, article header h2 {
+  font-size: 1.5rem !important;
+}
+
+article header h1[class*='title_'],
+article header h2[class*='title_'] {
   font-size: 1.5rem !important;
 }