diff --git a/doc/JSON-RPC-interface.md b/doc/JSON-RPC-interface.md
index ec332d23ebe..acd821b17c3 100644
--- a/doc/JSON-RPC-interface.md
+++ b/doc/JSON-RPC-interface.md
@@ -188,11 +188,8 @@ this RPC may not yet be reflected as such in this RPC response.
 
 ## Limitations
 
-There is a known issue in the JSON-RPC interface that can cause a node to crash if
-too many http connections are being opened at the same time because the system runs
-out of available file descriptors. To prevent this from happening you might
-want to increase the number of maximum allowed file descriptors in your system
-and try to prevent opening too many connections to your JSON-RPC interface at the
-same time if this is under your control. It is hard to give general advice
-since this depends on your system but if you make several hundred requests at
-once you are definitely at risk of encountering this issue.
+When too many connections are opened quickly the interface will start to
+respond with 503 Service Unavailable to prevent a crash from running out of file
+descriptors. To prevent this from happening you should try to prevent opening
+too many connections to the interface at the same time, for example
+by throttling your request rate.
diff --git a/doc/REST-interface.md b/doc/REST-interface.md
index 2d7d0e37693..6c0d406bf0e 100644
--- a/doc/REST-interface.md
+++ b/doc/REST-interface.md
@@ -15,14 +15,11 @@ apply.
 Limitations
 -----------
 
-There is a known issue in the REST interface that can cause a node to crash if
-too many http connections are being opened at the same time because the system runs
-out of available file descriptors. To prevent this from happening you might
-want to increase the number of maximum allowed file descriptors in your system
-and try to prevent opening too many connections to your rest interface at the
-same time if this is under your control. It is hard to give general advice
-since this depends on your system but if you make several hundred requests at
-once you are definitely at risk of encountering this issue.
+When too many connections are opened quickly the interface will start to
+respond with 503 Service Unavailable to prevent a crash from running out of file
+descriptors. To prevent this from happening you should try to prevent opening
+too many connections to the interface at the same time, for example
+by throttling your request rate.
 
 Supported API
 -------------