diff --git a/blog/2019-08-06-trouble-with-ocsp.markdown b/blog/2019-08-06-trouble-with-ocsp.markdown
index e676303..bc05b23 100644
--- a/blog/2019-08-06-trouble-with-ocsp.markdown
+++ b/blog/2019-08-06-trouble-with-ocsp.markdown
@@ -24,11 +24,7 @@ OCSP[^2] works roughly as follows in an https connection:
 2. Client crafts a OCSP request and sends it to OCSP responder (server provided by the CA).
 3. Responder returns the current status of the certificate, one of `good`, `revoked` or `unknown`
 
-> Note: There are many other interactions defined in the OCSP ecosystem. Maybe
-> the most important one is [OCSP Stapling](https://en.wikipedia.org/wiki/OCSP_stapling). In stapling
-> the original request server sends back OCSP validation message with
-> the certificate itself, removing the need for another seperate
-> request.
+There are many other interactions defined in the OCSP ecosystem. Maybe the most important one is [OCSP Stapling](https://en.wikipedia.org/wiki/OCSP_stapling). In stapling the original request server sends back OCSP validation message with the certificate itself, removing the need for another seperate request.
 
 ## Dissecting an OCSP Request
 If the request is less than `255 bytes`, OCSP allows it to be passed as a GET path. A typical request looks like this