--- a/mfbt/Move.h
+++ b/mfbt/Move.h
@@ -100,17 +100,17 @@ namespace mozilla {
  *     new(this) C(Move(rhs));
  *     return *this;
  *   }
  *
  * With that in place, one can write move assignments like this:
  *
  *   c2 = Move(c1);
  *
- * This destroys c1, moves c1's value to c2, and leaves c1 in an undefined but
+ * This destroys c2, moves c1's value to c2, and leaves c1 in an undefined but
  * destructible state.
  *
  * As we say, a move must leave the original in a "destructible" state. The
  * original's destructor will still be called, so if a move doesn't
  * actually steal all its resources, that's fine. We require only that the
  * move destination must take on the original's value; and that destructing
  * the original must not break the move destination.
  *