From e756dd039dbb22e6bbc8ba574b4c75978e226290 Mon Sep 17 00:00:00 2001
From: Felipe Zimmerle <felipe@zimmerle.org>
Date: Mon, 3 Dec 2018 09:06:28 -0300
Subject: [PATCH] README: Adds link to v2 repo

Making a reference to v2/repo.
---
 README.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index d2549f8b..80ca3790 100644
--- a/README.md
+++ b/README.md
@@ -21,9 +21,8 @@ and applying traditional ModSecurity processing. In general, it provides the
 capability to load/interpret rules written in the ModSecurity SecRules format
 and apply them to HTTP content provided by your application via Connectors.
 
-Currently, libmodsecurity is known to be compatible with the following
-Connectors: ModSecurity Nginx Connector (ModSecurity-nginx).
-
+If you are looking for ModSecurity for Apache (aka ModSecurity v2.x), it is still under maintenence and available:
+[here](https://github.com/SpiderLabs/ModSecurity/tree/v2/master).
 
 ### What is the difference between this project and the old ModSecurity (v2.x.x)?