diff --git a/site3/website/docs/api/ledger-api.md b/site3/website/docs/api/ledger-api.md
index 54ef7793b04..541dd01ed48 100644
--- a/site3/website/docs/api/ledger-api.md
+++ b/site3/website/docs/api/ledger-api.md
@@ -163,13 +163,13 @@ long entryId = ledger.addEntry("Some entry data".getBytes());
 ## Reading entries from ledgers
 
 ```java
-Enumerator<LedgerEntry> entries = handle.readEntries(1, 99);
+Enumeration<LedgerEntry> entries = handle.readEntries(1, 99);
 ```
 
 To read all possible entries from the ledger:
 
 ```java
-Enumerator<LedgerEntry> entries =
+Enumeration<LedgerEntry> entries =
   handle.readEntries(0, handle.getLastAddConfirmed());
 
 while (entries.hasNextElement()) {
@@ -187,12 +187,12 @@ For entries outside that range it is possible that the writer never received the
 With this method you can even read entries before the LastAddConfirmed and entries after it with one call, the expected consistency will be as described above.
 
 ```java
-Enumerator<LedgerEntry> entries =
+Enumeration<LedgerEntry> entries =
   handle.readUnconfirmedEntries(0, lastEntryIdExpectedToRead);
 
-while (entries.hasNextElement()) {
+while (entries.hasMoreElements()) {
     LedgerEntry entry = entries.nextElement();
-    System.out.println("Successfully read entry " + entry.getId());
+    System.out.println("Successfully read entry " + entry.getEntryId());
 }
 ```
 
@@ -216,7 +216,8 @@ Ledgers can also be deleted asynchronously:
 
 ```java
 class DeleteEntryCallback implements AsyncCallback.DeleteCallback {
-    public void deleteComplete() {
+    @Override
+    public void deleteComplete(int rc, Object ctx) {
         System.out.println("Delete completed");
     }
 }