From 2961bd1288e4bae2c18eb3a12d9a100d2eac6e96 Mon Sep 17 00:00:00 2001
From: Sierra <1969608+wackysysadmin@users.noreply.github.com>
Date: Sat, 8 Jun 2024 00:43:50 +0400
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fa71885..66cb565 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ This can be done by using a method of your choice, if you append a reverse proxy
 
 Serving an OCSP responder over HTTPS <a href=https://datatracker.ietf.org/doc/html/rfc5280#section-8>isn't a requirement</a> but is certainly possible, as mentioned in the wider community OCSP requirements on CA/Intermediate certificates can cause issues, using them on issued server/client certificates from them should be fine. 
 
-<h3>Building the container from scratch</h3>
+<h2>Building the container from scratch</h2>
 The container can be built manually, it is only an Alpine image with OpenSSL and CMD values set.
 
 Enter a directory and create a Dockerfile with the contents from <a href=https://github.com/wackysysadmin/ocsp-responder-container/blob/main/Dockerfile>here</a>.