diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md
index 524a6d8e84..b31a06c800 100644
--- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md
+++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md
@@ -55,17 +55,6 @@ The request includes the following parameters:
 | `ledger_hash`  | [Hash][]         | No        | A 32-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
 | `ledger_index` | [Ledger Index][] | No        | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
 
-{% admonition type="warning" name="Known Issues" %}
-There are several known issue with this method in `rippled`.
-
-- You must specify the `ledger_index` or `ledger_hash` explicitly instead of using a default or a shortcut string. ([Issue #5034](https://github.com/XRPLF/rippled/issues/5034))
-- JSON-RPC API responses may be missing the `validated` field even when querying validated ledgers. ([#5035](https://github.com/XRPLF/rippled/issues/5035))
-- When querying a recently-closed ledger, a successful response may sometimes return a Ledger Request Object instead of the intended data. ([#5033](https://github.com/XRPLF/rippled/issues/5033))
-- When querying data from older ledgers, the server may take a long time (over 30 seconds) to respond. ([#5036](https://github.com/XRPLF/rippled/issues/5036))
-
-These bugs do not apply to Clio servers.
-{% /admonition %}
-
 ## Response Format
 
 An example of a successful response: