From 308d49cbd2a00c231a9ef2eae597946ec18ef9ac Mon Sep 17 00:00:00 2001
From: Paul Blacknell <blacknell@users.noreply.github.com>
Date: Thu, 15 Dec 2022 22:59:30 +0000
Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md

Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
---
 docs/docs/guides/reverse_proxy.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md
index 811c4e375..26ca1f825 100644
--- a/docs/docs/guides/reverse_proxy.md
+++ b/docs/docs/guides/reverse_proxy.md
@@ -62,9 +62,6 @@ This Apache2 configuration snippet then results in unencrypted requests being re
     RewriteCond %{SERVER_NAME} =cctv.mydomain.co.uk
     RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
 </VirtualHost>
-```
-### Step 3: Authenticate users at the proxy
-There are many ways to authenticate a website but a simple straightforward approach is to use [Apache2 password files](https://httpd.apache.org/docs/2.4/howto/auth.html).
 ```xml
 <VirtualHost *:443>
     <Location />