diff --git a/maven-surefire-plugin/src/site/apt/examples/debugging.apt.vm b/maven-surefire-plugin/src/site/apt/examples/debugging.apt.vm
index 8f33e40150..46abb00c7d 100644
--- a/maven-surefire-plugin/src/site/apt/examples/debugging.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/debugging.apt.vm
@@ -76,7 +76,7 @@ mvn -DforkCount=0 verify
 +---+
 #{end}
 
-  Then all you need to do is debug Maven itself.  Since Maven 2.0.8, Maven ships with a <<<mvnDebug>>> shell script that you can
+  Then all you need to do is debug Maven itself.  Maven ships with a <<<mvnDebug>>> shell script that you can
   use to launch Maven with convenient debugging options:
 
 #{if}(${project.artifactId}=="maven-surefire-plugin")
diff --git a/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm b/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
index 1aed2f3a94..79b821a57e 100644
--- a/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
@@ -403,12 +403,3 @@ public class TestSuite {
   therefore the threads will encounter race conditions when setting
   properties, e.g. <<<baseDir>>>, which may lead to changing system properties
   and unexpected runtime behaviour.
-
-* Known issues and limitations
-
- * <<<$\{surefire.forkNumber\}>>> propagation is not supported on Maven 2.x
-   (the variable will be resolved to null value all the time)
-
- * <<<$\{surefire.forkNumber\}>>> is properly propagated within <<<workingDirectory>>>
- since ${project.artifactId}:2.19, more details in
- {{{https://issues.apache.org/jira/browse/SUREFIRE-1136}SUREFIRE-1136}}