diff --git a/akka-docs/rst/java/untyped-actors.rst b/akka-docs/rst/java/untyped-actors.rst
index c708188d07..a7575148c4 100644
--- a/akka-docs/rst/java/untyped-actors.rst
+++ b/akka-docs/rst/java/untyped-actors.rst
@@ -566,9 +566,8 @@ To hotswap the Actor using ``getContext().become``:
 
 This variant of the :meth:`become` method is useful for many different things,
 such as to implement a Finite State Machine (FSM). It will replace the current
-behavior (i.e. the top of the behavior stack), which means that
-:meth:`unbecome` is not called, instead always the next behavior is explicitly
-installed.
+behavior (i.e. the top of the behavior stack), which means that you do not use
+:meth:`unbecome`, instead always the next behavior is explicitly installed.
 
 The other way of using :meth:`become` does not replace but add to the top of
 the behavior stack. In this case care must be taken to ensure that the number
diff --git a/akka-docs/rst/scala/actors.rst b/akka-docs/rst/scala/actors.rst
index 6e90d589ae..21556eeefa 100644
--- a/akka-docs/rst/scala/actors.rst
+++ b/akka-docs/rst/scala/actors.rst
@@ -669,7 +669,7 @@ To hotswap the Actor behavior using ``become``:
 This variant of the :meth:`become` method is useful for many different things,
 such as to implement a Finite State Machine (FSM, for an example see `Dining
 Hakkers`_). It will replace the current behavior (i.e. the top of the behavior
-stack), which means that :meth:`unbecome` is not called, instead always the
+stack), which means that you do not use :meth:`unbecome`, instead always the
 next behavior is explicitly installed.
 
 .. _Dining Hakkers: @github@/akka-samples/akka-sample-fsm/src/main/scala/DiningHakkersOnBecome.scala