diff --git a/web-animations-1/Overview.bs b/web-animations-1/Overview.bs
index 628f9af6f5f..1539b459e35 100644
--- a/web-animations-1/Overview.bs
+++ b/web-animations-1/Overview.bs
@@ -1691,7 +1691,7 @@ enters the finished state. If notification of the finished state occurred
 synchronously this code would cause the <a>finish event</a> to be queued
 and the <a>current finished promise</a> to be resolved. However, if we
 reverse the order of the two statements such that the
-<code>iterationCount</code> is updated first, this would not happen.
+<code>iterations</code> is updated first, this would not happen.
 To avoid this surprising behavior, notification about the finished state of
 an animation is typically performed asynchronously.
 
@@ -1699,7 +1699,7 @@ an animation is typically performed asynchronously.
 var animation = elem.animate({ left: '100px' }, 2000);
 animation.playbackRate = 2;
 animation.currentTime = 1000; // animation is now finished
-animation.effect.updateTiming({ iterationCount: 2 }); // animation is no longer finished
+animation.effect.updateTiming({ iterations: 2 }); // animation is no longer finished
 </pre></div>
 
 The one exception to this asynchronous behavior is when the <a>finish an