diff --git a/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc b/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc
index d38c6b3af6..f04a529691 100644
--- a/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc
+++ b/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc
@@ -2,18 +2,6 @@
 == Technical Overview
 
 
-[[runtime-environment]]
-=== Runtime Environment
-Spring Security {spring-security-version} requires a Java 8 Runtime Environment or higher.
-As Spring Security aims to operate in a self-contained manner, there is no need to place any special configuration files into your Java Runtime Environment.
-In particular, there is no need to configure a special Java Authentication and Authorization Service (JAAS) policy file or place Spring Security into common classpath locations.
-
-Similarly, if you are using an EJB Container or Servlet Container there is no need to put any special configuration files anywhere, nor include Spring Security in a server classloader.
-All the required files will be contained within your application.
-
-This design offers maximum deployment time flexibility, as you can simply copy your target artifact (be it a JAR, WAR or EAR) from one system to another and it will immediately work.
-
-
 [[core-components]]
 === Core Components
 As of Spring Security 3.0, the contents of the `spring-security-core` jar were stripped down to the bare minimum.