diff --git a/akka-docs/src/main/paradox/distributed-data.md b/akka-docs/src/main/paradox/distributed-data.md
index a70f13cf81..a2574ad623 100644
--- a/akka-docs/src/main/paradox/distributed-data.md
+++ b/akka-docs/src/main/paradox/distributed-data.md
@@ -710,7 +710,7 @@ durable entry if the data could not be stored for some reason. When enabling `wr
 such errors will only be logged and `UpdateSuccess` will still be the reply to the `Update`.
 
 There is one important caveat when it comes pruning of [CRDT Garbage](#crdt-garbage) for durable data.
-If and old data entry that was never pruned is injected and merged with existing data after
+If an old data entry that was never pruned is injected and merged with existing data after
 that the pruning markers have been removed the value will not be correct. The time-to-live
 of the markers is defined by configuration
 `akka.cluster.distributed-data.durable.remove-pruning-marker-after` and is in the magnitude of days.
diff --git a/akka-docs/src/test/java/jdocs/ddata/DataBot.java b/akka-docs/src/test/java/jdocs/ddata/DataBot.java
index bc62fed17b..b03c9c6579 100644
--- a/akka-docs/src/test/java/jdocs/ddata/DataBot.java
+++ b/akka-docs/src/test/java/jdocs/ddata/DataBot.java
@@ -47,7 +47,7 @@ public class DataBot extends AbstractActor {
     return receiveBuilder()
       .match(String.class, a -> a.equals(TICK), a -> receiveTick())
       .match(Changed.class, c -> c.key().equals(dataKey), c -> receiveChanged((Changed<ORSet<String>>) c))
-      .match(UpdateResponse.class, r -> receiveUpdateResoponse())
+      .match(UpdateResponse.class, r -> receiveUpdateResponse())
       .build();
   }
 
@@ -81,7 +81,7 @@ public class DataBot extends AbstractActor {
     log.info("Current elements: {}", data.getElements());
   }
   
-  private void receiveUpdateResoponse() {
+  private void receiveUpdateResponse() {
     // ignore
   }