From 8a68ea279d5b153d59e8fd99ec3bc0d80800ab6e Mon Sep 17 00:00:00 2001
From: Tim van Dijen <tvdijen@gmail.com>
Date: Fri, 19 Aug 2022 12:02:52 +0200
Subject: [PATCH] Fix markdown

---
 modules/saml/docs/keyrollover.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/modules/saml/docs/keyrollover.md b/modules/saml/docs/keyrollover.md
index 11926434d..ee642962f 100644
--- a/modules/saml/docs/keyrollover.md
+++ b/modules/saml/docs/keyrollover.md
@@ -14,13 +14,16 @@ entity publishes metadata with two certificates in it. Meanwhile it continues to
 5. Your SimpleSAMLphp now publishes metadata with only the new cert. Relying parties will refresh metadata and drop the old certificate, not trusting it anymore (or remove the old certificate from their config manually). This last step is essential to ensure that the old certificate is actually distrusted.
 
 ## The steps
+
 ### Create the new key and certificate
 
 First you must create the new key that you are going to use.
 To create a self signed certificate, you may use the following command:
 
-    cd cert
-    openssl req -newkey rsa:3072 -new -x509 -days 3652 -nodes -out new.crt -keyout new.pem
+```bash
+cd cert
+openssl req -newkey rsa:3072 -new -x509 -days 3652 -nodes -out new.crt -keyout new.pem
+```
 
 ### Add the new key to SimpleSAMLphp
 
-- 
GitLab