From aa4f737645ab97b5b1eacd6e08b09f3c400a78a7 Mon Sep 17 00:00:00 2001
From: Alex Nederlof <alex@nederlof.com>
Date: Sun, 18 Nov 2018 12:33:34 +0100
Subject: [PATCH] Fix typo in documentation

---
 openjdk/content.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/openjdk/content.md b/openjdk/content.md
index 15f96263b..c1fbdb0c9 100644
--- a/openjdk/content.md
+++ b/openjdk/content.md
@@ -43,7 +43,7 @@ This will add your current directory as a volume to the container, set the worki
 
 On startup JVM tries to detect the number of available CPU cores and the amount of RAM to adjust its internal parameters (like the number of garbage collector threads to spawn) accordingly. When container is run with limited CPU/RAM, standard system API, used by JVM for probing, will return host-wide values. This can cause excessive CPU usage and memory allocation errors with older versions of JVM.
 
-Inside Linux containers, OpenJDK versions 8 and later can correctly detect container-limited number of CPU cores and available RAM. In OpenJDK 11 this is turned on by default. In versions 8, 9, and 10 you have to enable the detection of container-limited amount of RAM using following the following options:
+Inside Linux containers, OpenJDK versions 8 and later can correctly detect container-limited number of CPU cores and available RAM. In OpenJDK 11 this is turned on by default. In versions 8, 9, and 10 you have to enable the detection of container-limited amount of RAM using the following options:
 
 ```console
 $ java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap ...