Docusaurus Faster (take 2) (#4928)

* Docusaurus Faster

* license

Author: kimsauce

LICENSE

@@ -88,7 +88,7 @@ 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><small>
+<table>
   <tr>
    <td>Deployment</td>
    <td>Service Endpoint (login URL)</td>
@@ -192,7 +192,7 @@ https://endpoint9.collection.us2.sumologic.com/</td>
    <td>syslog.collection.us2.sumologic.com</td>
    <td>https://open-collectors.us2.sumologic.com</td>
   </tr>
-  </small>
+  
   </table>
 
 ### Which endpoint should I should use?

docs/api/getting-started.md

@@ -28,7 +28,7 @@ With the Organizations Management API, you can get the credits usage details of
 | JP         | https://api.jp.sumologic.com/docs/#tag/orgsManagement  |
 | KR         | https://api.kr.sumologic.com/docs/#tag/orgsManagement  |
 | US1        | https://api.sumologic.com/docs/#tag/orgsManagement     |
-| US2        | https://api.us2.sumologic.com/docs/#tag/orgsManagement<br/>https://organizations.sumologic.com/docs/#tag/organizationsManagement* <br/><small> *This assembly is exclusive to the US2 deployment and is designed to manage APIs for Sumo Logic orgs that are not tied to a specific deployment. For example, a parent organization might have child organizations across different deployments. As a result, the [List Organizations API](https://organizations.sumologic.com/docs/#operation/listOrganizations), which lists child organizations, is included in this assembly to accommodate child organizations spread across multiple deployments.</small> |
+| US2        | https://api.us2.sumologic.com/docs/#tag/orgsManagement<br/>https://organizations.sumologic.com/docs/#tag/organizationsManagement* <br/> *This assembly is exclusive to the US2 deployment and is designed to manage APIs for Sumo Logic orgs that are not tied to a specific deployment. For example, a parent organization might have child organizations across different deployments. As a result, the [List Organizations API](https://organizations.sumologic.com/docs/#operation/listOrganizations), which lists child organizations, is included in this assembly to accommodate child organizations spread across multiple deployments. |
 
 <!-- ## Required role capabilities
 

docs/api/organizations-management.md

@@ -37,7 +37,7 @@ 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><small>
+<table>
   <tr>
     <td><strong>Deployment</strong></td>
     <td><strong>Collection Endpoint</strong></td>
@@ -119,7 +119,7 @@ https://endpoint9.collection.us2.sumologic.com</td>
     <td>https://open-collectors.us2.sumologic.com</td>
     <td>us-west-2</td>
   </tr>
-</small></table>
+</table>
 
 ### Create an endpoint to connect with the Sumo Logic endpoint service
 

docs/integrations/amazon-aws/aws-privatelink.md

@@ -51,7 +51,7 @@ 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>
 
-<table><small>
+<table>
   <tr>
     <td><strong>Folder</strong></td>
     <td><strong>Scheduled Search Name (prefixed with gis_benchmarks)</strong></td>
@@ -282,7 +282,7 @@ This application relies on 45 Scheduled Searches that Save to two different Inde
     <td>S3_ListBuckets</td>
     <td>Counts S3 events related to listing buckets.</td>
   </tr>
-</small></table>
+</table>
 
 * 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.

docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md

@@ -200,7 +200,7 @@ To collect the metrics in Sumo Logic, follow the steps below:
 
 Once Provisioned Concurrency is enabled and you start collecting CloudWatch metrics, the following new metrics will be available:
 
-<table><small>
+<table>
   <tr>
    <td>Metric   </td>
    <td>Description   </td>
@@ -220,7 +220,7 @@ Once Provisioned Concurrency is enabled and you start collecting CloudWatch metr
   <tr>
    <td><strong>ProvisionedConcurrencySpilloverInvocations</strong>   </td>
    <td>Number of Invocations that are above Provisioned Concurrency   </td>
-  </tr></small>
+  </tr>
 </table>
 
 

docs/integrations/amazon-aws/lambda.md

@@ -114,7 +114,7 @@ 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><small>
+<table>
   <tr>
    <td><strong>Log source</strong></td>
    <td><strong>File Path</strong></td>
@@ -139,7 +139,7 @@ The following suffixes are required. For example, you could use `_sourceCategory
    <td>Traffic</td>
    <td>$JFROG_HOME/&#60;product&#62;/var/log/artifactory-traffic.*.log</td>
    <td>artifactory/traffic</td>
-  </tr></small>
+  </tr>
 </table>
 
 :::note

docs/integrations/app-development/jfrog-artifactory.md

@@ -228,7 +228,7 @@ Advanced configuration can be used with all JFrog Xray script-based collection c
 
 This section provides a list of variables for Jfrog Xray that you can define in the configuration file.
 
-<table><small>
+<table>
   <tr>
    <td>Variable   </td>
    <td>Usage   </td>
@@ -272,7 +272,7 @@ This section provides a list of variables for Jfrog Xray that you can define in
   <tr>
    <td>HTTP_LOGS_ENDPOINT in SumoLogic sectio   </td>
    <td>HTTP source endpoint url created in Sumo Logic for ingesting Logs.   </td>
-  </tr></small>
+  </tr>
 </table>
 
 </details>

docs/integrations/app-development/jfrog-xray.md

@@ -126,7 +126,7 @@ There are alternative methods for collecting Docker logs and metrics. See [Docke
 There will be no **Network** metrics if you use the `host` network mode for the container.
 :::
 
-<table><small>
+<table>
   <tr>
    <td><strong>Metrics Name</strong></td>
    <td><strong>Unit</strong></td>
@@ -451,7 +451,7 @@ There will be no **Network** metrics if you use the `host` network mode for the
    <td>current </td>
    <td>Count </td>
    <td>Number of PIDs (Not available on Windows) </td>
-  </tr></small>
+  </tr>
 </table>
 
 
@@ -491,7 +491,7 @@ The table below defines the types of variables you can use.
 
 Docker engine event log data doesn't support the tagging with metadata.
 
-<table><small>
+<table>
   <tr>
    <td><strong>Namespace/VAR_TYPE</strong> </td>
    <td><strong>Description</strong> </td>
@@ -521,7 +521,7 @@ Docker engine event log data doesn't support the tagging with metadata.
    <td>User-defined container environment variables that are set with <code>--env|-e</code> flags when starting a container. </td>
    <td>The name of the variable.
 <br/>Dot characters (<code>.</code>) are not supported. </td>
-  </tr></small>
+  </tr>
 </table>
 
 

docs/integrations/containers-orchestration/docker-ulm.md

@@ -826,7 +826,7 @@ This section describes the monitors provided with the MySQL app. These monitors
 
 Here are the Telegraf metrics for MySQL collected by the MySQL app.
 
-<table><small>
+<table>
   <tr>
    <td>mysql_aborted_clients<br/>
 mysql_aborted_connects<br/>
@@ -927,5 +927,5 @@ mysql_threads_connected<br/>
 mysql_threads_created<br/>
 mysql_threads_running<br/>
 mysql_uptime</td>
-  </tr></small>
+  </tr>
 </table>