From 12d814003e86ff7b6d63877e9b324a56304a19e4 Mon Sep 17 00:00:00 2001 From: upupming Date: Thu, 4 Oct 2018 23:33:14 +0800 Subject: [PATCH] Fixed: code desc & task desc --- 3-animation/3-js-animation/2-animate-ball-hops/task.md | 6 +++--- 3-animation/3-js-animation/article.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/3-animation/3-js-animation/2-animate-ball-hops/task.md b/3-animation/3-js-animation/2-animate-ball-hops/task.md index 1134d192..fdc26c8d 100644 --- a/3-animation/3-js-animation/2-animate-ball-hops/task.md +++ b/3-animation/3-js-animation/2-animate-ball-hops/task.md @@ -2,12 +2,12 @@ importance: 5 --- -# Animate the ball bouncing to the left +# Animate the ball bouncing to the right -Make the ball bounce to the left. Like this: +Make the ball bounce to the right. Like this: [iframe height=250 src="solution"] -Write the animation code. The distance to the right is `100px`. +Write the animation code. The distance to the left is `100px`. Take the solution of the previous task as the source. diff --git a/3-animation/3-js-animation/article.md b/3-animation/3-js-animation/article.md index f0f258c3..e98ee8f0 100644 --- a/3-animation/3-js-animation/article.md +++ b/3-animation/3-js-animation/article.md @@ -100,7 +100,7 @@ The `callback` gets one argument -- the time passed from the beginning of the pa Usually `callback` runs very soon, unless the CPU is overloaded or the laptop battery is almost discharged, or there's another reason. -The code below shows the time between first 20 runs for `requestAnimationFrame`. Usually it's 10-20ms: +The code below shows the time between first 10 runs for `requestAnimationFrame`. Usually it's 10-20ms: ```html run height=40 refresh