diff --git a/src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-kafka-confluentcloud.mdx b/src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-kafka-confluentcloud.mdx
index c63920c0438..d3e76f01e6f 100644
--- a/src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-kafka-confluentcloud.mdx
+++ b/src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-kafka-confluentcloud.mdx
@@ -21,7 +21,7 @@ Complete the steps below to collect Kafka metrics from Confluent using an OpenTe
 
       * You have a docker daemon running
       * You have [Docker Compose](https://github.com/newrelic/newrelic-opentelemetry-examples/tree/main/other-examples/collector/confluentcloud) installed
-      * You must have a [Confluent Cloud account](https://www.confluent.io/get-started/).  
+      * You have a [Confluent Cloud account](https://www.confluent.io/get-started/)  
 
     </Step>
 
@@ -34,13 +34,17 @@ Complete the steps below to collect Kafka metrics from Confluent using an OpenTe
     <Step>
         ##  Add the authentication files 
 
-        This example setup uses TLS to authenticate the request to Confluent Cloud. There are multiple methods to authenticate, so you should follow your company best practices and authentication methods. TLS/SSL requires you to create keys and certificates, create your own Certificate Authority (CA), and sign the certificate. Doing this should leave you with 3 files which need to be added to this directory. They are referenced in this example as the follwing files: `key.pem`, `cert.pem`, `ca.pem`.
+        This example setup uses TLS to authenticate the request to Confluent Cloud. There are multiple methods to authenticate, so you should follow your company best practices and authentication methods. 
+        
+        * TLS/SSL requires you to create keys and certificates, create your own Certificate Authority (CA), and sign the certificate. 
+        * Doing this should leave you with three files which need to be added to this directory. 
+        * Those files are referenced in this example as the follwing files: `key.pem`, `cert.pem`, `ca.pem`.
 
         <Callout variant="important">
           For more information about TLS authentication with Confluent Cloud, check the [documentation on authenticating with TLS](https://docs.confluent.io/platform/current/kafka/authentication_ssl.html) as well as the [security tutorial](https://docs.confluent.io/platform/current/security/security_tutorial.html).
-        </Callout>
-        <Callout variant="note">
+
           For dev/test Confluent environments, you can simplify this by using plain text authentication.
+
         </Callout>
 
     </Step>
@@ -78,6 +82,7 @@ docker compose up
           <th>
             Docs
           </th>
+        </tr>
         </thead>
         <tbody>
           <tr>