From ab672674f9433d075261f83ddec55ead5aa7468e Mon Sep 17 00:00:00 2001
From: Richard Sill <67586553+rssag@users.noreply.github.com>
Date: Fri, 15 Dec 2023 09:25:48 +0100
Subject: [PATCH] Merge pull request #1579 from SoftwareAG/bugherd-task-759

bugherd task 759 - section restored for 1018
---
 content/device-sdk/mqtt-bundle/device-certificates.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/content/device-sdk/mqtt-bundle/device-certificates.md b/content/device-sdk/mqtt-bundle/device-certificates.md
index 150bade8b6..99e35e9518 100644
--- a/content/device-sdk/mqtt-bundle/device-certificates.md
+++ b/content/device-sdk/mqtt-bundle/device-certificates.md
@@ -316,8 +316,6 @@ If you are using multiple intermediate certificates between the CA certificate a
     * If your keystore is in the JKS format: `keytool -import -file serverCertificate.pem -alias servercertificate -keystore deviceKeystore.jks`
 6. You can check the content of your keystore (or truststore) with the command: `keytool -list -v -keystore deviceKeystore.jks`
 
-### How to test created certificates with MQTT client
-
 ### Keystore and truststore
 
 Generate a keystore and a truststore as described in [Generating and signing certificates](#generating-and-signing-certificates) if you didn't do it yet.