Small fix.

Signed-off-by: Kai Hudalla <kai.hudalla@bosch-si.com>

site/content/release-notes.md

@@ -7,7 +7,7 @@ title = "Release Notes"
 ### Fixes & Enhancements
 
 * `HonoClientImpl`'s strategy for attempting to establish a connection with a peer has been enhanced. The client's *connect* methods by default will only try three times to establish a TCP connection with the peer before giving up. Based on the value of the new *reconnectAttempts* property of `ClientConfigProperties`, the client will then either re-try to connect to the peer (including a fresh DNS lookup of the peer's host name) or fail the overall connection attempt. This way, the client will not get stuck in an endless loop if the peer's IP address has changed or the peer has crashed while the client tries to connect to it.
-* The Docker images provided by Hono now consider resource limitations defined for a container on startup. See [Limiting Resource Usage]({{< relref "deployment/resource-limitation.md" >}}) for details how this can e.g. be used to limit memory consumption. The example deployment already makes use of this mechanism.
+* The Java Virtual Machines run by Docker images provided by Hono now consider resource limitations defined for a container on startup. See [Limiting Resource Usage]({{< relref "deployment/resource-limitation.md" >}}) for details how this can e.g. be used to limit memory consumption. The example deployment already makes use of this mechanism.
 
 ## 0.6