diff --git a/Reference-Manual-(v3.x).mediawiki b/Reference-Manual-(v3.x).mediawiki
index aecfa8a..50c2c7b 100644
--- a/Reference-Manual-(v3.x).mediawiki
+++ b/Reference-Manual-(v3.x).mediawiki
@@ -4,6 +4,8 @@
 
 = Table of Contents =
 = Introduction =
+WARNING: This document is only in the beginning stages of being adapted and modified from the v2 document. Do not rely on what you see here.
+
 ModSecurity is a web application firewall (WAF). With over 70% of attacks now carried out over the web application level, organisations need all the help they can get in making their systems secure. WAFs are deployed to establish an increased external security layer to detect and/or prevent attacks before they reach web applications. ModSecurity provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with little or no changes to existing infrastructure.
 
 == HTTP Traffic Logging ==
@@ -1200,17 +1202,7 @@ If SecStatusEngine directive is not present, it is disabled.  If SecStatusEngine
 '''Not supported in v3'''
 
 == SecTmpDir ==
-'''Description:''' Configures the directory where temporary files will be created.
-
-'''Syntax:''' <code>SecTmpDir /path/to/dir</code>
-
-'''Example Usage:''' <code>SecTmpDir /tmp</code>
-
-'''Scope:''' Any
-
-'''Version:''' 2.0.0-2.9.x
-
-'''Supported on libModSecurity:''' No
+'''Not supported in v3'''
 
 The location specified needs to be writable by the Apache user process. This is the directory location where ModSecurity will swap data to disk if it runs out of memory (more data than what was specified in the SecRequestBodyInMemoryLimit directive) during inspection.