diff --git a/akka-docs/rst/java/persistence-schema-evolution.rst b/akka-docs/rst/java/persistence-schema-evolution.rst
index 8c0ac8f2ef..cf31056e37 100644
--- a/akka-docs/rst/java/persistence-schema-evolution.rst
+++ b/akka-docs/rst/java/persistence-schema-evolution.rst
@@ -193,7 +193,7 @@ Add fields
 ----------
 
 **Situation:**
-You need to add a field to an existing message type. For example, a ``SeatReservation(String letter, int row)`` now
+You need to add a field to an existing message type. For example, a ``SeatReserved(String letter, int row)`` now
 needs to have an associated code which indicates if it is a window or aisle seat.
 
 **Solution:**
@@ -229,7 +229,7 @@ Rename fields
 -------------
 
 **Situation:**
-When first designing the system the ``SeatReverved`` event featured an ``code`` field.
+When first designing the system the ``SeatReserved`` event featured a ``code`` field.
 After some time you discover that what was originally called ``code`` actually means ``seatNr``, thus the model
 should be changed to reflect this concept more accurately.
 
@@ -275,7 +275,7 @@ or using a library like `Stamina`_ which helps to create those ``V1->V2->V3->...
 .. figure:: ../images/persistence-manual-rename.png
    :align: center
 
-The following snippet showcases how one could apply renames if working with plain JSON (using a 
+The following snippet showcases how one could apply renames if working with plain JSON (using a
 ``JsObject`` as an example JSON representation):
 
 .. includecode:: code/docs/persistence/PersistenceSchemaEvolutionDocTest.java#rename-plain-json
diff --git a/akka-docs/rst/scala/persistence-schema-evolution.rst b/akka-docs/rst/scala/persistence-schema-evolution.rst
index 74cf7ac391..ae34c58558 100644
--- a/akka-docs/rst/scala/persistence-schema-evolution.rst
+++ b/akka-docs/rst/scala/persistence-schema-evolution.rst
@@ -193,7 +193,7 @@ Add fields
 ----------
 
 **Situation:**
-You need to add a field to an existing message type. For example, a ``SeatReservation(letter:String, row:Int)`` now
+You need to add a field to an existing message type. For example, a ``SeatReserved(letter:String, row:Int)`` now
 needs to have an associated code which indicates if it is a window or aisle seat.
 
 **Solution:**
@@ -229,7 +229,7 @@ Rename fields
 -------------
 
 **Situation:**
-When first designing the system the ``SeatReverved`` event featured an ``code`` field.
+When first designing the system the ``SeatReserved`` event featured a ``code`` field.
 After some time you discover that what was originally called ``code`` actually means ``seatNr``, thus the model
 should be changed to reflect this concept more accurately.